MCP n8n API Server

Created By
ahmadsolimana year ago
MCP server for n8n API integration - Connect Claude AI to n8n workflows
Overview

What is MCP n8n API Server?

MCP n8n API Server is a server that provides an interface to interact with n8n workflows through the Model Context Protocol (MCP), allowing integration with Claude AI and other MCP clients.

How to use MCP n8n API Server?

To use the MCP n8n API Server, you can install it globally using npm, run it with npx without installation, or clone the repository for local usage. Configuration involves setting up a .env file with your n8n API details.

Key features of MCP n8n API Server?

  • List all n8n workflows
  • Trigger specific workflows with custom data
  • Integration with Claude Desktop and other MCP clients

Use cases of MCP n8n API Server?

  1. Automating workflows in n8n through Claude AI.
  2. Triggering webhooks and workflows programmatically.
  3. Managing and listing workflows for better organization.

FAQ from MCP n8n API Server?

  • Can I use MCP n8n API Server without installing it?

Yes! You can run it directly using npx without any installation.

  • What do I need to configure in the .env file?

You need to set the n8n Host URL, API Key, and optionally the Project ID for cloud instances.

  • Is it possible to run the server locally?

Yes! You can clone the repository and run the server locally.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ahmadsoliman
Star
0
Language
JavaScript
License
-
Tags

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

7 hours ago