A TypeScript-based MCP server for inter-session terminal orchestration, pseudo-terminal (PTY) lifecycle management, ring-buffered I/O multiplexing, and reactive event hooking across polyglot execution harnesses.
menager-mcp provides 13 tools with complete input schemas and descriptions. Naming follows verb_noun convention (session_*, agent_*) and is clear. However, descriptions are terse (10-50 chars for most tools), parameter descriptions are sparse or missing, and output schemas are entirely undocumented. No error handling guidance, no recovery hints, and no parameter validation rules stated in descriptions. Tool composition is reasonable (single responsibility), but lacks idempotency guarantees and confirmation patterns for destructive operations.
Send a follow-up message to an agent session. Writes into the running PTY, or resumes via opencode run --session when the PTY already exited.
Spawn an opencode agent run (opencode run) inside a managed PTY. Native multi-agent orchestration: each agent gets its own sessionId for routing follow-ups via agent_send/agent_fork.
Kills and removes a session, freeing its memory.
Awaits a specific regex pattern on the session stream with optional automated reply.
Returns metadata and status for a specific session.
Lists all active and completed sessions managed by the server.
Output schemas completely undocumented. No tool returns a documented response structure. LLMs cannot plan downstream calls or extract required fields.
Descriptions are terse (10-50 chars). Most lack WHEN to use, WHAT it returns, and prerequisites. Baseline for A+ tools is 50-200 chars with actionable context.
Parameter descriptions missing or minimal. 'pattern' in session_hook, 'status' in session_prune, 'format' in agent_spawn lack context. LLMs cannot infer meaning from names alone.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
Force deletes sessions (default: only 'exited' sessions).
Reads buffered output from the target session.
Resizes the PTY terminal dimensions.
Sends a POSIX signal to the target session process.
Spawns a new child PTY session.
Blocks and waits for a session to exit, returning its exit code.
Injects keystrokes, commands, or escape sequences into the session's standard input.
No error handling guidance. Tools like session_close and session_signal are destructive but provide no recovery hints, confirmation patterns, or actionable error messages.
No idempotency guarantees or confirmation patterns. Destructive operations (session_close, session_prune, session_signal) lack dry-run or confirmation support, risking accidental data loss.