Skip to main content
Glama
xici001

workflow-mcp

by xici001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to workflow-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Tool Server

      Krishna89287
      F
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that advertises tools with JSON schemas and executes tool calls safely, enabling AI agents to perform actions on real systems.
      -

    • FlowMCP

      PeterGreenAppliedAI
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that exposes deterministic workflows as tools, allowing small models to reliably orchestrate APIs and other MCP servers with minimal parameters.
      2
      21 npm
      2
      MIT

    • Agent Construct

      ai-mcp-garage
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server implementation that standardizes how AI applications access tools and context, providing a central hub that manages tool discovery, execution, and context management with a simplified configuration system.
      13
      -

    • promptflow-mcp

      RozuniFix72
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server for prompt template management, enabling storage, versioning, search, and rendering of prompt templates via MCP tools.
      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

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct operation: list_templates (enumerate), get_template_info (inspect contract), run_template (sync execute), run_template_async (async execute), get_task_status (poll). The sync/async pair is clearly differentiated by explicit timeout guidance in the descriptions, so no realistic misselection.

    Naming Consistency4/5

    All names follow a clean verb_noun snake_case pattern (list/get/run/get). Minor inconsistency: list_templates uses a plural noun while get_template_info uses singular, and 'info'/'status' suffixes differ slightly, but this is readable and predictable.

    Tool Count5/5

    Five tools is well-scoped for a template-consumer/executor server, with each tool earning its place (discovery, inspection, sync exec, async exec, polling). No redundant or filler tools.

    Completeness4/5

    Covers the full discover-inspect-execute-monitor lifecycle, including an async path for long-running templates. Minor gap: no cancel/abort operation for a running async task, which could strand agents waiting on a hung task.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources