Skip to main content
Glama

Related Servers

Alternatives to sim-lab

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables external MCP clients like Claude Desktop, Claude Code, Cursor and Zed to hand work to a local crew of AI agents that plan, write, check and fix code in a folder, while also acting as an MCP client that can use their tools. Runs locally with user-supplied keys, approval-gated commands, diffable and undoable runs.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables ML researchers to manage experiments across local and remote AutoDL GPU instances, including experiment creation, training launch, run polling, and report writing via Claude Code.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coordinating Claude Code and Codex on one machine by fanning out tasks to multiple agents in isolated Git worktrees, comparing results, picking a winning candidate, and handing off work between harnesses. It provides MCP stdio tools, a CLI, and a local loopback web cockpit.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple Claude sessions on the same PC — Claude Desktop chats, Cowork tasks and Claude Code — to coordinate as siblings, sharing full context, splitting work and handing tasks to each other. Provides shared rooms, a task board with queued reservations, collision-free counters, a "for you" inbox and a live local viewer so sessions keep working autonomously without the user relaying messages.
      MIT

    TDQS

    A3.6/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool maps to a distinct resource and action: catalogue for discovery, experiment CRUD/run (list/get/run/save), campaign batching, tune for search, run inspection (list/get/compare), and plan listing/saving. run_experiment, run_campaign, and tune all execute but are cleanly separated by scope (one, several variants, parameter search).

    Naming Consistency4/5

    Strong verb_noun snake_case pattern throughout (list_experiments, get_experiment, run_campaign, compare_runs, save_plan). Two outliers—catalogue and tune—lack a noun and break the pattern, but the convention is otherwise predictable and readable.

    Tool Count5/5

    12 tools is well-scoped for a simulation lab covering discovery, experiment lifecycle, campaign execution, tuning, run inspection, and plan authoring. Every tool earns its place with no redundant surface.

    Completeness4/5

    Core lifecycle is covered: discover, define, run, batch, tune, inspect, and compare. Minor gaps exist—no delete for experiments/plans, no single get_plan (only list_plans), and no run cancellation—but these are workable around for most workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data