← Back to directory

n8n MCP Client Node

Community

Connect and call MCP servers in n8n workflows.

GitHub source repository ↗

★ 3.0k Stars Category · Dev Tools Popular Source revision 6ee215b30e51

40FMRS · D

Reliability

5/20

Security and permissions

6/20

Maintenance

7/20

Documentation

11/20

Setup experience

11/20

This node enables seamless integration of MCP servers into n8n workflows, supporting multiple transports and use as a tool in AI agents. However, it requires proper security configuration, especially when using local commands.

Read the FMRS scoring method →

n8n-nodes-mcp-client is an n8n community node that lets you interact with Model Context Protocol (MCP) servers in your n8n workflows. It supports accessing resources, executing tools, and using prompts, and can be used as a tool in AI agents. It supports STDIO, SSE (deprecated), and HTTP Streamable transports.

Tools

execute_tool

Execute a specific tool with given parameters.

get_prompt

Retrieve a specific prompt template.

list_prompts

List all available prompts.

list_resources

List all resources provided by the server.

list_tools

List all available tools with their descriptions and parameter schemas.

read_resource

Read a specific resource by URI.

Setup

To install the community node in n8n:

Go to n8n's 'Settings' -> 'Community Nodes'.
Enter the package name n8n-nodes-mcp-client and install.
Alternatively, refer to the official n8n documentation for installing community nodes.

If you want to use this node as a tool in AI agents, you must set the environment variable N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true and restart n8n.

Fit and risk

Best for

n8n users who want to integrate MCP tools into their automation flows.
Developers building AI agents that need to call external tools and data sources.
Teams that need to quickly connect to various MCP servers, whether local (via npx) or remote (HTTP).

Not for

Developers who need a direct programming interface rather than a graphical workflow.
Users without an n8n environment who just want a standalone MCP client.
Users who rely on SSE transport and cannot upgrade to HTTP Streamable (SSE is deprecated).

Required permissions

Requires the ability to install community nodes in n8n.
Requires setting the environment variable N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true to use the node as a tool.
With STDIO transport, it can execute arbitrary local commands (as defined by the user's command setting), potentially with system permissions.
Can make network requests to configured MCP servers, including sending additional headers.

Risks and side effects

STDIO commands can execute arbitrary local commands; if misconfigured (e.g., using untrusted servers), it may compromise the system.
SSE transport is deprecated and no longer updated, potentially having security vulnerabilities.
Environment variables (like API keys) may be stored in n8n credentials; if the n8n instance is not secure, there is a risk of exposure.
Running third-party MCP servers (e.g., downloaded via npx) may introduce insecure dependencies.

Troubleshooting

Ensure n8n version is at least 1.0.0.
If you need to use tools in AI agents, confirm that N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true is set and n8n is restarted.
Check that the command and arguments are correct, especially for local npx servers.
Verify that the MCP server URL is reachable and that additional headers are properly set.
If SSE connections fail, consider switching to HTTP Streamable (recommended).

Use cases

Connect to external MCP servers like Brave Search, OpenAI, Serper, Weather, etc., within n8n workflows.

Let an AI agent call multiple tools via MCP, e.g., search for popular destinations, check weather, and find travel restriction news.

Manage MCP resources, prompts, and tools from within n8n.

Supported clients

Claude DesktopPartial support

Related MCP servers

Compare with other MCP servers