Skip to main content
Glama
BrutalSystems

muster

by BrutalSystems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to muster

No user-submitted related servers found.

    Related Servers

    • pokeclaw

      madebydia
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP clients to spawn and control Codex CLI and Claude Code sessions on the host machine, with session management and filesystem access.
      4
      MIT

    • LightsOut

      filipeagg
      F
      license
      Not graded
      quality
      A
      maintenance
      Agent orchestration system that runs coding-agent sessions (Claude Code, Codex) with policy mediation and exposes tools via MCP.
      -

    • pi-agent-mcp

      a809384377
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP hosts like Claude Code and Codex to spawn, manage, and interact with persistent, reusable Pi coding-agent sessions, supporting task dispatch, status checks, and session lifecycle control.
      2 npm
      -

    • claude-code-mcp

      xihuai18
      A
      license
      A
      quality
      D
      maintenance
      Wraps Claude Code as tools for MCP clients, enabling autonomous coding tasks via a 4-tool lifecycle with session management, async polling, and permission controls.
      4
      34 npm
      20
      MIT

    • Claude Code Manager WAN

      medelmouhajir
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables ISLI agents and MCP clients to dispatch natural-language coding and terminal tasks to a locally-installed Claude Code CLI, supporting both one-shot execution and persistent sessions with workspace and security controls.
      -
    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 4 tools

    Disambiguation5/5

    Each tool targets a distinct concern: launching a run, listing resources, stopping a run, and reading output. There is no meaningful overlap between actions.

    Naming Consistency4/5

    All tools use short, lowercase, single-word names in an imperative style, which is consistent overall. 'output' is slightly noun-like compared to 'run', 'list', and 'stop', but it still reads as a clear command.

    Tool Count5/5

    Four tools is a tight, well-scoped set for a small agent/session management server. Each tool has a clear role with minimal redundancy.

    Completeness4/5

    The core lifecycle of launch/list/stop/read-output is covered. Minor gaps exist around explicit status checking, session-level output, or cleanup/removal, but agents can likely work around these with list and stop.

    Resources