Skip to main content
Glama
Sign In
Highway MCP

Highway MCP

by rodmena-limited
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Highway MCP

No user-submitted related servers found.

    Related Servers

    • TGP MCP Server

      TGP MCP Serverofficial

      tecadrise-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM agents to execute gated, multi-step workflows in a fixed order, with engine-checked tasks and controlled stage unlocking. It exposes workflow state, task completion, and human approval controls through MCP.
      4 npm
      MIT

    • bizops

      Yassine-64
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover, execute, and inspect actions across business systems through three compact MCP tools, backed by server-side policy, single-use human approvals, and durable idempotent execution that prevents duplicate side effects.
      1
      MIT

    • agent-workflows-mcp

      ndmxjp
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to run declarative agents and DAG workflows as plain tools, with parallel nodes, review loops, and per-run least-privilege sandboxing.
      13 npm
      MIT

    • clef-use

      kotori0919
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP agents to run, continue, observe, check status of, and abort bounded GUI automation tasks through a shared local runtime with visual detection and deterministic input.
      Apache 2.0

    • Workflow MCP

      zero36kai
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables users to submit goals via MCP so a host agent can generate scripts, coordinate subagents, monitor execution stages, recover interrupted runs, and deliver reusable artifacts.
      6 npm
      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.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: 'approve' handles pending actions, 'get_status' tracks run progress, 'run_goal' starts a new run, and 'schedule_goal' sets up recurring runs. No overlap or ambiguity.

    Naming Consistency4/5

    Three tools follow a clear verb_noun pattern (get_status, run_goal, schedule_goal), but 'approve' omits the noun. The pattern is mostly consistent and readable, with a minor deviation.

    Tool Count5/5

    Four tools is well-scoped for the server's purpose of managing durable agent runs with approvals. Each tool is essential and the set is concise without being sparse.

    Completeness3/5

    The tools cover starting, scheduling, checking status, and approving runs, but missing cancellation or deletion capabilities (e.g., cancel_run, delete_schedule) are notable gaps that agents may need.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Resources