Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for n8n workflow management -- view, create, sync and manage workflows via AI.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"n8n-manager": {
"command": "npx",
"args": [
"-y",
"n8n-manager-mcp"
]
}
}
}Run this in your terminal
claude mcp add n8n-manager -- npx -y n8n-manager-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"n8n-manager": {
"command": "npx",
"args": [
"-y",
"n8n-manager-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"n8n-manager": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"n8n-manager-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account lukisch, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 9 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, aamio rendezvous
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Meet an agent you have not met, exchange messages that expire, and prove it happened. No account.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
🇬🇧 English | [🇩🇪 Deutsch](README_de.md) | [🇪🇸 Español](README_es.md) | [🇯🇵 日本語](README_ja.md) | [🇷🇺 Русский](README_ru.md) | [🇫🇷 Français](README_fr.md) | [🇨🇳 简体中文](README_zh.md) | [🇮🇳 हिन्दी](README_hi.md) | [العربية](README_ar.md) | [বাংলা](README_bn.md) | [Português](README_pt.md)
*Part of the ellmos-ai family and the open-bricks umbrella.*
[!NOTE]
For AI Assistants & LLMs: An
llms.txtindex file is available in the root directory for fast context ingestion, tool catalog references, and directory listings.
MCP (Model Context Protocol) server for managing n8n workflows via AI assistants like Claude, Cursor, and Windsurf.
| Nr | Section | Highlights |
|---|---|---|
| 01 | 📐 System Architecture & Topology (#system-architecture) | Local stdio transport, multi-server routing, and safety middleware |
| 02 | 📊 Dual Mermaid Diagrams (#dual-mermaid-diagrams) | Component Architecture flowchart TD & Safe Mutation Lifecycle sequence diagram |
| 03 | 🌐 Directory Status & Registries (#directory-status) | Official listings on npm, Glama, PulseMCP, and Enterprise DNA |
| 04 | 🎯 Target Personas & Discoverability (#target-personas--discoverability) | Persona mapping [PERSONA-01] to [PERSONA-04] and High-Intent SEO queries |
| 05 | 📋 Project Capabilities & Boundaries (#comparative-matrix--alternatives) | 10 implementation areas and their documented limits |
| 06 | 🛡️ Capabilities & Implementation Boundaries (#core-capabilities--safety-invariants) | Read-only mode, optional local backups and audit logging, input checks, and scope notes |
| 07 | ✨ Key Features (#features) | Direct REST integration, multi-server routing, backup snapshots, node catalog |
| 08 | ⚙️ Client Installation (#installation) | One-command setup for Claude Code, Claude Desktop, Cursor, and Windsurf |
| 09 | 🚀 Quick Start (#quick-start) | Step-by-step workflow creation, execution inspection, and server switching |
| 10 | 🛠️ Available Tools (19 Tools) (#available-tools) | Complete MCP tool reference across CRUD, executions, backups, and nodes |
| 11 | 🔗 Optional: n8n-workflow-manager Seam (#optional-n8n-workflow-manager-seam) | Decision tracking and change history integration with paired manager service |
| 12 | 🔒 Configuration & Safety Defaults (#configuration) | Environment variables, local backup root, and strict monotonic constraints |
| 13 | 🧪 Development & Testing (#development) | Test suite, smoke runner, and current CI platform scope |
| 14 | 🧱 ellmos-ai Ecosystem (#ellmos-ai-ecosystem) | Sibling MCP servers, BACH agent OS, and open-bricks desktop software suites |
| 15 | 📜 Third-Party Licenses & Transparency (#third-party-licenses--transparency) | Project license and dependency license inventory |
| 16 | 📈 Marketing & Personas Log (#marketing--personas-log) | Comprehensive positioning log, keyword matrix, and 3-phase roadmap |
| 17 | 📝 Changelog (#changelog) | Complete release notes, security hardenings, and discoverability history |
| 18 | ⚖️ Liability / Haftung (#haftung--liability) | Statutory open-source donation notice under §§ 516 ff. BGB, MIT disclaimer, 48h SLA |
The n8n Manager MCP Server operates as a local-first, stdio-connected bridge between AI development environments (Claude Code, Claude Desktop, Cursor, Windsurf) and local or remote n8n instances.
stdio) using JSON-RPC 2.0. It inherits the privileges of the process that launches it.servers.json are plaintext; config updates use a temporary file and rename.n8n_describe_nodes) without a network call. It does not expose full node schemas or required properties.+========================================================================================================+
| [VIEW 1: CALLER RUNTIMES & AGENT ECOSYSTEM] | | Claude Code CLI | Claude Desktop | Cursor IDE / Windsurf | Antigravity / Gemini / Codex | | (JSON-RPC 2.0 Stdio) | (stdio MCP Client) | (Dev Environments) | (Autonomous Orchestrator Swarms) | +===================================================+====================================================+ | v +========================================================================================================+ | [VIEW 2: N8N-MANAGER-MCP CORE ENGINE & MUTATION CHECKS] | | +----------------------------------------------------------------------------------------------------+ | | | Tool Dispatcher (19 Registered MCP Tools: CRUD, Execution Inspect, Backup/Restore, Node Catalog) | | | +----------------------------------------------------------------------------------------------------+ | | | Read-Only Check: persisted setting or N8N_MANAGER_READ_ONLY=1 process ceiling | | | | Input Bounds and Backup-Path Checks (scope limited to the implemented handlers) | | | | Multi-Instance Routing: configured profiles and endpoints | | | | Bundled Offline Node Catalog: Common Node Types & Descriptions (INV-NODE-09) | | | +----------------------------------------------------------------------------------------------------+ | +===================================================+====================================================+ | v +========================================================================================================+ | [VIEW 3: RUNTIME PERSISTENCE, BACKUP SNAPSHOTS & LOCAL AUDIT LOG] | | +------------------------------------+----------------------------------+----------------------------+ | | | Conditional Workflow Snapshots | Local Append-Only Audit Log | Multi-Server Config Store | | | | ~/.n8n-manager-mcp/backups/ | ~/.n8n-manager-mcp/audit.log | ~/.n8n-manager-mcp/ | | | | ({server}/{id}-{timestamp}-{reason}.json) | (Timestamped JSON entries) | (servers.json; POSIX 0600 requested) | | | +------------------------------------+----------------------------------+----------------------------+ | +===================================================+====================================================+ | v +========================================================================================================+ | [VIEW 4: STDIO TRANSPORT, CONFIGURED ENDPOINTS & LAUNCHER PRIVILEGES] | | Inherits launcher process privileges | Configured n8n/manager requests; interactive update check may run | | No MCP listening port (stdio transport) | Published security policy and reporting contacts | +========================================================================================================+
flowchart TD
Client["AI Client (Claude Code / Desktop / Cursor / Windsurf)"] -->|"MCP Stdio Protocol (JSON-RPC 2.0)"| Router["Tool Router (19 Tools)"] subgraph MCPServer["n8n Manager MCP Server (Local Stdio Process)"] Router --> Safety["Mutation Checks (Read-Only Gate & Backup-Path Checks)"] Safety --> Backup["Conditional Pre-Mutation Snapshot"] Safety --> MultiServer["Multi-Server Manager"] Safety --> Catalog["Offline Node Catalog (n8n_describe_nodes)"] Router --> Audit["Local Audit Append"] end MultiServer -->|"REST API (API Key / Auth Header)"| LocalInst["Configured n8n Instance (local or remote URL)"] MultiServer -->|"REST API (HTTPS / Token)"| CloudInst["Remote / Cloud n8n Instance"] Backup --> BackupFS[("Backups (~/.n8n-manager-mcp/backups/)")] Audit --> AuditFS[("Audit Log (~/.n8n-manager-mcp/audit.log)")]
These diagrams show the intended operation order. Snapshots are attempted only when backup_before_mutations is enabled (default: true); if that attempt fails, the following n8n mutation request is not sent. Audit append errors propagate and can follow a successful remote mutation.
sequenceDiagram
autonumber actor AI as AI Assistant (Claude / Cursor) participant MCP as n8n-manager-mcp Router participant Safety
Only the beginning is shown; read the rest in the repo