Skip to main content
Glama
carlosjperez

n8n-mcp-connector

by carlosjperez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to n8n-mcp-connector

No user-submitted related servers found.

    Related Servers

    • n8n MCP Server

      leonardsellem
      A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with n8n workflows through natural language, supporting actions like listing, creating, updating, executing and monitoring workflows.
      329 npm
      1,635
      MIT

    • n8n-MCP

      czlonkowski
      A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol server that provides AI assistants with comprehensive access to n8n node documentation, properties, and operations for effective workflow automation.
      28
      96,726 npm
      22,906
      MIT

    • 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.
      96,726 npm
      34
      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

    B3.2/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions: nodes, connections, workflows, and executions. create_webhook slightly overlaps with create_node since a webhook is a node type in n8n, but the descriptions clarify the specialized intent.

    Naming Consistency5/5

    All tools use a consistent snake_case verb_noun pattern such as create_node, update_node, list_workflows, and execute_workflow. Minor plural/singular variations are conventional and readable.

    Tool Count5/5

    12 tools is well within a reasonable range for an n8n connector, covering key node, connection, workflow, and execution operations without obvious bloat. Each tool appears to earn its place.

    Completeness3/5

    Core node and connection operations are present, but the workflow lifecycle is incomplete: there is no create_workflow, update_workflow, or delete_workflow, and no update_connection. These gaps may force agents to work around missing fundamental workflow management operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources