Validation is the distinctive part: five named rule sets with an adjustable strictness, so "is this workflow production-ready" becomes a check rather than an opinion. The code generator is the other half — API routes, OpenAPI docs, types and a client all emitted for one workflow. The README is French throughout, which is worth knowing before you go looking for setup detail.
An MCP server for n8n that does two distinct jobs: it checks your workflows against best-practice rules, and it generates the code needed to call them from a NextJS application. It also manages workflows directly and passes calls through to the n8n API.
- Workflows validated against five rule sets — naming conventions, error handling, security, performance and documentation — with a `strictness` setting, via `WorkflowValidatorTool`
- NextJS integration generated for a workflow: API routes, OpenAPI/Swagger documentation, TypeScript types and an API client — `NextJSIntegrationTool`
- Workflows listed, fetched, created, updated, deleted, exported and imported — `WorkflowManagerTool`, filterable by tag
- Direct n8n API access for anything else, by method, endpoint and query parameters — `N8nApiTool`
- Ready-made workflow templates for common cases, including Google Calendar
A reachable n8n instance, local or remote, with its API connection details set in `.env` — copy `.env.example` and fill it in. Node.js v16 or higher and pnpm v7 or higher. `pnpm install`, `pnpm build`, `pnpm start`; the server listens on `http://localhost:3000` unless the port is overridden in `.env`. For Claude Desktop, point the config at `dist/server.js` with `node`. Package `mcp-n8n-server` 1.0.0, MIT licensed. The README is written in French.
Build from source — clone the repository and build it, then point your client at the binary