throng
Related Servers
Alternatives to throng
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables launching and supervising local Codex and Claude Code agent sessions and one-shot tasks, exposing run, list, stop, and output operations over MCP with session-scoped permissions and sandbox controls.54,779 npmMIT
- AlicenseBqualityBmaintenanceEnables 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
- AlicenseAqualityDmaintenanceWraps Claude Code as tools for MCP clients, enabling autonomous coding tasks via a 4-tool lifecycle with session management, async polling, and permission controls.459 npm20MIT
- AlicenseAqualityDmaintenanceEnables AI agents to interact programmatically with Claude Code CLI, managing sessions, streaming outputs, and handling permission requests.711 npm1MIT
- 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
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code and Claude Desktop to delegate coding tasks to any model available in OpenCode while Claude remains the orchestrator, planning work, reviewing diffs, and running tests. Supports synchronous and async delegation, model selection, session continuation, and permission-aware execution.MIT
TDQS
Scored across 6 tools
Most tools are clearly distinct: cancel, list, run, send, and wait target different operations. However, run_thronglet and send_message both initiate turns and return the same result shape, which could cause slight confusion without careful reading of descriptions. The overlap is manageable but not perfectly clean.
All tool names use snake_case and follow a consistent verb_noun pattern (cancel_thronglet, list_harnesses, list_thronglets, send_message, run_thronglet, wait_thronglet). There are no mixed conventions or vague verbs. The naming is predictable and readable.
Six tools is well-scoped for a coding agent session manager. Each tool covers a distinct lifecycle operation without redundancy or bloat. The count is neither too thin nor too heavy for the apparent purpose.
The set covers core session lifecycle operations: start (run_thronglet), continue (send_message), wait (wait_thronglet), cancel (cancel_thronglet), and list sessions/harnesses. Minor gaps exist, such as no explicit tool to delete or archive a session, and no dedicated single-session status retrieval beyond wait_thronglet with a timeout. These are workaround-able but not fully complete.