Skip to main content
Glama
mckinleymedia

McFlow

by mckinleymedia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to McFlow

No user-submitted related servers found.

    Related Servers

    • 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.
      45 npm
      232
      MIT

    • n8n MCP Server

      Octavian-Labs
      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

      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

    B3/5.0

    Scored across 27 tools

    Disambiguation3/5

    Most tools have distinct purposes, but some overlap exists. For example, 'list' and 'deployed' both list workflows but in different contexts (project vs n8n instance), which could cause confusion. Similarly, 'analyze' and 'validate' both involve workflow inspection but with different focuses, potentially leading to misselection.

    Naming Consistency4/5

    The naming is mostly consistent with a verb-based pattern (e.g., 'activate', 'add_node', 'create', 'deploy'), but there are minor deviations like 'deployed' (past tense verb) and 'info' (noun). Overall, the naming is readable and follows a clear convention, with only a few inconsistencies.

    Tool Count2/5

    With 27 tools, the count is too high for a focused workflow management server. This many tools suggests feature bloat and can overwhelm agents, making it difficult to navigate and select the right tool efficiently. A more streamlined set of 10-15 tools would be more appropriate.

    Completeness5/5

    The tool set provides comprehensive coverage for n8n workflow management, including creation, deployment, execution, analysis, and maintenance. It covers the full lifecycle from 'create' to 'deploy' and 'execute', with additional tools for code extraction, tracking, and validation, leaving no obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources