What it is
n8n's instance-level MCP server is part of n8n, the workflow automation platform, rather than a separate package. An owner or admin switches it on under Settings > Instance-level MCP, and MCP clients connect to one URL on the instance ending in /mcp-server/http. It works on n8n Cloud and self-hosted instances, and n8n's launch post says it is in every edition, including the free self-hosted Community Edition.
It began as a way to run existing workflows. Since an update announced on 29 April 2026, clients can also create and edit workflows, validate them, run test executions with pinned data and publish them; n8n recommends version 2.18.4 or later. The model writes each workflow in TypeScript, which must type-check before anything reaches the instance. Later releases added project and folder controls (2.24.0), agent management (2.34.0, labelled Preview) and auto-exposure of new workflows (2.36.0, still rolling out).
It is not the MCP Server Trigger node, which turns a single workflow into its own MCP server with tools you design.
Install
https://<your-n8n-instance>/mcp-server/httpOur review
The permission model is the reason to prefer it over community servers. Nothing is exposed in bulk: you enable MCP per workflow, or for a project or folder, and search_workflows returns only previews of workflows that are not enabled. OAuth is the recommended sign-in, each OAuth client gets only the permissions approved at connection, and connected clients can be reviewed and revoked from the settings page.
The gaps are specific. Access is not scoped per client, so every connected client sees every enabled workflow the user can reach. Callback URLs are open by default, which n8n's own docs call less secure. Clients that connect with the personal API key do not appear in the revoke list, and the key cannot be viewed again once you leave the tab. execute_workflow defaults to production mode and runs the published version, so a model can cause real side effects in anything you expose.
On quality, n8n's launch post is unusually frank. Complex workflows often need a second or third pass, branching logic often needs manual cleanup, and models tend to over-build, for instance writing a 50-line Code node where a template and a Set node would do. Edits made in the UI mid-session can be overwritten if the model does not fetch the latest version. n8n also reports that Claude Code produced better results than Claude chat with the same prompt and model.
Compared with the community n8n-MCP server, this one needs no extra process and can use capabilities that are not in n8n's public API, but it lacks that project's large node and template database. Cloud-hosted clients such as Claude.ai and ChatGPT also need the instance reachable from the internet, which is exactly what many teams chose to self-host n8n to avoid.
Where it earns its place
An automation engineer at a 30-person agency on self-hosted n8n
Draft a new client-onboarding workflow from a written spec in Claude Code
The model searches nodes, writes the workflow as TypeScript that must type-check, runs test_workflow with pinned data and publishes only when told. n8n's own post says complex flows need a second or third pass, so budget review time rather than expecting a one-shot build.
An operations lead on n8n Cloud Pro
Let support staff trigger existing refund and reporting workflows from ChatGPT
Enable only those workflows; execute_workflow runs the published version, and each run is an ordinary execution against the plan (10,000 a month on Pro from €50). Revoke a person's client from Connected clients when they leave.
A platform engineer at an insurer with an internal n8n
Keep AI access to automations auditable and easy to switch off
Set callback URLs to trusted-only, require OAuth rather than the shared API key, and keep the instance off the public internet so only local or IDE clients connect. On self-hosted instances N8N_DISABLED_MODULES=mcp removes the endpoints entirely.
Before you commit
- Setup
- An owner or admin enables it under Settings > Instance-level MCP, then enables workflows individually or by project or folder; clients connect to the instance URL ending /mcp-server/http. n8n documents Claude Desktop, Claude Code, Codex, Cursor, VS Code, Gemini CLI and Windsurf, and recommends 2.18.4 or later for building.
- Integrations
- The tools reference documents 25 tools for workflows, executions, credentials, instance context and the builder, of which publish, unpublish, execute and test change state; create, update, restore, agent and data-table tools sit on top. list_credentials returns names, never secret values.
- Data and privacy
- Everything stays in your instance, but the connected client and its model provider see the workflow definitions and execution data the user can reach. n8n Cloud is covered by SOC 2 Type II according to n8n's trust centre; a self-hosted instance keeps data on your servers.
- Cost at scale
- The server adds no fee. Agent-triggered runs count as executions: Cloud Starter at €20 a month covers 2,500 and Pro from €50 covers 10,000 on yearly billing, while a self-hosted Community Edition costs only the server.
- Limits
- test_workflow waits 5 minutes by default and 60 at most; proxies and firewalls must pass the MCP-Protocol-Version, Mcp-Method and Mcp-Name headers; agent management needs the agents module on self-hosted instances.
What's good
- First-party, runs inside n8n with no extra service
- Opt-in exposure per workflow, project or folder
- OAuth clients reviewable and revocable
- Builds, validates and test-runs workflows, not just triggers them
What's not
- Workflow building is a public preview; agents are Preview
- No per-client scoping of workflows
- execute_workflow defaults to production mode
- API-key clients are missing from the revoke list
Best for
Teams already on n8n who want AI clients to run and build workflows under n8n's own permissions.
Alternatives
n8n Instance-level MCP: common questions
- Is n8n Instance-level MCP worth it?
- For a team already running n8n this is the MCP server to start with: first-party, opt-in per workflow, and candid about where its workflow builder still stumbles. We rate it 4.2 out of 5.
- How much does n8n Instance-level MCP cost?
- Included in every n8n edition, including the free self-hosted Community Edition. n8n Cloud and Enterprise are paid n8n plans.
- What are the downsides of n8n Instance-level MCP?
- Workflow building is a public preview; agents are Preview; no per-client scoping of workflows; execute_workflow defaults to production mode; aPI-key clients are missing from the revoke list.
- Who is n8n Instance-level MCP best for?
- Teams already on n8n who want AI clients to run and build workflows under n8n's own permissions.
- How much does n8n Instance-level MCP cost for a team or in production?
- The server adds no fee. Agent-triggered runs count as executions: Cloud Starter at €20 a month covers 2,500 and Pro from €50 covers 10,000 on yearly billing, while a self-hosted Community Edition costs only the server.
- Is n8n Instance-level MCP safe for company data?
- Everything stays in your instance, but the connected client and its model provider see the workflow definitions and execution data the user can reach. n8n Cloud is covered by SOC 2 Type II according to n8n's trust centre; a self-hosted instance keeps data on your servers.
- What are the best n8n Instance-level MCP alternatives?
- The closest alternatives we have reviewed are n8n-MCP and Zapier MCP.
Answers checked Oct 22, 2026.
Make n8n Instance-level MCP? Show this rating on your site
