n8n MCP Server – Workflows and Data Tables
n8n's official instance-level MCP server gives AI agents structured access to workflows and data tables in an n8n instance. Use it to search, build, edit, test, and execute approved workflows, and to manage supported data-table operations from an MCP-compatible client.
Overview
n8n's official instance-level MCP server connects compatible AI clients to an
n8n Cloud or self-hosted instance. After MCP access is enabled, agents can work
with current workflows and data tables instead of relying only on manually
exported workflow JSON or static model knowledge.
What the MCP server enables
The server exposes tools for workflow management, workflow building, workflow
execution, and data tables. Depending on the n8n version, user permissions, and
which workflows are explicitly exposed, an AI agent can:
- Search workflows the authenticated user can access.
- Retrieve workflow details for MCP-enabled workflows.
- Create and edit workflows and their nodes.
- Trigger and test workflows that have been made available to MCP.
- Execute published workflows in production mode or current unpublished
versions in manual mode. - Search and create data tables.
- Add, rename, or delete data-table columns.
- Rename data tables and insert rows.
- Use workflow descriptions to identify the right automation for a task.
When to use it
Use n8n MCP when an AI agent needs live automation context or must perform
authorized workflow operations. Typical uses include finding an existing
automation, creating a new workflow from a specification, updating a workflow,
testing a draft, executing an approved production workflow, and preparing or
maintaining data tables used by automations.
Connection and authentication
The MCP endpoint is instance-specific and uses the format
https://<your-n8n-domain>/mcp-server/http. n8n supports OAuth 2.0, which is
the recommended option, and a personal MCP access token sent as a Bearer token.
Instance owners or admins must first enable instance-level MCP access. Each
workflow must then be explicitly marked as available in MCP before clients can
retrieve its full definition, modify it, or execute it. Self-hosted instances
can disable the module entirely with N8N_DISABLED_MODULES=mcp.
Key considerations
MCP access is not scoped independently per connected client. All connected
clients can see the same workflows enabled for MCP, although each user's normal
n8n permissions still apply. The workflow search tool can return previews of
workflows the user can access, even when those workflows are not MCP-enabled,
but full access and execution remain restricted. Require human confirmation for
production execution, workflow edits, and destructive data-table changes.
Personal MCP tokens are shown only once, should be stored securely, and are
revoked when rotated.
Supported Transports
streamable_http
URL: https://<your-n8n-domain>/mcp-server/http
Frequently Asked Questions
- When should an AI agent use the n8n MCP server?
- Use it when a workflow needs current n8n automation context or approved operations, such as searching workflows, building or editing automations, testing drafts, executing enabled workflows, or managing supported data tables.
- What does the n8n MCP server add to an AI agent's capabilities?
- It gives the agent structured access to live n8n workflows, workflow builder tools, execution tools, and data-table operations instead of relying only on static model knowledge or manually exported workflow definitions.
- What can an AI agent access or manage through n8n MCP?
- Depending on permissions and enabled workflows, the agent can search, retrieve, create, edit, test, and execute workflows, and can search, create, rename, and modify supported data tables and rows. Full workflow access requires explicit MCP enablement for that workflow.
- How is authentication configured for the n8n MCP server?
- n8n supports OAuth 2.0 and personal MCP access tokens. OAuth is recommended. Access-token clients send the token as a Bearer value to the instance MCP endpoint. Store tokens securely, copy them when first generated, and rotate them when exposure is suspected.
- Which transport should be used for the n8n MCP server?
- Use Streamable HTTP with the instance-specific /mcp-server/http endpoint. n8n's official instance-level MCP server is remote and does not require a separate local stdio package for normal use.