Enterprise DNA
M MCP Servers Developer low

ellmos-ai/n8n-manager-mcp

by Various

MCP server for n8n workflow management -- view, create, sync, and manage n8n workflows via AI assistants

E

MCP

ellmos-ai/n8n-manager-mcp

Added 1 June 2026

#agent-framework #ai-agents #ai-automation #automation #claude-code #llm #llm-agents #local-first

Overview

A Model Context Protocol server that lets AI assistants view, create, sync, and manage n8n workflows. It connects to an n8n instance via its API, enabling natural language workflow operations.

Best for

Best for
Developers who want to manage n8n workflows through AI assistants using the Model Context Protocol

Use cases

  • Create new n8n workflows by describing them to an AI assistant
  • List and inspect existing workflows without opening the n8n UI
  • Sync workflow changes between an AI assistant and an n8n instance

Notes

A Model Context Protocol server that lets AI assistants view, create, sync, and manage n8n workflows. It connects to an n8n instance via its API, enabling natural language workflow operations.

1 stars on GitHub. Last updated 2026-05-31. Licensed MIT.

Use cases

  • Create new n8n workflows by describing them to an AI assistant
  • List and inspect existing workflows without opening the n8n UI
  • Sync workflow changes between an AI assistant and an n8n instance

Pros

  • Enables natural language workflow management through any MCP-compatible AI client
  • Lightweight TypeScript implementation with minimal dependencies
  • Direct integration with n8n’s existing API

Cons

  • Very early stage with only 1 GitHub star and limited community adoption
  • Requires running an MCP client and configuring n8n API access
  • No built-in error handling or workflow validation beyond what n8n provides

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Enables natural language workflow management through any MCP-compatible AI client
  • Lightweight TypeScript implementation with minimal dependencies
  • Direct integration with n8n's existing API

Cons

  • Very early stage with only 1 GitHub star and limited community adoption
  • Requires running an MCP client and configuring n8n API access
  • No built-in error handling or workflow validation beyond what n8n provides

Pairs with

Other entries in the index that connect to this one. Click through to see the chain.