Skip to main content
Glama
FarazHayder

n8n-mcp-guard

by FarazHayder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to n8n-mcp-guard

No user-submitted related servers found.

    Related Servers

    • n8n MCP Server

      masseater
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI models to manage n8n workflow automation through a standardized interface. Supports creating, reading, updating, and deleting workflows with comprehensive access to workflow nodes, connections, and configurations.
      12 npm
      MIT

    • n8n Manager for AI Agents

      czlonkowski
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage n8n workflow automation instances through tools for workflow CRUD operations, execution monitoring, and webhook triggering. It facilitates programmatic interaction with n8n instances via the n8n API with AI-optimized descriptions and error handling.
      62
      MIT

    • n8n MCP Server

      JBrightmanAI
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage n8n workflows and executions, including creating, updating, deleting, activating, deactivating, and executing workflows, as well as listing and retrieving execution details.
      54 npm
      MIT

    • n8n-mcp-server

      eric050828
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to programmatically control n8n via natural language for automated workflow creation, modification, and execution management.
      1
      -
    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

    A3.9/5.0

    Scored across 5 tools

    Disambiguation4/5

    n8n_plan_workflow_update is effectively a superset of n8n_diff_workflow and n8n_backup_workflow (it reads, backs up, and diffs), so boundaries overlap. The descriptions do a good job disambiguating — diff is read-only and stores nothing, backup is standalone, plan orchestrates the guarded update — so an agent can mostly pick correctly.

    Naming Consistency5/5

    Every tool follows the same n8n_ prefix plus snake_case verb_noun pattern (diff_workflow, list_test_clones, get_workflow, backup_workflow, plan_workflow_update). Fully predictable and consistent.

    Tool Count4/5

    Five tools is lean and each earns its place within a guarded-update workflow. It is slightly thin because the commit stage is referenced but absent from the listed surface.

    Completeness2/5

    The descriptions repeatedly reference n8n_apply_workflow_update as the commit step, yet it is not in the tool set, leaving the guarded-update lifecycle without its terminal operation. Test-clone management is also only half-present (list exists, no create/cleanup), creating dead ends for agents.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources