
n8n MCP Community
io.github.drzamarianPublished by GitHub account drzamarianv0.3.1Updated Oct 24, 2026
A security-focused MCP server for self-hosted n8n Community Edition.
Overview
Security-focused MCP server that lets an AI assistant manage workflows, executions, credentials, tags, users and diagnostics on a self-hosted n8n Community…
- What you can do
- List, read, create, update, diff, archive, activate and delete workflows, and edit single nodes
- List and inspect executions, and retry, stop or delete them
- Create, read, update, test and delete credentials, and find where a credential is used
- Manage tags and users, including inviting members or admins
- Run health checks, insights summaries, security audits, workflow search, node-type inventory and offline node docs
- When to use it
- Useful when you run a self-hosted n8n Community Edition instance and want an assistant to inspect, build or debug workflows and manage instance objects through the Public API, with read-only access by default.
- Requirements
- Runs locally over stdio via npm (Node.js 22 or 24) or as a Claude Desktop MCPB extension. Needs the n8n base URL in N8N_API_URL and a dedicated n8n Public API key in N8N_API_KEY; N8N_MCP_MODE selects read-only, write or unsafe. Network access to the n8n host is required.
Installation
In SourceWeft
- Open n8n MCP Community in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
n8n MCP Community
[n8n-mcp-community MCP server]
A security-focused Model Context Protocol server for self-hosted n8n Community Edition
Give your AI client 44 tools for self-hosted n8n Community Edition. Manage workflows, nodes, runs, credentials, tags, users, and diagnostics. No paid n8n features. The server makes no external AI calls.
[Install with npm] [Download MCPB] [Read the docs]
Install
You need Node.js 22 or 24, your n8n URL, and an n8n API key.
Install
--global installs the command once. Use npx below if you do not want a
global install.
Connect
Restart your client. You should see 44 tools, 5 resources, and 4 prompts.
If the client cannot find the command, run command -v n8n-mcp-community on
macOS/Linux or where n8n-mcp-community on Windows. Put that full path in
"command".
Want no global install? Copy this command into the client configuration shown in the full guide:
Want the Claude Desktop app flow? Use the MCPB below. See the full installation guide for updates, rollback, and checks.
Claude Desktop: install the MCPB (no Node.js needed)
- Open the latest GitHub release.
- Download the file that ends in
.mcpb. - In Claude Desktop, open Settings → Extensions → Advanced settings → Install Extension….
- Pick the file. Enter your n8n URL, API key, and mode.
Anthropic's MCPB guide explains the same steps. Our installation guide explains how to check the download.
Install public builds only from npm or the latest GitHub release.
[Animated demo showing installation, connection, and a useful local Introspect finding]
Why this project
- Community Edition first. The release surface is designed for self-hosted n8n Community Edition, without presenting paid-only capabilities as available.
- 44 useful tools, one explicit contract. Every tool has bounded inputs, documented side effects, MCP safety annotations, and contract tests.
- Safe by default. Read-only mode is the default. You choose when to allow writes or the full tool set.
- Deterministic Introspect.
n8n_introspectruns a local 23-rule engine; it does not execute workflows, call an agent, or contact an external model. - Surgical node updates.
n8n_update_nodechanges one validated node path while preserving the rest of the workflow and disclosing the Public API's non-atomic limitation. - Truthful discovery.
n8n_list_node_typesreports only types observed in accessible workflows. It does not claim to be a complete installed catalog. - Data minimization. Credential values, raw execution values, pin data, and static workflow data are not returned by the generic public tools.
See verification evidence
Current verification
The current source candidate has been verified with:
- exactly 44 tools, 5 resources, and 4 prompts over real stdio;
- 320 passing tests locally on Node.js 24.21.0; CI and release gates require the pinned Node.js 22.23.1 and 24.18.0 matrix;
- zero findings from Gitleaks, Semgrep, Trivy, and both project-root
production/full
npm auditruns; all three source scanners are reproduced in CI, with immutable scanner/action identities; - a separate no-override consumer install that resolves the patched
@hono/node-server2.x line, requires a zero-finding production audit, and proves the stdio runtime and exact 44/5/4 inventory; - a reproducible dependency-license gate covering 187 installed package paths;
- bounded same-origin HTTP contracts and zero-request policy-denial tests;
- all 44 compiled tool lifecycles on disposable n8n Community 2.30.5 and 2.30.7 instances with egress isolation, revoked keys, cleanup, and zero residue; and
- a reviewed offline npm-tarball installation under the project's committed dependency policy, plus a byte-reproducible unsigned MCPB with the same compiled runtime and complete production dependency notices.
Publication proceeds only through the reviewed release procedure: the repository-pinned MCPB signing identity, a human artifact-baseline receipt, tag-scoped protected-environment approval, and an externally signed MCPB handoff verified byte for byte against the reviewed unsigned candidate.
Safety modes
Selecting unsafe mode is the complete server-side authorization gate for unsafe tools. MCP safety annotations remain accurate so compatible clients can apply their native approval UX, and the n8n API key remains the final upstream permission boundary.
Plain HTTP is accepted automatically only for loopback URLs. A non-loopback
HTTP instance additionally requires N8N_ALLOW_INSECURE_HTTP=1, which accepts
the risk of exposing the API key and data in transit.
Tool catalog
Every entry links to its complete input, output, endpoint, compatibility, failure, and security reference.
Workflows
Executions
Credentials
Tags
Users
Diagnostics and instance metadata
Resources and prompts
The server also exposes five static resources:
n8n://usage-guiden8n://node-docs/webhookn8n://node-docs/coden8n://node-docs/http-requestn8n://node-docs/if
Four prompts guide safe workflow creation, debugging, optimization, and
credential management: create-workflow, debug-workflow,
optimize-workflow, and manage-credentials.
Security model in one minute
- The server uses local stdio; it does not expose an inbound HTTP listener.
- Connected requests are same-origin and limited to the configured n8n host.
- Redirects are rejected; request and response bodies are bounded to 2 MiB.
- Generic output is validated, sanitized, bounded to 256 KiB, and wrapped as
{ "data": ..., "redacted": boolean, "untrusted": true }. - Raw credential values and generic execution payload values are never returned.
n8n_introspectuses fixed local rules and has no external-model code path.- Security controls reduce risk; they do not make untrusted n8n content safe to execute or authorize broader API-key permissions.
Read the complete security model and use SECURITY.md to report a vulnerability privately.
Documentation
- Documentation map
- Getting started
- Installation and upgrades
- Configuration
- Complete tool reference
- Tested examples
- FAQ
- Client configuration
- Architecture
- Security model
- Compatibility
- Troubleshooting
- Provenance
- Roadmap
- Changelog
Development
npm run verify:contributor runs the complete keyless contributor gate,
including formatting, dependency licenses/notices, strict TypeScript, all
tests, the compiled runtime, and documentation inventory parity.
See CONTRIBUTING.md before opening a change.
Scope and non-affiliation
This project is not affiliated with, endorsed by, or sponsored by n8n GmbH.
“n8n” is used only to identify compatibility with the n8n product and Public
API. The project does not redistribute the n8n-nodes-base catalog and does not
use browser cookies, interactive session routes, or runtime package downloads to
construct one.
The v0.3.x surface intentionally excludes arbitrary workflow execution, credential/workflow transfer, folders, data tables, beta evaluation endpoints, and execution annotations. See the roadmap for the annotation proposal retained outside the release target.
License and maintainer
The project is released under the MIT License. Third-party dependencies retain their own licenses.
Created and maintained by Dr. Walter Zamarian Jr..
Source: README.md at commit fd2185e
Tools
0Version history
2- v0.3.1LatestOct 4, 2026
- v0.3.0Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts