Skip to main content
Glama
orieg

orieg/yaml-workflow

by orieg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to orieg/yaml-workflow

No user-submitted related servers found.

    Related Servers

    • Atlas

      Ctrl1CandV
      A
      license
      A
      quality
      A
      maintenance
      A local, auditable multi-model workflow engine that lets you define YAML graphs for orchestrating LLM agents across vendors, with MCP tools for validation, dry-runs, execution, and human approval, all fully observable in a local web interface.
      8
      3
      Apache 2.0

    • mcpGraph

      TeamSparkAI
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables orchestration of MCP tool calls through declarative YAML-defined directed graphs with data transformation, conditional routing, and observable execution flows.
      65 npm
      22
      MIT

    • workflow-mcp

      qddfxp
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables deterministic, resumable workflow automation through DAG step graphs, boolean gate branching, automatic parallel execution, and in-step agent loops with sandboxed file and command tools.
      7 npm
      1
      MIT

    • skill-workflow-runner

      hjamet
      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

    • ZooGent

      bepunk
      A
      license
      Not graded
      quality
      C
      maintenance
      Lightweight AI agent orchestrator with built-in Architect AI, enabling users to automate tasks by describing them via chat or Claude Code + MCP, with multi-team isolation.
      47 npm
      3
      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

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing workflows, validating a file, previewing execution without side effects, and actually running a workflow. There is no ambiguity between them.

    Naming Consistency5/5

    All tool names are in snake_case and follow a verb_noun pattern (list_workflows, validate_workflow, dry_run_workflow, run_workflow). The use of 'dry_run' as a compound verb is consistent with the pattern.

    Tool Count4/5

    Four tools is on the lower end but perfectly scoped for this server's purpose—covering discovery, validation, preview, and execution. Each tool earns its place without any redundancy.

    Completeness5/5

    The tool surface covers the full lifecycle of using a YAML workflow: list available workflows, validate a file, preview effects, and execute. There are no obvious gaps for the stated domain of running existing workflows.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources