muster
Related Servers
Alternatives to muster
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to spawn and control Codex CLI and Claude Code sessions on the host machine, with session management and filesystem access.4MIT
- FlicenseNot gradedqualityAmaintenanceMCP server for programmatic lifecycle management of Claude Code sessions, supporting list, create, read, send, fork, wait, and interrupt operations.1 npm1-
- FlicenseNot gradedqualityAmaintenanceAgent orchestration system that runs coding-agent sessions (Claude Code, Codex) with policy mediation and exposes tools via MCP.-
- AlicenseBqualityAmaintenanceEnables MCP clients to delegate prompts to locally configured Codex, Antigravity, OpenCode, and Claude Code agents, fetch live model catalogs and quotas, and maintain stateful multi-turn sessions with selectable tool policies.6MIT
- FlicenseNot gradedqualityBmaintenanceEnables 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-
- AlicenseAqualityAmaintenanceEnables delegating coding tasks to Claude Code, Codex or OpenCode agents over the Agent Client Protocol, running a prompt to completion in a chosen directory and returning the agent's result. Also supports follow-up messages, background turns, session listing, cancellation, and harness discovery with configurable permission policies.6807 npm2MIT
TDQS
Scored across 5 tools
Each tool targets a distinct lifecycle action: run launches, list enumerates, output reads, title renames, and stop terminates. Overlap is minimal, with output and list only differing by scope.
All tool names are lowercase single-word commands (run, title, list, output, stop), giving a consistent imperative style. No mixed conventions or prefixes/suffixes are present.
Five tools is compact and appropriate for a session/task orchestration server, covering launch, inspection, output retrieval, naming, and termination without redundancy. No obvious over- or under-scoping.
The surface covers the core lifecycle: launch (run), list/inspect (list), read output (output), rename (title), and stop. It may lack a direct message/send tool for interacting with reachable sessions, but core operations are present.