Skip to main content
Glama
ShiroganeKaichou

LinkedRun

by ShiroganeKaichou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to LinkedRun

No user-submitted related servers found.

    Related Servers

    • mcp-job-queue

      tommypj
      A
      license
      A
      quality
      D
      maintenance
      Enables MCP clients to submit long-running jobs that are executed safely in isolated child processes with a durable SQLite queue, configurable timeouts, retries with backoff, and backpressure.
      5
      MIT

    • codex-router

      rixzkiye
      A
      license
      Not graded
      quality
      B
      maintenance
      A durable MCP control plane for starting, observing, steering, continuing, cancelling, and handing off long-running coding agents, with bounded MCP calls and persistent worktrees.
      6 npm
      MIT

    • superagentic

      narimannemo
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that lets agents claim, work on, and finish units of work in a coordinated fleet, with lease and heartbeat protection, plus tools for orchestrators to define work and collect results.
      Apache 2.0
    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.5/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: submission (single vs batch), task state management (get, list, cancel, retry), artifact resolution, graph query, event streaming, and resource status. No two tools appear to overlap in purpose.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (submit_task, get_task, list_artifacts, watch_events, etc.). Minor exception like resource_status is still readably aligned with the convention.

    Tool Count5/5

    With 12 tools, the surface is well-scoped for a task orchestration server. Every tool has a clear role and the count feels appropriate for the domain without redundancy or bloat.

    Completeness5/5

    The set covers the full lifecycle: task submission (single and DAG), state inspection, cancellation/retry, artifact access, dependency graph queries, event consumption (pull and push), and resource monitoring. No obvious gaps for common workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources