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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago