Skip to main content
Glama
tuanknguyen

Workflow MCP Server

by tuanknguyen

Related Servers

Alternatives to Workflow MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to execute multi-step Standard Operating Procedures step by step, with enforcement of completion at each step, making LLM behavior predictable and auditable.
      5
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables deterministic, step-by-step execution of YAML-defined skills and workflows for AI agents, with progressive disclosure of active-step instructions and tools. It manages workflow state, conditional DAG transitions, loops, and persistent sessions via start_workflow, next_step, and end_workflow.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides LLMs with structured workflow guidance and next-step instructions for development procedures, ensuring consistent practices across projects.
      5
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to navigate users through pre-defined decision trees by submitting answer labels, returning deterministic next instructions without extra LLM calls. Supports domain-independent procedural workflows with state tracking, handling of unknown responses, and a read-only Web UI.
      MIT

    TDQS

    B3.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Tools are largely distinct, focusing on framework creation, session management, and step execution. The only potential confusion is between complete_step and execute_current_step, but their descriptions clarify different actions: completing vs executing steps.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_framework, list_sessions, complete_step). The pattern is uniform and predictable.

    Tool Count5/5

    With 8 tools, the server covers core workflow operations without being excessive. The number is appropriate for a workflow management server's typical needs.

    Completeness3/5

    The tool set covers basic lifecycle (create framework, start, execute steps, manage sessions), but lacks tools for editing workflow definitions, listing steps, or pausing/aborting sessions, which are notable gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues