Skip to main content
Glama
duynghien

n8n-custom-mcp

by duynghien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to n8n-custom-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-n8n

      lyzetam
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for n8n workflow automation, enabling management of workflows, executions, credentials, tags, users, and webhooks via an MCP-compatible client.
      MIT

    • mcp-n8n-builder

      spences10
      A
      license
      A
      quality
      D
      maintenance
      🪄 MCP server for programmatic creation and management of n8n workflows. Enables AI assistants to build, modify, and manage workflows without direct user intervention through a comprehensive set of tools and resources for interacting with n8n's REST API.
      10
      28 npm
      86
      MIT

    • n8n-mcp

      Siddharth0903
      A
      license
      B
      quality
      D
      maintenance
      A 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.
      43
      1
      MIT

    • n8n-MCP

      mohsin-zaheer
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides AI assistants with access to documentation, schemas, and operations for over 535 n8n workflow automation nodes. It enables models to understand, create, and manage n8n workflows through natural language by connecting to the n8n API.
      77,070 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

    B3.1/5.0

    Scored across 31 tools

    Disambiguation3/5

    Most tools target distinct resources and actions, but there is notable overlap among the analysis tools: lint_workflow and suggest_workflow_improvements both check error handling, hardcoded values, and loops, while validate_workflow_credentials and test_credential both validate credential validity. Detailed descriptions help, but an agent could easily select the wrong validation tool.

    Naming Consistency5/5

    All 31 tools follow a consistent snake_case verb_noun pattern, such as list_workflows, create_credential, restore_workflow, and diff_workflow_versions. Even longer names like export_workflow_as_template and validate_workflow_structure remain predictable and readable.

    Tool Count2/5

    31 tools is above the 25+ threshold and feels heavy for a single MCP server. While the n8n administration scope is broad, several validation, linting, suggestion, and backup tools could be consolidated without losing core capability.

    Completeness4/5

    The tool surface covers workflow CRUD, activation, execution, validation, linting, templates, backups, credentials, and node schemas, so agents have no major dead ends in the primary n8n workflow lifecycle. Minor gaps remain around execution lifecycle operations, such as retrying or deleting executions, and there is no workflow tagging or categorization support.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources