Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
MCP server for n8n workflow management -- view, create, sync and manage workflows via AI.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"n8n-manager": {
"command": "npx",
"args": [
"-y",
"n8n-manager-mcp"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add n8n-manager -- npx -y n8n-manager-mcpPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"n8n-manager": {
"command": "npx",
"args": [
"-y",
"n8n-manager-mcp"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"n8n-manager": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"n8n-manager-mcp"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub lukisch, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.1.0) llegó al registro hace 9 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Winecellarbuilders
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Find the team for your wine room.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
🇬🇧 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
Solo se muestra el principio; lee el resto en el repo