This n8n community node enables interaction with Model Context Protocol (MCP) servers, allowing n8n workflows to leverage AI models for tool execution and data access. It targets n8n users seeking to integrate AI capabilities into their automation pipelines, providing a standardized way to connect to and utilize various AI tools and resources.

How It Works

The node connects to MCP servers via either Command-line Based Transport (STDIO) or Server-Sent Events (SSE). For STDIO, it executes a specified command to launch the MCP server, passing optional arguments and environment variables. The SSE transport connects to a dedicated endpoint for real-time communication. This dual-transport approach offers flexibility, supporting both local command-line execution and standalone server integrations.

Quick Start & Requirements

• Installation: Follow the n8n community nodes documentation.
• Prerequisites: n8n version 1.0.0+, MCP Protocol version 1.0.0+. For AI Agent tool usage, set N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true.
• Resources:
  • n8n community nodes documentation
  • MCP Protocol Documentation
  • MCP TypeScript SDK
  • MCP Transports Overview
  • Using SSE in MCP

Highlighted Details

• Supports two connection types: STDIO (command-line) and SSE (Server-Sent Events).
• Allows configuration of credentials via UI or Docker environment variables (prefixed with MCP_).
• Operations include: Execute Tool, Get Prompt, List Prompts, List Resources, List Tools, Read Resource.
• Can be used as a tool within n8n AI Agents when N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE is enabled.

Maintenance & Community

• The project is a community node, with multiple community videos available for learning.
• Further information on MCP can be found in the "MCP Explained" YouTube series.

Licensing & Compatibility

• n8n is fair-code licensed. The specific license for this community node is not explicitly stated in the README.
• Compatible with n8n v1.0.0+ and MCP Protocol v1.0.0+.

Limitations & Caveats

The README does not explicitly state the license for this specific community node, which may impact commercial use. Environment variables for Docker deployments require specific MCP_ prefixing for MCP servers.