n8n Expert MCP: Build n8n Workflows from Claude
Our own product (RetailBox)
Retailbox R&D: our own product, launched December 2025 and taken down in August 2026
We built and ran a hosted MCP server that lets Claude and other AI assistants create, check, and deploy n8n workflows straight into a user's own n8n instance.
What was the problem?
Building n8n workflows by hand is slow, and general AI assistants don't know n8n's node quirks, so they produce workflows that break on import. Teams wanted to describe an automation in plain English and get a working workflow in their own n8n.
How did Retailbox solve it?
We built a multi-tenant MCP server on top of the open-source n8n-mcp project and added our own layer: a built-in n8n methodology and a known-issues knowledge base, an n8n API proxy to create, update, run, and monitor workflows, per-user API keys with usage limits, n8n credentials encrypted with AES-256, an OAuth 2.0 flow for the Claude.ai connector, and Stripe subscriptions with a 7-day trial. A landing page with sign-up and pricing sat in front of it.
Some of the tools came from the open-source project. Multi-tenancy, keys and limits, encryption, OAuth, billing, the methodology and the known-issues base are ours.
Facing the same problem? These are the services that cover this kind of work: n8n workflow development and consulting.
What does it look like?
(opens the full-size image in a new tab)
(opens the full-size image in a new tab)What were the results?
- ✓50+ MCP tools to build, validate, deploy, and debug n8n workflows
- ✓Connected to Claude.ai as a remote connector over OAuth 2.0, with nothing to install locally
- ✓Each user's n8n API key stored encrypted (AES-256)
- ✓Self-serve SaaS: sign-up, 7-day trial, three paid plans billed through Stripe