1. Conduid
  2. Automation
  3. N8n Nodes MCP Local
MCP server · Automation

N8n Nodes MCP Local

· github.com/PhilflowIO/n8n-nodes-mcp-local
Unclaimed automation
InstallView source
30Low

Scored 6 months ago · breakdown

About N8n Nodes MCP Local

N8n Nodes MCP Local is an MCP server in the Automation category.

Install

From source
git clone https://github.com/PhilflowIO/n8n-nodes-mcp-local

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about N8n Nodes MCP Local

Powered by Claude · Grounded in docs

I know everything about N8n Nodes MCP Local. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

n8n-nodes-mcp-local

Transform any MCP server into native AI Agent tools.

npm version

Quick Start

  1. Install: Settings → Community Nodes → n8n-nodes-mcp-local
  2. Workflow: Add AI Agent + MCP Local Provider → Connect via tool
  3. Credentials: Create "MCP Server (STDIO)" → Package: wikipedia-mcp → Save triggers npx and discovers tools
  4. Done. All MCP tools appear at your Agent.

Why This Node?

Most MCP servers are STDIO-based — designed to run locally via npx. n8n has two existing options, but neither gives you direct access:

n8n Native MCP nerding.io MCP This Node
STDIO / npx ❌ ✅ ✅
SSE / HTTP ✅ ✅ ❌
Agent sees individual tools ✅ ❌ ✅
Tool selection (include/exclude) ✅ ❌ ✅

What's Missing

n8n Native gives you clean Agent integration, but no STDIO. You'd need to host MCP servers yourself.

nerding.io has STDIO, but requires two separate nodes for every call. The Agent never sees actual tools — just a "List Tools" and "Execute Tool" wrapper. More indirection, less reliable tool calls.

Direct Access

nerding.io:   Agent → "List Tools" → "Execute Tool" → Result
This node:    Agent → tool_name() → Result

No detours. The Agent sees every tool, reads its description, and calls it like any native function.

Built for Flow

This node uses npx — the MCP server is fetched on every execution

No setup friction. Test ideas, iterate fast, ship when it works.

When you're ready for production scale with high-frequency calls, host your MCP server and switch to the native n8n MCP Client.

How It Works

┌──────────────────┐       ┌──────────────────┐
│  MCP Local       │──────►│    AI Agent      │
│  Provider        │       │                  │
└──────────────────┘       └──────────────────┘
         │
         ▼
    npx wikipedia-mcp
         │
         ▼
    Tools discovered & registered:
    • store_memory
    • retrieve_memory
    • list_memories

Configuration

Credentials

Field Description Example
MCP Package npm package name wikipedia-mcp
Environment Variables Optional config API_KEY=xxx

Node Options

Option Description
Tools Mode all / selected / exclude
Include/Exclude Tools Filter which tools the Agent sees

Troubleshooting

First run slow? npx downloads the package. Subsequent runs use npm cache.

No tools discovered? Check package name. Some servers need environment variables.

License

MIT

Credits

Model Context Protocol by Anthropic • n8n

Build something. Ship it.

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About N8n Nodes MCP Local

How do I install N8n Nodes MCP Local?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is N8n Nodes MCP Local safe to use with an AI agent?

Its trust score is 30 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is N8n Nodes MCP Local still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.