Skip to main content
Glama
n8n MCP Server

n8n MCP Server

by nikolausm

n8n MCP Server

MCP n8n

MCP (Model Context Protocol) server for n8n workflow automation. This server enables AI assistants like Claude to interact with n8n instances via the REST API.

Features

  • 🔄 Workflow Management: List, create, update, and delete workflows

  • ▶️ Execution Control: Execute workflows and monitor executions

  • 🏷️ Tag Management: Organize workflows with tags

  • 📊 Execution History: Access workflow execution history and results

  • 🔑 Credential Management: List available credentials (read-only)

  • 🌐 Webhook Management: Create and manage webhooks

  • 🔍 Search: Search workflows by name or tags

Related MCP server: n8n MCP Server

Prerequisites

  • Node.js 20 or higher

  • n8n instance with API access enabled

  • n8n API key

Installation

From npm (when published)

npm install -g n8n-mcp-server

From source

git clone https://github.com/nikolausm/n8n-mcp-server.git
cd n8n-mcp-server
npm install
npm run build

Configuration

Getting your n8n API Key

  1. Log in to your n8n instance

  2. Go to Settings → API

  3. Generate an API key

Configure Claude Desktop

Add the following to your Claude Desktop configuration (claude_desktop_config.json):

{
  "mcpServers": {
    "n8n": {
      "command": "node",
      "args": ["/path/to/n8n-mcp-server/dist/index.js"],
      "env": {
        "N8N_URL": "https://your-n8n-instance.com",
        "N8N_API_KEY": "your-api-key-here"
      }
    }
  }
}

For n8n cloud instances, use:

  • N8N_URL: https://your-subdomain.app.n8n.cloud

Available Tools

Workflow Management

  • list_workflows - List all workflows with optional filtering

  • get_workflow - Get detailed information about a specific workflow

  • create_workflow - Create a new workflow from JSON

  • update_workflow - Update an existing workflow

  • delete_workflow - Delete a workflow

  • activate_workflow - Activate a workflow

  • deactivate_workflow - Deactivate a workflow

Execution

  • execute_workflow - Execute a workflow with optional input data

  • get_executions - Get execution history with filtering options

  • get_execution - Get details of a specific execution

  • delete_execution - Delete an execution

  • retry_execution - Retry a failed execution

Tags

  • get_tags - List all available tags

  • create_tag - Create a new tag

  • update_tag - Update a tag

  • delete_tag - Delete a tag

Other

  • get_credentials - List available credentials (names only)

  • search_workflows - Search workflows by name or tags

  • get_workflow_webhooks - Get webhook URLs for a workflow

Usage Examples

List all active workflows

Assistant: I'll list all your active n8n workflows.

[Uses list_workflows tool with active=true]

Execute a workflow

Assistant: I'll execute the workflow with the data you provided.

[Uses execute_workflow tool with workflowId and data]

Create a new workflow

Assistant: I'll create a new workflow for you.

[Uses create_workflow tool with workflow JSON]

Development

Setup

npm install

Build

npm run build

Test locally

N8N_URL=https://your-instance.com N8N_API_KEY=your-key npm start

Run tests

npm test

The protocol tests start the built server over stdio and do not contact an n8n instance. Schema regression tests use a mocked client and HTTP adapter. GitHub CI runs the offline tests and dependency audit on Node.js 20 and 24 without API credentials.

Security Notes

  • Never commit your API keys

  • Use environment variables for sensitive data

  • The MCP server has the same permissions as your API key

  • Consider using a restricted API key if possible

Contributing

Contributions are welcome! Please:

  1. Fork the repository

  2. Create a feature branch

  3. Make your changes

  4. Add tests if applicable

  5. Submit a pull request

License

MIT - see LICENSE file

Support

Author

Michael Nikolaus - GitHub

Available Tools

19 tools
activate_workflowC

Activate a workflow

Inputs: workflowId (required).

create_tagB

Create a new tag

Inputs: name (required).

create_workflowB

Create a new n8n workflow from JSON definition

Inputs: name (required), nodes (required), connections (required), active, +2 more.

deactivate_workflowB

Deactivate a workflow

Inputs: workflowId (required).

delete_executionC

Delete an execution

Inputs: executionId (required).

delete_tagD

Delete a tag

Inputs: tagId (required).

delete_workflowC

Delete a workflow

Inputs: workflowId (required).

execute_workflowB

Execute a workflow with optional input data

Inputs: workflowId (required), data.

get_credentialsA

List available credentials (names only, no sensitive data)

Inputs: no named parameters.

get_executionC

Get details of a specific execution

Inputs: executionId (required).

get_executionsB

Get workflow execution history with filtering options

Inputs: workflowId, finished, limit, cursor.

get_tagsB

List all available tags

Inputs: no named parameters.

get_workflowC

Get detailed information about a specific workflow

Inputs: workflowId (required).

get_workflow_webhooksB

Get webhook URLs for a workflow

Inputs: workflowId (required).

list_workflowsC

List all n8n workflows with optional filtering

Inputs: active, limit, cursor, tags.

retry_executionB

Retry a failed execution

Inputs: executionId (required).

search_workflowsA

Search workflows by name or tags

Inputs: query (required).

update_tagC

Update a tag

Inputs: tagId (required), name (required).

update_workflowB

Update an existing workflow

Inputs: workflowId (required), name, nodes, connections, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 19 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose: workflow CRUD, activation, execution, and history; tag CRUD; credential listing; and webhook retrieval. No two tools overlap significantly.

    Naming Consistency5/5

    All tool names follow a consistent 'verb_noun' pattern in snake_case, such as 'create_workflow', 'get_executions', and 'update_tag'. No mixed conventions or vague verbs.

    Tool Count4/5

    With 19 tools, the set covers multiple domains (workflows, executions, tags, credentials, webhooks) and each tool seems necessary. Slightly on the higher end but still well-scoped for the server's purpose.

    Completeness4/5

    Workflows, executions, and tags have full CRUD/lifecycle coverage. Credentials are limited to listing names, which is a minor gap but likely intentional for security. No obvious dead ends for typical workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers