Automatelab N8n

by ratamaha-git

277 downloads
Not rated
GitHub

About

Generate n8n workflow JSON (including LangChain AI agents), scaffold custom TypeScript nodes, and lint workflows for missing credentials, deprecated types, and broken connections.

Details

Author
ratamaha-git
Downloads
277
Categories
Developer Tools, Other, Automation, AI

- Generate workflow JSON from plain-English descriptions.
- Diagnose failed executions with per-node hints.
- Lint workflow JSON for silent failures and deprecated nodes.
- Scaffold custom n8n node TypeScript files.
- Interact with live n8n instances via five REST tools.
- Works without a live n8n instance for core tools.

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name Automatelab N8n
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

Install the server globally with npm install -g @automatelab/n8n-mcp, then configure it in your MCP host (e.g., Cursor's mcp.json or Claude Desktop's claude_desktop_config.json) by specifying the command npx -y @automatelab/n8n-mcp. Optionally set environment variables N8N_API_URL and N8N_API_KEY to enable the five live-instance tools; the four stateless tools work without them. After restarting the host, the nine n8n_* tools appear in the MCP panel.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "automatelab n8n": {
            "n8n": {
                "command": "npx",
                "args": [
                    "-y",
                    "@automatelab/n8n-mcp"
                ],
                "env": {
                    "N8N_API_URL": "",
                    "N8N_API_KEY": ""
                }
            }
        }
    }
}

McpServers

{
    "n8n": {
        "command": "npx",
        "args": [
            "-y",
            "@automatelab/n8n-mcp"
        ],
        "env": {
            "N8N_API_URL": "",
            "N8N_API_KEY": ""
        }
    }
}

AnMCPserver forn8nthat gives Claude, Cursor, and other AI agents tools for generating workflows, linting, diagnosing failed executions, and driving live n8n instances.

We use n8n daily inside AutomateLab and kept hitting the same LLM failures: workflow JSON that imports but fails at runtime, AI Agent clusters wired with the wrong connection types, executions that silently drop items with no clue where to look. Dumping the whole n8n catalog into context doesn't fix it - the failure modes are too subtle (typeVersion mismatches, IF v1 schema, credentials that don't survive import).

So we built a small, focused server:encode the failure modes the lint can catch, the cluster topology the generator must respect, and the diagnosis the agent can't do alone.For a walkthrough of the nine tools with example output, see thelaunch post on automatelab.tech.

Other n8n MCP servers (notablyczlonkowski/n8n-mcp) compete on breadth - 20+ tools and an indexed corpus of every n8n node. They own that niche.

This server is thedebugging-and-first-run-correctness MCP for n8n:

- execution_explainis the wedge. Paste the execution JSON; get back per-node findings: which nodes returned 0 items, which had unresolved={{ ... }}expressions, error messages with concrete hints. No other MCP server does this well, and it hits the n8n community's #1 debugging pain point (silent data loss between nodes).
- workflow_generateis opinionated about AI Agent topology - emits proper LangChain clusters withai_languageModel/ai_memory/ai_toolconnections (sub-nodes connectupwardto the agent, not viamain). Imports cleanly on n8n 1.x.
- workflow_lintcatches the silent failures: deprecated node types (Function → Code, spreadsheetFile → convertToFile), AI Agent missing language model, IF v1 schema, Webhook missing webhookId, broken connections across all connection types (not justmain).
- 5 REST tools(gated onN8N_API_URL+N8N_API_KEY) let you list, fetch, create, activate workflows and pull executions - so the lint and explain tools can run against your live workflows, not just JSON pasted in chat.

Plus: a pairedAgent Skillthat teaches the model when to use which tool and where to load deeper context (split intoreferences/so it doesn't bloat the prompt).

Tool names follow dot-notation and form a navigable tree:node.,workflow.,execution.. Every tool declares anoutputSchema(so callers can type-check responses) and MCPannotations(read-only / destructive / idempotent / open-world hints).

Stateless(work without a live n8n instance):

Live-instance(requireN8N_API_URL+N8N_API_KEYenv vars):

v0.5.0 changes.Three new tools:workflow_diff,execution_replay,execution_timeline. Lint expanded with 10 new rules (rate-limit, credential drift, expression staleness, code sandbox, webhook test path, manualTrigger-in-active, DST schedule risk, disabled-but-wired, empty Set, HTTP method/body mismatch). New runtime policy env vars:N8N_MCP_READ_ONLY,N8N_MCP_DISABLED_TOOLS,N8N_MCP_ALLOWED_WORKFLOW_IDS,N8N_MCP_ALLOWED_TAGS. DXT bundle + Dockerfile + Render/Railway/Fly deploy configs.

v0.4.0 breaking change.Tools were renamed fromn8n_(snake_case) to dot-notation. Update any prompts, agent skills, or scripts that referenced the old names.

Constrain the server without forking. Set these env vars before launching:

Useful when handing the MCP to a junior agent or wiring it behind a customer-facing assistant.

- Claude Desktop one-click: build the.dxtbundle fromdxt/manifest.json(seedxt/README.md).
- Docker:docker build -t n8n-mcp . && docker run --rm -i -e N8N_API_URL=... -e N8N_API_KEY=... n8n-mcp.
- Render: drop in
render.yamland click "New from Blueprint".
- Railway:
railway.tomlrailway upin the repo root.
- Fly.io:
fly.tomlfly launch --copy-config.

Use the n8n MCP GitHub Action to lint workflows, diagnose executions, and generate workflow JSON in your CI/CD pipeline:

- uses: ratamaha-git/n8n-mcp@v1 with: command: 'lint' workflow-json: ${{ env.WORKFLOW_JSON }}

SeeACTION.mdandGITHUB-ACTION-SETUP.mdfor examples and publication details.

Cursor(~/.cursor/mcp.json) orClaude Desktop(claude_desktop_config.json):

{ "mcpServers": { "n8n": { "command": "npx", "args": ["-y", "@automatelab/n8n-mcp"], "env": { "N8N_API_URL": "https://your-n8n.example.com", "N8N_API_KEY": "n8n_..." } } } }

Theenvblock is optional - the 4 stateless tools work without it. Get an API key from n8n:Settings → API → Create API key.

Restart your MCP host. The 12 dot-notation tools (workflow.,node.,execution.*) appear in the MCP panel.

Use workflow_generate to build: Stripe webhook → Slack message + new row in Google Sheets.

Returns workflow JSON ready for n8n's "Import from File" dialog.

Here's a failed execution from n8n. Why is the Slack node not firing? [paste JSON]

WARNING [Filter] Returned 0 items. Downstream nodes will not execute. hint: Common causes: (1) IF/Switch routed to the other branch — check parameters.conditions. (2) Filter/Set node dropped everything — inspect its output explicitly. INFO [Last node executed was "Filter". If the workflow stopped here unexpectedly, check its output items below.]
ERROR [AI Agent] AI Agent has no ai_languageModel sub-node connected. Attach a chat model (e.g. lmChatOpenAi). WARNING [Webhook] Webhook node has no webhookId. n8n auto-generates one on import, so the production URL will change. WARNING [LegacyFunction] Node type "n8n-nodes-base.function" is deprecated. Use "n8n-nodes-base.code".

Theexamples/directory ships with two ready-to-import workflows:

- workflow-stripe-to-slack.json- Stripe webhook fans out to Slack and Google Sheets.
- workflow-rss-to-discord.json- RSS feed trigger posts new items to a Discord channel.

Import either via n8n'sImport from Filedialog.

git clone https://github.com/ratamaha-git/n8n-mcp cd n8n-mcp npm install npm run build npm run smoke

npm run smokeboots the server with a--smokeflag that lists registered tools and exits without binding stdio. Useful for CI or first-run sanity checks.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

What Shopify did for ecommerce, Chipp does for AI agents. Build, deploy, and monetize AI agents for your business — no engineering team required.

CodeVF MCP lets AI hand off problems to real engineers instantly, so your workflows don’t stall when models hit their limits.

Client implementation for Mastra, providing seamless integration with MCP-compatible AI models and tools.

Agent-native developer Q&A API with MCP + A2A endpoints for citations, job pickup, and answer submission.

On-demand access to 150+ specialist AI agent templates — search, browse, and spawn agents. 150x reduction in context usage vs loading agents locally.

AgentChatBus is a persistent AI communication bus that lets multiple independent AI Agents chat, collaborate, and delegate tasks — across terminals, across IDEs, and across frameworks.

Remote MCP server (Streamable HTTP) at https://mcp.agenticrail.nz/ — deterministic step-order enforcement for AI agents. evaluate_step returns ALLOW or DENY before a step runs; verify_receipt proves a sequence's Ed25519-signed, hash-chained receipt chain is intact. No auth required: omit the bearer token and calls run on the public demo key. That first clause matters — the form has no "remote/hosted" field, and putting the endpoint in the description is the convention on that list ("Fully REMOTE! Just use…"). The rest mirrors your own server card verbatim, so the listing and the card can't drift.

An AI Agent with optional Human-in-the-Loop Safety and Model Context Protocol (MCP) integration.

Agent Mail Rooms is a paid remote MCP endpoint for OpenAI Codex agent coordination MCP. It exposes structured JSON tools, a public server card, token-based access, usage receipts, and audit-

MCP bridge that lets Claude Code delegate heavy tasks to the Antigravity CLI (agy) — purpose-built tools, model routing with fallback, session continuity, and output truncation to save Claude's context and tokens.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.