N8nApiToolLABSCO SUMMARY
A linter for workflows, which is not a thing n8n ships.
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.
What it is
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.
What you get
- Workflows validated against five rule sets — naming conventions, error handling, security, performance and documentation — with a
strictnesssetting, viaWorkflowValidatorTool - 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
Requirements
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. Clients connect over SSE at http://localhost:3000/sse. The README's Claude Desktop block launches dist/server.js as a stdio command, but the server it builds only speaks SSE. Package mcp-n8n-server 1.0.0, MIT licensed. The README is written in French.
Setup effort
Build from source — git clone https://github.com/lowprofix/n8n-mcp-server
USE CASES
01
Checking a workflow before it goes live
Run validation with the rule sets that matter to you and turn strictness up for anything customer-facing.
02
Calling an n8n workflow from a web app
Generate the API route, the TypeScript types and the client into your NextJS project instead of hand-writing them.
03
Auditing what is running
List workflows filtered by tag and export the ones you want to review or version.
04
Reaching an endpoint the tools do not cover
Call the n8n API directly with the method, endpoint and parameters you need.
4 tools
Listed in project docs. Your client may show a different list.
WorkflowManagerToolNextJSIntegrationToolWorkflowValidatorToolBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- Node.js v16 or later
- pnpm v7 or later
- A reachable n8n instance (local or remote) with an API key
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/lowprofix/n8n-mcp-server
cd n8n-mcp-server
pnpm install
cp .env.example .envEdit .env: set N8N_API_URL to your n8n instance's API address (the example is http://localhost:5678/api/v1) and N8N_API_KEY to an n8n API key
TERMINAL
pnpm build
pnpm startThe server listens for MCP clients over SSE at http://localhost:3000/sse (set PORT in .env to change the port)
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"n8n-mcp-server": {
"url": "http://localhost:3000/sse"
}
}
}For clients that connect to an SSE URL. Start the server first with pnpm start in your clone, so it reads your .env.
