n8n-fabric

What it does

n8n has 500+ nodes and a full REST API, but it lives behind a UI. n8n-fabric puts it behind MCP instead, so an AI assistant can list, build, run and manage workflows in plain language. Every workflow is also embedded into Qdrant, so you can find one by what it does — "how did I handle webhook → transform → API?" — not just by name. Redis caches metadata and execution state; PostgreSQL is n8n's own store.

Related MCP server: n8n MCP Server

The 36 tools

Quick start

git clone https://github.com/ry-ops/n8n-fabric
cd n8n-fabric

# full stack: n8n + Qdrant + Redis + PostgreSQL
docker compose up -d
docker compose ps

open http://localhost:5678   # n8n UI

Run the MCP server from source (Python 3.11+, uv):

uv sync
export N8N_URL=http://localhost:5678
export N8N_API_KEY=your-api-key
uv run n8n-fabric-mcp

Connect Claude Desktop — add to claude_desktop_config.json:

{
  "mcpServers": {
    "n8n-fabric": {
      "command": "uv",
      "args": ["run", "n8n-fabric-mcp"],
      "cwd": "/path/to/n8n-fabric"
    }
  }
}

Then ask: "List my active workflows," "Create a webhook → Slack workflow and activate it," or "Find the workflow that posts deploy notifications and run it."

Configuration

Ports 6343 / 6389 are used to avoid clashing with any existing Qdrant/Redis instances.

Part of the ry-ops fabric

n8n-fabric is one layer of a larger fabric, each exposed over MCP:

Together they close the loop: "Create a webhook-to-Slack workflow and commit it" → n8n-fabric builds it, git-steer commits the JSON, aiana indexes it for next time.

Documentation

• CLAUDE.md — AI assistant context

• Fabric coordination — wiring n8n-fabric, git-steer and aiana together

• ADR-001 — fabric design decisions

License

MIT. See LICENSE.