Skip to main content
Glama
leonardosepulvedat

mcp-n8n

by leonardosepulvedat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to mcp-n8n

No user-submitted related servers found.

    Related Servers

    • n8n MCP Server

      Shravan1610
      A
      license
      B
      quality
      D
      maintenance
      Enables users to manage workflows, monitor executions, and perform administrative tasks in n8n through natural language conversations with Claude. It provides over 40 tools to control self-hosted or cloud n8n instances via the Model Context Protocol.
      42
      61 npm
      MIT

    • n8n MCP Server

      Ospray-creator
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables management of n8n workflow automations through natural language, supporting creation, execution, updates, and deletion of workflows, along with node discovery and execution status monitoring.
      MIT

    • n8n Workflow Builder MCP

      salacoste
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to create, manage, and monitor n8n workflows through natural language using AI interfaces like Claude and Cursor. It supports multi-instance environments and provides tools for workflow lifecycle management, execution monitoring, and tag organization.
      25 npm
      232
      MIT

    • n8n Workflow Builder

      Schimmilab
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI-powered building, optimization, debugging, and management of n8n workflows directly from Claude. Features workflow analysis, execution monitoring, security audits, drift detection, and intelligent error debugging with best practices guidance.
      1
      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

    C2.9/5.0

    Scored across 61 tools

    Disambiguation3/5

    Most tools map cleanly to a resource and action, but a few boundaries blur: n8n_update_workflow vs n8n_update_workflow_partial, n8n_get_workflow_template vs n8n_search_public_templates, and the various workflow listing variants can lead agents to pick the wrong one. Descriptions help, but the overlap is real.

    Naming Consistency4/5

    Nearly all tools follow the n8n_verb_noun pattern with predictable list/get/create/update/delete groups. Minor deviations like n8n_workflow_health (no verb), n8n_debug_last_error, and the plural n8n_create_users keep it from being fully consistent.

    Tool Count2/5

    61 tools is far above the 25+ threshold and feels heavy for an agent-facing surface. The n8n domain is broad, but several utilities such as the workflow list vs summary, update vs partial update, and snapshot/backup/export tooling could be consolidated.

    Completeness3/5

    Workflows, executions, tags, variables, users, and projects have solid CRUD/lifecycle coverage. However, credentials are missing list/get/update operations, and source control only supports pull, leaving notable gaps for a full n8n management server.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources