MCP in n8n: Built-in MCP Nodes vs Community MCP Nodes

n8n can work with the Model Context Protocol (MCP) in both directions: it can call tools on an external MCP server, and it can act as an MCP server itself. It ships several built-in nodes for this, and there is also a large group of MCP community nodes. This guide explains what each built-in MCP node does (from n8n’s documentation), lists the most used MCP community packages (from our own npm data), and helps you pick the right one.

Which MCP node do you need?

MCP servers from the registry

n8n’s node panel includes a registry of MCP servers you can connect to an agent in one click. Open the tools panel on an AI Agent node (Tool +), search for the service or open the MCP Servers section, select the server and sign in. Then choose which of its tools the agent can use with Tools to include: all, a selected list, or all except a selected list. n8n creates the MCP credential for you when you sign in. n8n notes that the list of registry servers changes often, so check the node panel for the current list.

The MCP Client Tool node

The MCP Client Tool node is an MCP client that lets an n8n AI Agent use the tools exposed by an external MCP server. n8n says to use it for MCP servers that aren’t in the registry yet. Its parameters:

• SSE Endpoint: the endpoint of the MCP server you want to connect to.
• Authentication: Bearer, generic header, multiple headers, or OAuth2. Select None to try without authentication. Use Multiple Headers Auth when the server needs more than one header, for example an API key and a username.
• Tools to Include: All, Selected (only the tools you pick), or All Except (every tool except the ones you pick).

The MCP Client node

The MCP Client node also uses the tools of an external MCP server, but as regular workflow steps instead of agent tools. Its parameters are Server Transport, MCP Endpoint URL (for example https://mcp.notion.com/mcp), Authentication (the same four methods), Tool (the list is fetched from the server), and Input Mode: Manual for each parameter or JSON for tools with nested parameters. Two options are available: Convert to Binary, which turns images and audio into binary data instead of base64 strings, and Timeout in milliseconds.

The MCP Server Trigger node

The MCP Server Trigger node turns n8n into an MCP server. It exposes a URL that MCP clients connect to, and unlike a normal trigger it only connects to and runs tool nodes. Clients list the available tools and call them. To expose a whole workflow, attach it with the Custom n8n Workflow Tool node.

• Transports: Server-Sent Events (SSE) and streamable HTTP. It doesn’t currently support standard input/output (stdio).
• MCP URL: a test URL, registered when you select Listen for Test Event or Execute workflow, and a production URL, registered when you publish the workflow.
• Authentication: None, Bearer auth or Header auth.
• Path: randomly generated by default to avoid conflicts. You can set your own, including route parameters.

n8n’s docs show how to connect Claude Desktop to this node through the mcp-remote gateway, which proxies the connection for stdio-based clients. They also note that claude.ai custom connectors ask you to sign in to n8n even when Authentication is set to None, and that claude.ai is the only client known to do this.

Running the MCP Server Trigger behind nginx or in queue mode

• Reverse proxy: turn off proxy buffering for the MCP endpoint. n8n also suggests turning off gzip (n8n compresses itself) and chunked transfer encoding, and setting the Connection header to an empty string:

  location /mcp/ {
      proxy_http_version          1.1;
      proxy_buffering             off;
      gzip                        off;
      chunked_transfer_encoding   off;
      proxy_set_header            Connection '';
  }

• Queue mode: with a single webhook replica the node works as expected. With several webhook replicas, route all /mcp* requests to one dedicated webhook replica, or SSE and streamable HTTP connections will break or drop events.

MCP credentials and OAuth2

The MCP credential (OAuth2) is used by the MCP Client Tool node and needs an MCP server that supports OAuth2. It adds two fields to n8n’s generic OAuth2 credential:

• Use Dynamic Client Registration (on by default): n8n registers itself as an OAuth2 client with the server, so you don’t paste a Client ID and Client Secret. Turn it off if the server doesn’t support it or you already have your own Client ID and Secret.
• Resource URL (optional): leave it empty and n8n discovers it from the server.

If you see redirect URI errors during the OAuth2 flow, n8n’s docs say to check that the server’s Dynamic Client Registration endpoint accepts n8n’s OAuth Redirect URL exactly as shown in the credential.

Built-in tool or MCP server for an agent?

n8n’s own guidance: a built-in node used as a tool gives you tighter control, because you fix the operation and can pin parameters so the model only fills in the fields you leave open. An MCP server gives the agent every tool the server exposes from one connection, so it is the better fit when the agent needs a range of actions or you don’t know in advance which one, at the cost of control and more context per call.

MCP community nodes

Our MCP hub lists 51 packages that pass our quality rule, with 161,036 npm downloads a week between them. The most downloaded, with the description each author gives on npm (weekly npm downloads as of 27 October 2026):

n8n-nodes-mcp

By far the most installed MCP package. According to its README, it connects to MCP servers to access resources, execute tools and use prompts, and supports three connection types: command-line (STDIO), where you give the command that starts the server plus its arguments and environment variables; HTTP Streamable, which the author recommends for new setups; and SSE, which the author marks as deprecated but still available. The README also says you must set N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true to use the node as a tool in AI Agents. The stdio option is the main difference from n8n’s built-in client nodes, whose documented settings take an endpoint URL.

Installing an MCP community node

On a self-hosted n8n instance, an owner or admin can install a package from Settings > Community Nodes by entering its npm name, for example n8n-nodes-mcp. Full steps, including npm and Docker, are in How to Install n8n Community Nodes. On n8n Cloud you can only install verified community nodes, see Verified vs Unverified n8n Community Nodes. For the environment variables that control community packages, see n8n Community Node Environment Variables.

FAQ

Does n8n support MCP without community nodes?

Yes. n8n has a registry of MCP servers in the node panel, the MCP Client Tool node for agents, the MCP Client node for regular workflow steps, and the MCP Server Trigger node to expose n8n as an MCP server.

Can n8n be an MCP server?

Yes, with the MCP Server Trigger node. It serves tool nodes, and workflows attached with the Custom n8n Workflow Tool node, to MCP clients over SSE or streamable HTTP.

Does the MCP Server Trigger support stdio?

Not currently, according to n8n’s docs. Clients that only speak stdio, such as Claude Desktop, can connect through the mcp-remote gateway.

What is the most used MCP community node?

n8n-nodes-mcp, with 154,802 weekly npm downloads on our MCP hub as of 27 October 2026.