Skip to content

MCP server

n8n MCP server

n8n's official instance-level MCP server lets AI search, run, build, update and publish workflows and look up nodes and credentials.

At a glance

Maintained by
n8n
Tools exposed
10 listed below
Reviewed
September 24, 2026

Why it matters

What it does and why it matters

n8n is a workflow automation tool that can be self-hosted, which makes it popular with teams that want control over their data. Its official instance-level MCP server lets an assistant search workflows, read details, run them, inspect executions, create workflows from code, update and publish them, search nodes and list credentials.

Building a new automation becomes a conversation: describe the steps, let the assistant draft the workflow, and review it before publishing.

It can build and publish workflows, so we keep publishing behind review and test new workflows on sample data first. Listing credentials shows their names, not their secrets, but still limit who can connect. Self-hosting n8n keeps both the workflows and the data on your own servers.

Use cases

Best business use cases

Draft workflows

Describe an automation and get a draft workflow.

Run workflows

Trigger existing workflows on request.

Debug runs

Inspect failed executions and explain them.

Find nodes

Find the right node for an integration.

Self-hosted automation

Keep automation data on your own servers.

Tools

Available tools

Tool names as published by the maintainer at review time. Versions change, so check the repository for the current list.

Read and write: Read and write: search, run, build, publish and archive workflows, plus agents and data tables.

  • search_workflows

    Find workflows by name, project, tag or folder.

  • get_workflow_details

    Get a workflow's nodes, settings and trigger info.

  • execute_workflow

    Run a workflow in manual or production mode.

  • search_workflow_executions

    Search past workflow runs.

  • get_workflow_execution

    Get one execution's result.

  • create_workflow_from_code

    Build a new workflow from code.

  • update_workflow

    Change an existing workflow.

  • publish_workflow

    Publish (activate) a workflow.

  • search_nodes

    Search available n8n nodes.

  • list_credentials

    List credentials (without secrets).

Workflows

Example workflows

Build a new automation

  1. 1

    Describe the steps.

  2. 2

    The assistant searches nodes.

  3. 3

    It creates a draft workflow.

  4. 4

    You test it with sample data.

  5. 5

    You publish it after review.

Fix a failing workflow

  1. 1

    Ask about recent failures.

  2. 2

    The assistant finds failed executions.

  3. 3

    It reads the error details.

  4. 4

    It proposes an update.

  5. 5

    You approve and republish.

Prompts

Example prompts

  • “Create a workflow that adds new form entries to Google Sheets and posts a Slack message.”

  • “Why did the invoice sync workflow fail last night?”

  • “Run the weekly report workflow now.”

Setup

Installation and configuration

Examples for Claude Desktop and Claude Code. Replace the placeholder values with your own keys, and store secrets outside version control.

Claude Desktop: claude_desktop_config.json

{
    "mcpServers": {
        "n8n-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "supergateway",
                "--streamableHttp",
                "https://<your-n8n-domain>/mcp-server/http",
                "--header",
                "Authorization:Bearer <YOUR_N8N_MCP_TOKEN>"
            ]
        }
    }
}

Claude Code: terminal

claude mcp add --transport http n8n https://<your-n8n-domain>/mcp-server/http
  • Hosted server: https://<your-n8n-domain>/mcp-server/http (built into each n8n instance, Cloud or self-hosted).
  • Needs: OAuth (recommended) or an n8n MCP access token. Enable instance-level MCP in n8n settings..
  • Claude Desktop: Docs also allow Settings > Connectors with the Server URL and OAuth.

Security

Security considerations

  • Review before publishing

    Test and review workflows before they go live.

  • Credentials

    Credential names are visible. Limit who connects.

  • Self-hosting

    Self-host to keep data on your servers.

  • Execution history

    Review execution logs regularly.

Related servers

Servers that pair well with it

Zapier

Zapier's official MCP server lets AI discover, enable and run actions across thousands of connected apps, with separate read and write tools.

Make

Make's official MCP server turns your Make scenarios into tools AI can run, and on paid plans lets it view and modify scenarios and connections.

GitHub

GitHub's official MCP server lets AI read repositories, search code, manage issues and pull requests and, when allowed, change files.

Keep exploring

FAQ

Questions people ask us

Have a question that is not here? Ask us directly.

Start a project

Want this connected to your own systems? We build AI workflows with MCP.

Send a short brief. We reply with questions, a suggested plan and an estimate you can compare with other offers.

Your privacy choices

We use necessary storage to run this site. With your permission we also use Google Analytics to see which pages help people, and load maps from Google. You can change this at any time. Read the cookie policy.