n8n API MCP Server

What is n8n API MCP Server?

An MCP server that interacts with a self-hosted n8n instance, enabling API calls, searching endpoints via a local database populated from an OpenAPI spec, and storing frequently used calls in a Fast Memory database for quicker natural language access.

How to use n8n API MCP Server?

Clone the repository, install dependencies (npm install), build the server (npm run build), and configure environment variables (N8N_URL, N8N_API_KEY) in your MCP client’s settings (e.g., cline_mcp_settings.json). Then load the API spec using load_api_spec_from_json before using search tools.

Key features of n8n API MCP Server

• Two local SQLite databases: API spec cache and Fast Memory.
• Search endpoints by path, summary, description, or tags.
• Execute API calls with automatic Fast Memory prompts.
• Natural language search that checks memory first, then spec.
• Manual save, list, delete, and clear Fast Memory entries.
• Raw request string execution (send_raw_api_request).

Use cases of n8n API MCP Server

• Automate workflow management via natural language queries to n8n.
• Quickly reuse previously successful API calls without remembering details.
• Explore and test n8n API endpoints without external documentation.
• Build AI assistants that can interact with an n8n instance programmatically.

FAQ from n8n API MCP Server

What dependencies or runtime are required?

Node.js, npm, and your n8n instance URL plus an API key are required. The server is built with TypeScript and uses SQLite local databases.

Where does the API specification data come from?

It is loaded from a downloaded OpenAPI/Swagger JSON file using the load_api_spec_from_json tool. This file may be available from your n8n instance at /api/v1/docs-json.

How does the Fast Memory database work?

It caches successful API calls linked to natural language queries. On a successful call via execute_api_call or send_raw_api_request (where the call is not already in Fast Memory), the server prompts to save it. It supports manual save, list, delete, and clear operations.

What transport does the server use?

The server communicates via standard MCP protocol but the README does not specify a particular transport layer (stdio or HTTP). Configuration examples show a command: "node" setup typical for stdio transport.

Are there any known limits?

The README does not mention any specific limits. The server is designed for self-hosted n8n instances and requires the user to provide the URL and API key.