n8n

This MCP server for n8n provides tooling to validate, manage, and generate integrations around your n8n workflows. It includes a WorkflowValidatorTool to enforce naming conventions, error handling, security, performance, and documentation standards; a NextJSIntegrationTool to auto-generate Next.js API routes, OpenAPI/Swagger docs, TypeScript types, and a client API for easier integration; and a WorkflowManagerTool to list, retrieve, create, update, delete, export, and import workflows directly from n8n. You can also access the n8n API via the N8nApiTool for advanced operations. Install and run the server, then configure Claude Desktop or other clients to point at the MCP server to start validating workflows, generating Next.js integrations, and managing your workflow catalog. The server exposes an API and a set of CLI-like tool interfaces to perform common automation tasks against your n8n instance.

Prerequisites:

• Node.js v16 or higher
• pnpm v7 or higher
• Access to an n8n instance (local or remote)
• Git (optional, for cloning the repository)

Install steps:

1. Clone the repository or navigate to the project directory
2. Install dependencies:

pnpm install

3. Configure environment variables:

cp .env.example .env

Edit the .env file to provide your n8n API connection details (base URL, authentication token if required) and any other environment-specific settings. 4) Build the project (if a build step is present):

pnpm build

5. Start the MCP server:

pnpm start

6. Verify the server is running (default port 3000) and accessible at http://localhost:3000 or the port configured in your .env.

Optional (Claude Desktop integration):

• Create or update claude_desktop_config.json to include your MCP server reference, for example:

{
  "mcpServers": {
    "n8n-mcp-server": {
      "command": "node",
      "args": ["/path/to/mcp-n8n-server/dist/server.js"]
    }
  }
}

Environment variables and configuration options:

• N8N_API_BASE_URL: Base URL for your n8n instance API.
• N8N_API_TOKEN: Token or API key for authenticating with n8n if required.
• PORT: Port for the MCP server to listen on (default 3000).
• ENVIRONMENT: Runtime environment, e.g., production or development. Common issues:
• Ensure your n8n instance is reachable from the MCP server host.
• If using a remote n8n, configure CORS or API access restrictions accordingly.
• If the API routes or OpenAPI docs generation fail, verify that the n8n API path and credentials are correct.
• When building NextJS integrations, ensure the output directory exists and is writable by the process.
• For Claude Desktop integration, ensure the path in claude_desktop_config.json correctly points to the built server.js file.