n8n MCP Community
Related Servers
Alternatives to n8n MCP Community
- AlicenseAqualityAmaintenanceA Model Context Protocol server that provides AI assistants with comprehensive access to n8n node documentation, properties, and operations for effective workflow automation.2846,471 npm22,981MIT
- AlicenseAqualityDmaintenanceAn MCP server providing AI assistants with comprehensive access to n8n node documentation, properties, and operations, enabling deep knowledge about n8n's 2,063 workflow automation nodes.746,471 npmMIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for n8n workflow automation, enabling management of workflows, executions, credentials, tags, users, and webhooks via an MCP-compatible client.MIT
- AlicenseBqualityDmaintenanceAn MCP server enabling secure interaction with n8n workflows, executions, and settings via the Model Context Protocol, designed for integration with Large Language Models (LLMs).3350 npm118MIT
- AlicenseAqualityDmaintenanceFree and open-source MCP server for managing n8n workflows, executions, and tags via n8n's API. Enables workflow creation, activation, debugging, and deletion from any MCP client.122MIT
- AlicenseBqualityDmaintenanceA comprehensive MCP server that provides full control over n8n automation workflows through natural language. It offers 43 tools for managing workflows, executions, credentials, and data tables, with safety features like write-mode protection and double-validated workflow creation.431MIT
- AlicenseBqualityDmaintenanceMCP server for managing n8n workflows and executions. Enables listing, activating, deactivating, and executing workflows, as well as monitoring executions and instance health.9MIT
- AlicenseBqualityCmaintenanceSafe MCP server and CLI tool for testing, scoring, and inspecting n8n workflows. Features 19 tools for workflow testing, execution traces, tiered scoring, and a built-in node catalog with 800+ node types. Designed with safety-first approach: no credential management, no secrets lifecycle, no auto-fix loops.191MIT
TDQS
Scored across 44 tools
Each tool targets a distinct resource/action combination, and the descriptions explicitly disambiguate near neighbors such as list vs get vs search, get_version vs diff, archive vs deactivate, and workflows_update vs update_node. No two tools appear to do the same thing.
The dominant n8n_<resource>_<action> pattern is consistent across most tools, e.g. n8n_workflows_get, n8n_tags_delete, n8n_executions_list. A few verb-first outliers like n8n_search_workflows, n8n_update_node, n8n_get_node_docs, and n8n_list_node_types slightly break predictability.
44 tools is a heavy surface for an agent to navigate and exceeds the 25+ threshold, even though the resource coverage is broad. The tools are well-organized, but the sheer count adds meaningful selection overhead.
The server covers full lifecycle operations for workflows, executions, credentials, tags, and users, plus search, audit, insights, and node documentation. Minor gaps exist—such as no workflow execution trigger, no user update, and no package install/removal—but they are workable.