Skip to main content
Glama
Souzix76

n8n-workflow-tester-safe

by Souzix76
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to n8n-workflow-tester-safe

No user-submitted related servers found.

    Related Servers

    • n8n-mcp

      Siddharth0903
      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

    • 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

      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-ops-mcp

      lidless-labs
      A
      license
      A
      quality
      A
      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
      17 npm
      1
      MIT

    • n8n MCP Server

      illuminaresolutions
      A
      license
      B
      quality
      D
      maintenance
      An MCP server enabling secure interaction with n8n workflows, executions, and settings via the Model Context Protocol, designed for integration with Large Language Models (LLMs).
      33
      49 npm
      118
      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.2/5.0

    Scored across 19 tools

    Disambiguation3/5

    Most tools have clear distinct purposes (e.g., list_* vs get_* vs create_*), but some overlap exists: list_triggers and list_node_types both list node-like entities; get_execution and get_execution_trace both fetch execution data though with different levels of detail; evaluate_workflow_result and test_workflow are similar, with the former adding evaluation. This could cause occasional misselection.

    Naming Consistency4/5

    The naming follows a consistent pattern of verb_noun (e.g., list_triggers, connect_nodes, get_workflow_summary, create_workflow), with almost all using snake_case and standard CRUD verbs. The only minor deviation is the presence of both 'list_triggers' and 'list_node_types' which are similar but still follow the pattern, and 'connect_nodes' is descriptive. Overall, very consistent.

    Tool Count4/5

    The server has 19 tools, which is at the upper edge of the 'well-scoped' range (3-15) but not excessive given the breadth of workflow management, catalog exploration, testing, and execution retrieval functionality. It feels slightly heavy but each tool addresses a specific need in the workflow lifecycle.

    Completeness4/5

    The tool set covers major workflow lifecycle operations (create, read, update, delete) along with comprehensive testing and execution analysis, and catalog exploration. Minor gaps exist: there is no explicit tool for 'disconnect_nodes' or 'remove_node', and no tool for listing all workflows (only get by ID), which could be a dead end for agents needing overview. But the core domain is well-covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources