Skip to main content
Glama
mattmaas

n8n-admin-mcp

by mattmaas

Related Servers

Alternatives to n8n-admin-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables full workflow automation management in n8n through 40+ tools covering workflows, executions, credentials, tags, variables, projects, users, and source control operations.
      52
      69 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Lets AI agents read, create, and update n8n workflows with a guarded two-phase plan-and-apply flow that backs up every change, refuses writes when the live workflow has moved, and verifies results by readback. Also supports rehearsing changes on trigger- and outbound-disabled test clones, so mutations to a live instance stay reviewable and reversible.
      5
      10 npm
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides ops-focused n8n tools for MCP-compatible agents, enabling listing, inspecting, triggering, validating, managing tags, running security audits, and safely editing n8n workflows with auto-backup and confirm gates.
      20
      11 npm
      1
      MIT
    • 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
    • A
      license
      A
      quality
      D
      maintenance
      Provides comprehensive management of n8n instances, including workflows, data tables, tags, credentials, users, and more, through 43 tools.
      43
      39 npm
      1
      MIT

    TDQS

    C2.8/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (get_workflow by ID vs get_workflow_by_name, patch_node_params vs update_workflow_json). Minor overlap between get_active_state and get_workflow (which likely returns active state anyway), and the four IO/schema tools form a related cluster, but descriptions keep them distinguishable.

    Naming Consistency5/5

    Consistent verb_noun snake_case throughout (get_policy, list_workflows, create_workflow, update_workflow_json, patch_node_params, rollback_workflow). Minor word-order variance in set_workflow_active does not break the predictable pattern.

    Tool Count4/5

    17 tools is reasonable for an admin server covering workflow CRUD, state management, backups, and IO schema analysis, though it sits near the upper end of comfortably scannable.

    Completeness4/5

    Strong lifecycle coverage: create, get, update, patch, activate, duplicate, rollback, export, and backup listing. No delete_workflow and no execution/run tooling, which are minor gaps for a full n8n admin surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues