← All case studies

Nearly 130 GitHub stars · MIT licensed

N8N2MCP — Open Source

Turns an n8n workflow into a Model Context Protocol server, so automation a team already built becomes a tool Claude or Cursor can call directly.

The problem

Teams adopting the Model Context Protocol almost always start by writing new tools from scratch — rebuilding integrations they already have running somewhere else.

What we built

N8N2MCP converts an n8n workflow into an MCP server, so automation a team already built becomes a tool that Claude, Cursor or any MCP client can call directly. Paste the workflow, map the credentials, deploy, and the endpoint is live. Open source, MIT licensed.

Before: Teams rebuild tools they already have; Integrations duplicated for MCP. After: Nearly 130 GitHub stars · MIT licensed.

Before

  • Teams rebuild tools they already have
  • Integrations duplicated for MCP

How it works

  1. Paste the workflow. An existing n8n workflow is the input; nothing is rewritten.

  2. Map the credentials. The workflow’s credentials are mapped to the new server.

  3. Deploy as an MCP server. The workflow is exposed as a Model Context Protocol tool.

  4. Call it from any client. Claude, Cursor or any MCP client calls it directly.

After

Nearly 130 GitHub stars · MIT licensed

Stack

Open SourceMCPn8nClaude

Why it holds up

The tools are usually already there, sitting in the workflow engine, one adapter away from being callable. Nearly 130 GitHub stars is third-party validation of that argument that nobody paid for — anyone can read the source and check the claim.

Related service: AI staff augmentation

Get started

Talk to the engineer who will build it.

You will speak with me directly. Bring the use case, the data and the constraints, and I will give you a straight view on feasibility, effort and the first thing to ship.

Cat YungBook a call

Hong Kong & London time zones