nerding-io

n8n-nodes-mcp: Connect n8n Workflows to MCP Servers

A community node for connecting n8n workflows and AI agents to Model Context Protocol servers. Use it to discover and run tools, retrieve resources, and access prompts through STDIO or HTTP-based transports.

TypeScriptMITAutomationWorkflow AutomationMCP
View on GitHub Compare
Stars
3k
Forks
520
Stars, last 30 days
+0

Our take

Health score

35/100

How it is scored
Activity
39
Community
59
Issues
21
Pull requests
20

+0 stars in the last 30 days

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

3,041

Forks

518

Change since Nov 13, 2026: +1 stars·-1 forks

Overview

n8n-nodes-mcp is a community node that connects n8n workflows to Model Context Protocol (MCP) servers. It gives workflows a way to discover and invoke server-provided tools, read resources, and retrieve prompts without implementing MCP interactions in each workflow.

It is suited to n8n users who want to bring MCP-compatible capabilities into automations or make them available to AI Agent nodes. Connections can use STDIO or HTTP Streamable transport, with SSE retained for legacy compatibility.

Key Features

  • Execute tools exposed by an MCP server, passing parameters.
  • List available tools and inspect their descriptions and parameter schemas.
  • List prompts and retrieve a selected prompt.
  • List server resources and read a resource by URI.
  • Connect over STDIO or the recommended HTTP Streamable transport.
  • Configure server command arguments, environment variables, and HTTP headers.
  • Use the node as a tool in n8n AI Agents when community package tool usage is enabled.

Use Cases

  • An n8n workflow can call an MCP server’s search or other tools as part of a larger automation.
  • An n8n administrator can connect an AI Agent to tools exposed by one or more MCP servers.
  • A workflow can retrieve information from MCP resources or prompt templates and pass it to later steps.
  • Teams already using MCP servers can connect them to n8n workflows instead of building separate integrations for each server.

Getting Started

Install the package using the n8n community nodes installation guide. Configure MCP credentials for STDIO or HTTP Streamable, then add the node to a workflow. For setup details and examples, see the repository README.

Alternatives

  • Hexabot: Hexabot provides a standalone agentic-workflow runtime with tools and conversational channels, rather than an MCP connector embedded in n8n.
ProjectLanguageLicenseStarsStatus
n8n-nodes-mcpTypeScriptMIT3kNot checked yet
HexabotTypeScript–1.1kActive

Considerations

  • Requires n8n version 1.0.0 or later and an MCP server compatible with the selected transport.
  • HTTP Streamable is recommended for new integrations. SSE is deprecated and retained for legacy use.
  • To use the node as an AI Agent tool, set N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true in the n8n environment.
  • STDIO connections require the MCP server command and its runtime to be available to the n8n environment. HTTP connections may require endpoint and authentication headers.

Found this useful?

Share it with someone who would like n8n-nodes-mcp.

Comparisons

Hexabot vs n8n-nodes-mcp