n8n MCP Server

Created By
dopehuntera year ago
Complete MCP server for n8n workflow management in Cursor
Overview

what is n8n MCP Server?

The n8n MCP Server is a Model Context Protocol (MCP) server that facilitates the management of n8n workflows directly within LLMs and AI agents, enabling seamless integration and execution of workflows.

how to use n8n MCP Server?

To use the n8n MCP Server, install the package via npm, configure your n8n connection in a .env file, and start the server. You can then interact with the server using HTTP requests to manage workflows.

key features of n8n MCP Server?

  • List available workflows from n8n
  • View workflow details
  • Execute workflows
  • Monitor workflow executions
  • Pass parameters to workflows
  • MCP-compatible interface for AI agents

use cases of n8n MCP Server?

  1. Automating data processing workflows in n8n.
  2. Integrating n8n workflows with AI agents for enhanced automation.
  3. Monitoring and managing workflow executions in real-time.

FAQ from n8n MCP Server?

  • What is the purpose of the n8n MCP Server?

It allows for the management and execution of n8n workflows within AI agents using the Model Context Protocol.

  • How do I troubleshoot connection issues?

Ensure your n8n instance is running and accessible, and verify your API key is correct.

  • Can I use n8n MCP Server with Docker?

Yes, you can run the n8n MCP Server in a Docker container.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dopehunter
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

5 hours ago