MCP.so
Sign In

n8n API MCP Server

@jasondsmith72

Repository

About n8n API MCP Server

MCP Server for interacting with an n8n instance

#n8n#api#mcp#server

Basic information

Category

Developer Tools

Runtime

node

Transports

stdio

Publisher

jasondsmith72

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "n8n-api-mcp": {
      "command": "node",
      "args": [
        "C:\\MCP-Servers\\N8N-api-MCP\\build\\index.js"
      ],
      "env": {
        "N8N_URL": "",
        "N8N_API_KEY": ""
      }
    }
  }
}

Tools

10

Search the local API spec database for endpoints matching a query (path, summary, description, tags).

Retrieve detailed information (parameters, request body, responses) for a specific endpoint (path and method) from the local API spec database.

Execute an API call to the configured n8n instance. Checks Fast Memory first; if not found, prompts to save the call to Fast Memory upon success.

Search for API calls using natural language. Checks Fast Memory first, then falls back to searching the API spec database based on the query.

Manually save an API call (path, method, params, data) along with its original natural language query and a description to the Fast Memory database.

List entries currently stored in the Fast Memory database, optionally filtering by a search term.

Delete a specific entry from the Fast Memory database by its ID.

Remove all entries from the Fast Memory database.

Load or update the API Specification database (`api_spec.db`) by parsing an OpenAPI/Swagger JSON file.

Execute an API call using a raw request string (e.g., "GET /workflows?limit=5"). Uses the same underlying logic as `execute_api_call`, including Fast Memory checks and save prompts.

Overview

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.

Comments

More Developer Tools MCP servers

MCP Framework

QuantGeekDev

The Typescript MCP Framework

924

Hello World MCP Server (Reference Extension)

anthropics

Desktop Extensions: One-click local MCP server installation in desktop apps

2.0K

sentry-mcp

getsentry

An MCP server for interacting with Sentry via LLMs.

754

MCP Inspector

modelcontextprotocol

Visual testing tool for MCP servers

10.3K

DevDocs by CyberAGI 🚀

cyberagiinc

Completely free, private, UI based Tech Documentation MCP server. Designed for coders and software developers in mind. Easily integrate into Cursor, Windsurf, Cline, Roo Code, Claude Desktop App

2.1K