Skip to main content
Glama
najikay

sim-lab

by najikay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to sim-lab

No user-submitted related servers found.

    Related Servers

    • projtool

      zhyx12
      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

    • agentbus

      vatsal191201
      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

    • Ouroboros

      Q00
      A
      license
      B
      quality
      A
      maintenance
      Local-first Agent OS that wraps Claude Code, Codex CLI, and other coding agents in a replayable Seed → Ledger → Runtime contract, driven by an interview → seed → execute → evaluate → evolve workflow loop.
      34
      16,680 PyPI
      6,172
      MIT

    • Claude Code ⇄ Slack

      Palgenius
      F
      license
      A
      quality
      C
      maintenance
      Lets you @mention a bot in a Slack channel or DM to send work to a local Claude Code session and watch it run, with live self-updating turn cards, threaded answers, progress checklists and a per-channel inbox with read cursors. It runs entirely on your machine over Slack Socket Mode—no tunnel or public IP—routes misdelivered messages to the right project, and masks credentials in anything it posts back.
      7
      -

    • Agent World

      arpan1221
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a local, vendor-agnostic control room where coding agents can be assigned tasks, exchange scoped messages, submit claims, and have work reviewed across different models, with a voxel-world interface for inspecting sessions and evidence.
      4
      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.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

    ActivityMaintained
    ResponsivenessNo issues

    Resources