Skip to main content
Glama
allanbchancery

n8n MCP Server

by allanbchancery
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to n8n MCP Server

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-ops

      Redsf
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for operating an n8n instance, enabling AI assistants to monitor failing workflows, check health, and list executions. Read-only by default with an opt-in write mode for workflow activation.
      MIT

    • n8n-free-mcp

      jserna0001
      A
      license
      A
      quality
      C
      maintenance
      Free and open-source MCP server for managing n8n workflows, executions, and tags via n8n's API. Enables workflow creation, activation, debugging, and deletion from any MCP client.
      12
      2
      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
    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.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: workflow management (list/get/activate/deactivate/execute), execution management (list/get/stop), and instance info. No two tools overlap in purpose, and descriptions clearly delineate manual execution from activation and stopping a specific execution from deactivating a workflow.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (e.g., list_workflows, get_workflow, activate_workflow). The single get_instance_info slightly extends to verb_noun_noun but remains fully predictable and readable.

    Tool Count5/5

    Nine tools is well-scoped for an n8n management server, covering key workflow and execution lifecycle operations without redundancy. Each tool earns its place and the set is neither thin nor heavy.

    Completeness3/5

    The surface covers listing, retrieving, activating, deactivating, and executing workflows, plus execution monitoring and instance health. However, it lacks create, update, and delete operations for workflows, which are fundamental for a workflow automation platform and will cause agent failures when trying to build or modify workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources