Hosting

hosted or self-hosted

Transport

Streamable HTTP

Endpoint

https://<your-n8n-domain>/mcp-server/http

Authentication

OAuth 2.0 is recommended. An API key/Bearer token is an alternative. Authorization is user-scoped and bounded by n8n permissions; access to individual workflows must be explicitly enabled.

Requirements

• An n8n Cloud or self-hosted instance with instance-level MCP enabled.
• Instance owner/admin permission to enable MCP access; workflow access is configured per workflow or supported project/folder.
• A client supporting remote Streamable HTTP and OAuth, or an HTTP header bearer-token configuration.

Setup steps

1. In n8n, open Settings > Instance-level MCP and enable MCP access; owner/admin permissions are required.
2. Enable MCP access for each workflow (or supported project/folder) that the client should be able to use. Do not assume the whole instance is exposed.
3. Select Connect in Connection details and copy the Server URL shown by n8n. It ends in `/mcp-server/http`; do not use the editor URL from the browser address bar.
4. For Codex CLI, follow the current n8n client dialog or documented command `codex mcp add n8n --url "https://<your-n8n-domain>/mcp-server/http"`, then run `codex mcp login n8n` and approve access in the browser. Replace the documented domain placeholder only with the Server URL from your own n8n instance.
5. OAuth is recommended. Alternatively, use the API key tab in the n8n Connect a client dialog, copy the generated bearer token once, and store it in the client�s secure local configuration; do not paste it into chat or source control.
6. Reconnect and confirm the n8n tools are listed. Start with `search_workflows` to inspect accessible workflow previews. Only run or modify workflows when explicitly requested and after reviewing their effects.

Crawl4AI fetched three to four official n8n pages for this record, including the MCP server tools reference, which enumerates these 57 named tools. Tool availability is version-gated and may vary by instance; workflow access also depends on per-workflow enablement.

• search_workflows

  Search for workflows with optional filters. Returns a preview of each workflow.

  01
• get_workflow_details

  Get detailed information about a specific workflow, including trigger details.

  02
• execute_workflow

  Execute a workflow by ID. Returns the execution ID immediately without waiting for completion.

  03
• test_workflow

  **Feature availability** `test_workflow` is available from n8n 2.15.0. Test a workflow using pin data to bypass external services. Trigger nodes, nodes with credentials, and HTTP Request nodes are pinned (use simulated data). Other nodes (Set, If, Code, etc.) execute normally, including credential-free I/O nodes like Execute Command or file read/write nodes.

  04
• prepare_workflow_pin_data

  **Feature availability** `prepare_workflow_pin_data` is available from n8n 2.15.0. Prepare test pin data for a workflow. Trigger nodes, nodes with credentials, and HTTP Request nodes need pin data. Logic nodes (Set, If, Code, etc.) and credential-free I/O nodes (Execute Command, file read/write) execute normally without pin data. Returns JSON Schemas describing the expected output shape for each node that needs pin data.

  05
• publish_workflow

  **Feature availability** `publish_workflow` is available from n8n 2.12.0. Publish (activate) a workflow to make it available for production execution. This creates an active version from the current draft.

  06
• unpublish_workflow

  **Feature availability** `unpublish_workflow` is available from n8n 2.12.0. Unpublish (deactivate) a workflow to stop it from being available for production execution.

  07
• get_workflow_history

  **Feature availability** `get_workflow_history` is available from n8n 2.29.0. List the saved version history of a workflow, newest first, so you can inspect how it changed over time and pick a version to retrieve or restore.

  08
• get_workflow_version

  **Feature availability** `get_workflow_version` is available from n8n 2.29.0. From n8n 2.34.0, node credentials are included in the response, reduced to `id` and `name` per slot. Earlier versions strip credentials entirely. Retrieve the full content (nodes, connections, node groups) of a specific workflow version from its history. Use the `versionId` from `get_workflow_history`.

  09
• get_workflow_versions_diff

  **Feature availability** `get_workflow_versions_diff` is available from n8n 2.36.0. Compare two saved versions of a workflow and return what changed between them.

  10
• search_projects

  **Feature availability** `search_projects` is available from n8n 2.14.0. Search for projects accessible to the current user. Use this to resolve a project ID before creating workflows or data tables in a specific project.

  11
• search_folders

  **Feature availability** `search_folders` is available from n8n 2.14.0. Search for folders within a project.

  12
• list_workflow_tags

  **Feature availability** `list_workflow_tags` is available from n8n 2.27.0. List all workflow tags in the instance. Tags are global (not project-scoped) and can be used with `search_workflows` to filter results.

  13
• get_workflow_execution

  **Feature availability** `get_workflow_execution` is available from n8n 2.12.0. Get execution details by execution ID and workflow ID. By default returns metadata only.

  14
• search_workflow_executions

  **Feature availability** `search_workflow_executions` is available from n8n 2.20.0. Search for workflow executions with optional filters. Returns execution metadata including status, timing, and workflow ID.

  15
• list_credentials

  **Feature availability** `list_credentials` is available from n8n 2.21.0. List credentials the current user can access. Use this to find a credential ID before referencing it from a workflow node. Never returns credential secret data.

  16
• get_instance_context

  Read the opening picture of this instance: which workflows exist, what someone recently created, changed, or deleted, and what has run and failed. Call it once at the start of a session, before you ask the user what they want to do. When the user is vague, for example "fix it" or "carry on", the answer is usually the most recent thing here. MCP clients that support resources can read the same content from the [instance context resource](https://docs.n8n.io/connect/connect-to-n8n-mcp-server/mcp-server-tools-reference#instance-context-resource).

  17
• get_instance_activity

  Read the instance activity log: what someone recently created, changed, published, or deleted in this instance, and who did it. Use it to pick up work already in progress. When the user is vague, for example "fix it" or "what should I look at", the answer is usually the most recent entry here.

  18
• expand_instance_activity

  Read one activity log entry, together with everything else the log holds about the same resource.

  19
• get_node_usage

  Report which node types this instance already uses, and how widely. Call it before choosing between equivalent nodes, so a new workflow matches how this instance already builds, for example whether an HTTP Request node or a dedicated integration node is the local habit. Without `nodeType` it returns the histogram of node types in use. With one, it returns the workflows using that node type.

  20
• get_workflow_sdk_reference

  **Feature availability** `get_workflow_sdk_reference` is available from n8n 2.12.0. Get the n8n Workflow SDK reference documentation including patterns, expression syntax, functions, rules, import syntax, guidelines, and design guidance.

  21
• search_nodes

  **Feature availability** `search_nodes` is available from n8n 2.12.0. Search for n8n nodes by service name, trigger type, or utility function. Set `usage` to `"agentTool"` to return only agent-compatible tool nodes. Returns node IDs, discriminators (resource/operation/mode), and related nodes needed for `get_node_types` tool.

  22
• get_node_types

  **Feature availability** `get_node_types` is available from n8n 2.12.0. Get TypeScript type definitions for n8n nodes. Returns exact parameter names and structures.

  23
• get_workflow_best_practices

  **Feature availability** `get_workflow_best_practices` is available from n8n 2.26.0. Get best-practices guidance for a workflow technique. Useful this before searching for nodes or writing workflow code.

  24
• explore_node_resources

  **Feature availability** `explore_node_resources` is available from n8n 2.27.0. Resolve the real values behind a node's resource locator or load-options dropdown (for example Slack channels, Google Sheets tabs, or available AI models). Requires a credential to be set for the desired service.

  25
• validate_workflow

  **Feature availability** `validate_workflow` is available from n8n 2.12.0. Validate n8n Workflow SDK code. Parses the code into a workflow and checks for errors. Always validate before creating or updating a workflow.

  26
• validate_node_config

  **Feature availability** `validate_node_config` is available from n8n 2.25.1. Validate one or more node configurations independently against their generated node schemas. Useful while composing nodes, before assembling workflow code or calling `update_workflow`.

  27
• create_workflow_from_code

  **Feature availability** `create_workflow_from_code` is available from n8n 2.12.0. Create a workflow in n8n from validated SDK code. Parses the code into a workflow and saves it.

  28
• update_workflow

  **Feature availability** `update_workflow` is available from n8n 2.12.0. From n8n 2.20.0, this tool switched to performing partial updates instead of re-writing the full workflow on every update. Update an existing workflow in n8n by applying an ordered batch of targeted partial updates. The batch is atomic: if any operation fails, no changes are saved. From n8n 2.41.0, node group operations are the exception. n8n skips a failing group operation, reports it in `skippedOperations`, and applies the rest of the batch.

  29
• archive_workflow

  **Feature availability** `archive_workflow` is available from n8n 2.12.0. Archive a workflow in n8n by its ID.

  30
• restore_workflow_version

  **Feature availability** `restore_workflow_version` is available from n8n 2.29.0. From n8n 2.31.0, the resulting history entry is automatically named and described based on what was restored. Restore a workflow to a previous version from its history. Re-applies that version as the current draft and records a new history entry. Use `get_workflow_history` to find the `versionId`.

  31
• search_agents

  Search agents the current user can access. Use `publishedOnly` and `excludeAgentId` to discover candidate sub-agents.

  32
• get_agent

  Read an agent draft, its skills, tasks, custom tools, runnable state, and `configHash`. Call before `mutate_agent`. Pass `versionId` to inspect a published version snapshot instead of the draft.

  33
• get_agent_builder_reference

  Return the required reference for agent configuration and `mutate_agent` operations, including the canonical agent configuration JSON Schema. Read before building an agent.

  34
• discover_agent_assets

  Discover model catalogs, chat integrations, attachable workflows, published sub-agents, or MCP registry servers to ground an agent's configuration.

  35
• create_agent

  Create an agent draft, optionally with its initial model, credential, instructions, and ordinary tool configuration. Use `mutate_agent` afterward for skills, tasks, and custom tools.

  36
• mutate_agent

  Apply one config, skill, task, or custom-tool mutation to an agent draft. Returns the next `configHash` for subsequent mutations.

  37
• validate_agent

  Validate an agent draft, its sidecar references, and user-accessible credentials.

  38
• call_agent

  **Feature availability** `call_agent` is available from n8n 2.35.0. Test an agent draft through the built-in Preview chat. Start or continue a conversation with a message request, or resume a returned approval after a person decides. **This tool has real side effects** `call_agent` runs the agent's real tools with real credentials, so it can change data in connected systems and send messages to real recipients. It isn't a dry run. Test on an agent draft you're willing to have act on the outside world.

  39
• verify_agent_mcp_server

  Test an MCP server with a user-accessible credential and return its available tools. Call before writing an `mcpServers` config entry.

  40
• publish_agent

  Publish a valid agent draft and activate its tasks and integrations. Pass `versionId` to republish a previously published version instead.

  41
• unpublish_agent

  Unpublish an agent and stop its live tasks and integrations.

  42
• revert_agent

  Restore an agent draft from a published version, overwriting the draft's config, skills, tasks, and custom tools. Doesn't publish.

  43
• list_agent_versions

  List the publish history of an agent, newest first.

  44
• update_agent_integration

  Configure or disconnect a Slack, Telegram, or Linear conversation integration. This is the only way to manage integrations; `config.replace` and `config.patch` in `mutate_agent` can't change them. For Slack, n8n recommends that you connect without `credentialId` first, so that n8n can create the Slack app for the agent. You can also connect an existing `slackApi` credential.

  45
• delete_agent

  Permanently delete an agent and its associated resources.

  46
• get_user_preferences

  Read the preferences saved for this instance, the current user, and their projects. The n8n MCP server tells clients to call this tool before they create or change anything in n8n, such as a workflow, an agent, a data table, or a folder, and to apply what it returns for the rest of the task. If a preference conflicts with something the user asks for directly, the client follows the user and says which preference it set aside.

  47
• save_user_preference

  Save a new preference for the current user, with the scope `user`. Use it for a lasting rule the user states about how they work, such as "always add an error workflow". Don't use it for an instruction about the current task only, such as "make this one a POST request".

  48
• update_user_preference

  Change a saved preference's text, its scope, or both. Use it when the user refines a preference that's already saved, instead of saving a second one.

  49
• undo_user_preference

  Remove a preference that an MCP client saved for the current user. Use it when the user takes back a preference that was just saved, or asks to forget one an MCP client saved earlier.

  50
• search_data_tables

  **Feature availability** `search_data_tables` is available from n8n 2.16.0. Search for data tables accessible to the current user. Use this to find a data table ID before modifying or adding data to it.

  51
• create_data_table

  **Feature availability** `create_data_table` is available from n8n 2.16.0. Create a new data table with the specified columns.

  52
• add_data_table_column

  **Feature availability** `add_data_table_column` is available from n8n 2.16.0. Add a new column to an existing data table.

  53
• rename_data_table_column

  **Feature availability** `rename_data_table_column` is available from n8n 2.16.0. Rename a column in a data table.

  54
• delete_data_table_column

  **Feature availability** `delete_data_table_column` is available from n8n 2.16.0. Delete a column from a data table. This permanently removes the column and all its data.

  55
• rename_data_table

  **Feature availability** `rename_data_table` is available from n8n 2.16.0. Rename an existing data table.

  56
• add_data_table_rows

  **Feature availability** `add_data_table_rows` is available from n8n 2.16.0. Insert rows into an existing data table. Each row is an object mapping column names to values.

  57

• MCP must be enabled by an instance owner/admin; workflows are individually exposed.
• Clients connected to an instance can see the same MCP-enabled workflows subject to user permissions.

• official codex client setup

  Gives the exact Codex CLI add command and OAuth login step, URL pattern, and API-key alternative.

• official tool reference

  Lists instance-level workflow, agent, builder, and data-table tools and documents version-dependent features and potential side effects.

• official repository

  n8n�s official product repository identifies the publisher and project; behavior/setup claims rely on n8n docs.

• official documentation

  Current official publisher or maintainer documentation checked 2026-10-28T19:00:00.000Z.

Documentation checked 2026-10-29T00:00:00Z. Connection has not been runtime tested.