Skip to main content
Glama
ricardocairo

n8n-mcp

by ricardocairo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to n8n-mcp

No user-submitted related servers found.

    Related Servers

    • n8n-mcp

      AdvancedNolik22-dev
      A
      license
      A
      quality
      B
      maintenance
      Provides AI assistants with comprehensive access to n8n node documentation, properties, operations, templates, and workflow validation for building and managing n8n workflows.
      7
      141,724 npm
      MIT

    • n8n-MCP

      clanker25
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to access comprehensive n8n node documentation, properties, operations, workflow templates, and community nodes, allowing them to design, build, and validate n8n workflows through natural language.
      141,724 npm
      MIT

    • n8n-MCP

      markmocasa-boop
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with comprehensive access to n8n node documentation, properties, and operations for building and managing automation workflows.
      141,724 npm
      MIT

    • n8n-MCP

      88-888
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides AI assistants with comprehensive access to n8n's 525+ workflow automation nodes, including documentation, properties, operations, and 2,500+ templates. Enables creating, validating, and managing n8n workflows through natural language.
      141,724 npm
      -

    • n8n MCP Server

      Nielsen642
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to access comprehensive n8n node documentation, properties, and operations for building workflow automations.
      141,724 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

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct entity and action: nodes vs templates, search vs get vs validate. Even get_node and get_template are clearly separate resources, and tools_documentation is the only meta-tool, so there is no ambiguity.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun snake_case pattern (search_nodes, get_template, validate_workflow). tools_documentation breaks the pattern slightly—it should be something like get_tools_documentation—but the rest are very consistent.

    Tool Count5/5

    Seven tools is well within the ideal range and each tool earns its place. The set covers search, retrieval, and validation without unnecessary redundancy.

    Completeness5/5

    The server covers the full workflow lifecycle for an n8n assistant: discovering nodes, retrieving templates, fetching node details, validating individual node configs, validating full workflows, and accessing documentation. No obvious dead ends or missing operations.

    Resources