Skip to main content
Glama
czlonkowski

n8n-MCP

by czlonkowski
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to n8n-MCP

No user-submitted related servers found.

    Related Servers

    • n8n-MCP

      vredrick
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides AI assistants with comprehensive access to n8n node documentation, properties, and operations, enabling them to understand and work with n8n's 525+ workflow automation nodes.
      114,502 npm
      34
      MIT

    • n8n-mcp

      lucas-denzer
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides AI assistants with comprehensive access to n8n node documentation, properties, and operations, enabling them to build and validate workflows.
      114,502 npm
      MIT

    • n8n-mcp

      PCT-BR
      A
      license
      A
      quality
      B
      maintenance
      A Model Context Protocol (MCP) server that provides AI assistants with comprehensive access to n8n node documentation, properties, and operations, enabling them to understand and work with n8n's 2,175 workflow automation nodes.
      7
      114,502 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 28 tools

    Disambiguation3/5

    Most tools target distinct resources and actions, but validate_workflow and n8n_validate_workflow appear to serve the same purpose, creating ambiguity. There is also a minor potential confusion between n8n_test_workflow and n8n_executions, though descriptions differentiate them. The overall overlap is limited but significant enough to warrant a middle score.

    Naming Consistency2/5

    Naming is inconsistent: some tools have the 'n8n_' prefix (e.g., n8n_create_workflow) while others do not (e.g., validate_workflow, search_nodes). Even within the prefixed tools, patterns vary (e.g., n8n_workflow_versions is a noun phrase, while n8n_manage_credentials uses verb_noun). This mixed convention makes it harder to predict tool names and reduces consistency.

    Tool Count3/5

    With 28 tools, the set is at the upper edge of what is typical for a comprehensive MCP server. The broad scope of n8n automation (workflows, nodes, templates, credentials, agents, data tables, executions, evaluations) justifies a large surface, but the count is slightly heavy and could benefit from consolidation (e.g., merging the duplicate validation tools).

    Completeness4/5

    The tool set provides extensive lifecycle coverage for the n8n domain: workflow CRUD, validation, testing, execution monitoring, evaluations, template deployment, credential management, node exploration, and instance auditing. There are minor gaps (e.g., no direct workflow import/export), but overall the surface is quite complete for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources