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.23,029 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables any MCP-compatible client to run reusable, Markdown-defined coding agents (such as reviewers, test writers, or investigators) through a configurable coding CLI backend, returning results into the same conversation. Agent definitions and backend/model settings can be shared across clients, and sessions can persist across multiple calls for longer work.545 npmMIT
- 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.1931 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables an AI assistant to delegate coding tasks to local Codex or Claude Code CLIs, monitor their progress, read results, continue sessions, and browse the files in user-approved project workspaces. It exposes these capabilities over Streamable HTTP through a Cloudflare tunnel or locally over stdio, so a remote or cloud client can drive agents running on the user's own machine.45 npm1MIT
- 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.440 npm20MIT
- AlicenseAqualityDmaintenanceEnables AI agents to interact programmatically with Claude Code CLI, managing sessions, streaming outputs, and handling permission requests.76 npm1MIT
TDQS
Scored across 6 tools
Each tool maps to a clear, distinct operation: running a new agent, waiting on a session, sending a message to an existing session, cancelling, and two distinct listing tools (harnesses vs sessions). The run/send/wait/cancel lifecycle boundaries are well delineated.
Five of six tools follow a consistent verb_noun pattern (run_thronglet, wait_thronglet, cancel_thronglet, list_harnesses, list_thronglets). send_message breaks the suffix convention but is still clear and consistent in its verb-first style.
Six tools tightly cover the agent-session lifecycle (run, wait, message, cancel) plus discovery (list harnesses, list sessions). No bloat, no thin spots.
The full session lifecycle is covered: launch, observe, continue/steer, cancel, and both discovery surfaces. Background collection via wait_thronglet rounds out async workflows, leaving no obvious dead ends.