Skip to main content
Glama
DrBalls

n8n MCP Server

by DrBalls
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to n8n MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-n8n

      RPGMais
      A
      license
      A
      quality
      F
      maintenance
      Provides comprehensive management of n8n instances, including workflows, data tables, tags, credentials, users, and more, through 43 tools.
      43
      32 npm
      1
      MIT

    • n8n Automation MCP Server

      SohailShabbir867
      F
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to fully automate n8n instances via 34 MCP tools, covering workflow creation, execution debugging, credential management, environment variables, tags, and user administration through natural language.
      34
      1
      -

    • n8n MCP Server

      sonnd08
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides AI assistants with direct access to the n8n automation platform to manage and execute workflows, variables, and credentials. It features 18 integrated tools that allow for seamless automation management via the Model Context Protocol.
      54 npm
      3
      MIT

    • n8n MCP Server

      nikolausm
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with n8n workflow automation instances through the REST API. Supports workflow management, execution control, tag organization, execution history monitoring, and webhook management.
      19
      54 npm
      5
      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 52 tools

    Disambiguation4/5

    The tools are well-differentiated by resource type (workflow, credential, project, tag, variable, execution, user) and action (create, get, list, update, delete, activate, deactivate, run, retry, stop, export, import, duplicate, transfer, generate_audit, check_connection, get_active_webhooks, get_node_types, source_control operations). There is minimal overlap, with clear boundaries between similar tools like n8n_delete_execution and n8n_delete_executions, which are distinguished by single vs. bulk operations. The only minor ambiguity is between n8n_update_workflow and n8n_update_workflow_tags, but their descriptions clarify the scope.

    Naming Consistency5/5

    All tools follow a consistent snake_case naming pattern with the prefix 'n8n_' followed by a verb (e.g., create, get, list, update, delete) and a noun (e.g., workflow, credential, project). This pattern is applied uniformly across all 52 tools, making them predictable and easy to understand. There are no deviations in style or convention.

    Tool Count2/5

    With 52 tools, the count is excessive for an MCP server, making it overwhelming and difficult for agents to navigate effectively. While n8n is a complex automation platform, the tool surface could be more streamlined by grouping related operations or reducing redundancy. This high number exceeds typical well-scoped ranges (3-15 tools) and approaches the extreme mismatch threshold.

    Completeness5/5

    The tool set provides comprehensive coverage for managing n8n instances, including full CRUD operations for core resources (workflows, credentials, projects, tags, variables, users, executions), lifecycle management (activate/deactivate, run/retry/stop), import/export, auditing, source control, and utility functions. There are no obvious gaps; agents can perform all essential operations without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources