n8n MCP Server

Created By
illuminaresolutionsa year ago
MCP server implementation for n8n workflow automation
Overview

what is n8n MCP Server?

The n8n MCP Server is an implementation that provides access to n8n workflows, executions, credentials, and more through the Model Context Protocol, allowing Large Language Models (LLMs) to interact with n8n instances securely and in a standardized manner.

how to use n8n MCP Server?

To use the n8n MCP Server, you need to install it via npm or from source, configure it with your n8n API key, and set it up in your preferred application like Claude Desktop or Cline.

key features of n8n MCP Server?

  • List and manage workflows
  • Execute workflows and view details
  • Manage credentials and handle tags
  • Generate security audits
  • Enterprise features for project and user management

use cases of n8n MCP Server?

  1. Automating workflows in n8n using LLMs
  2. Managing and executing workflows programmatically
  3. Integrating n8n with other applications through the MCP protocol

FAQ from n8n MCP Server?

  • How do I install the n8n MCP Server?

You can install it using npm with the command npm install -g @illuminaresolutions/n8n-mcp-server or clone the repository and build it from source.

  • What are the core features?

Core features include listing and managing workflows, executing workflows, and managing credentials.

  • Are there any enterprise features?

Yes, enterprise features include project management and advanced user management, which require an n8n Enterprise license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
illuminaresolutions
Star
-
Language
-
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