Skip to main content
Glama
tonytanglab

cursor-relay-mcp

by tonytanglab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to cursor-relay-mcp

No user-submitted related servers found.

    Related Servers

    • Agent Bus MCP

      rickkeller
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables durable, least-privilege handoff of bounded tasks from a local producer to a configured MCP worker, with atomic claim, complete, and fail operations under expiring leases.
      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.
      198 npm
      MIT

    • cursor-mcp

      qmediat
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to run Cursor CLI agent prompts with any model the installed CLI offers, continue existing sessions, and list available models and sessions. Adds guarded execution with concurrency limits, timeouts, cancellation, and operator-gated auto-approval so multiple models can be run in parallel.
      5
      632 npm
      1
      MIT

    • LinkedRun

      ShiroganeKaichou
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to submit and manage persistent, dependency-aware task graphs with immutable artifacts, resource reservations, durable event streaming, and retryable process execution over MCP.
      12
      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.4/5.0

    Scored across 14 tools

    Disambiguation3/5

    Several tools target run observation and reading state (open_run, get_run, read_events, read_run_progress, view_run, wait_run), and their boundaries are subtle despite descriptions clarifying snapshot vs. streaming vs. live panel. Core run-control and auth tools are distinct, but the monitoring cluster invites misselection.

    Naming Consistency4/5

    Almost all tools use snake_case verb_noun-style names such as list_models, start_run, and wait_run, with only doctor as a noun exception. The convention is predictable and readable.

    Tool Count4/5

    14 tools is reasonable for auth, model discovery, workspace authorization, run lifecycle, and monitoring. The monitoring surface is somewhat heavy, but each tool maps to a defined operation.

    Completeness4/5

    The surface covers configuration/auth, model discovery, run creation, continuation, cancellation, listing, event reading, and progress monitoring. Explicit cleanup/prune/delete for persisted runs is missing, but the core lifecycle is otherwise covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources