Skip to main content
Glama

Related Servers

Alternatives to n8n-guard

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      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
    • A
      license
      B
      quality
      C
      maintenance
      Safe MCP server and CLI tool for testing, scoring, and inspecting n8n workflows. Features 19 tools for workflow testing, execution traces, tiered scoring, and a built-in node catalog with 800+ node types. Designed with safety-first approach: no credential management, no secrets lifecycle, no auto-fix loops.
      19
      1
      MIT
    • 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
    • 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
    • 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
      29 npm
      86
      MIT

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each check targets a distinct n8n failure mode: instance inventory, datastore growth, stuck executions, retention, and git drift. guard_run is explicitly an aggregate sweep, so its overlap with the individual checks is intentional and clearly described.

    Naming Consistency5/5

    All tool names use lower_snake_case and concise check-oriented identifiers. guard_run is slightly more action-oriented than the others, but the naming convention remains consistent throughout.

    Tool Count5/5

    Six tools is well-scoped for a read-only n8n monitoring server. Each tool maps to a meaningful check or aggregate runner, with no filler.

    Completeness4/5

    The surface covers the core monitoring lifecycle: instance discovery, DB health, stuck executions, retention, git drift, and a resilient aggregate run. Minor gaps remain around explicit alerting/escalation or worker/queue health, but the main guard workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues