Skip to main content
Glama
ellmos-ai

n8n-manager-mcp

by ellmos-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to n8n-manager-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      12 npm
      86
      MIT

    • n8n-custom-mcp

      duynghien
      F
      license
      B
      quality
      C
      maintenance
      A full-power MCP server for n8n that enables AI agents to create, read, update, delete, and test workflows and credentials, including webhook testing, validation, and backup/versioning.
      31
      9
      -

    • mcp-n8n

      backsoul
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for integrating with n8n, enabling workflow automation and management through natural language.
      221 npm
      1
      MIT

    • n8n MCP Server

      allanbchancery
      A
      license
      B
      quality
      D
      maintenance
      MCP server for managing n8n workflows and executions. Enables listing, activating, deactivating, and executing workflows, as well as monitoring executions and instance health.
      9
      MIT

    • 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

    • 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.
      46,471 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.4/5.0

    Scored across 19 tools

    Disambiguation3/5

    Most tools are clearly separated by resource and action, but n8n_create_workflow and n8n_import_workflow are nearly identical in intent, and n8n_get_workflow vs n8n_export_workflow could easily be confused. The safety/manager tools are distinct but add a few overlapping informational surfaces.

    Naming Consistency4/5

    The n8n_ prefix and snake_case are consistent, and most tools follow a clear verb_noun pattern (list_workflows, activate_workflow, add_server). Minor deviations like n8n_safety_status and n8n_manager_history use noun phrases instead of get/list verbs, but they do not create real ambiguity.

    Tool Count3/5

    19 tools is on the heavy side (16-25 range), but the count is largely justified by the distinct subdomains: workflow CRUD, server management, backups, safety, and executions. It could be tighter by merging create/import and get/export, but the scope is coherent.

    Completeness4/5

    Workflow lifecycle, server connections, backups, and safety are well covered. Obvious gaps are minor: only list executions (no get/stop execution detail) and no backup deletion/rotation, but the core workflow-management surface is complete.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources