OMP Tandem
Related Servers
Alternatives to OMP Tandem
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides coding agents with structured planning, persistent project memory, automated verification, and safety permission controls through MCP tools, enabling better planning, context retention, self-checking, and guarded execution.6 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides MCP tools for AI-powered code review, research, and book writing via a fleet of coding agents.Apache 2.0
- FlicenseAqualityCmaintenanceExposes pi as a sub-agent for MCP-capable coding assistants, enabling task dispatch, messaging, and interactive dialog handling via tools like pi_dispatch, pi_send, and pi_respond.91-
- FlicenseNot gradedqualityBmaintenanceEnables Claude Code to delegate work to persistent oh-my-pi (omp) subagents via an MCP server with 7 tools (spawn, send, output, status, list, stop, prune), wrapping omp RPC mode with enforcement hooks for descriptive agent naming, model configuration, denylists, write-scope ownership, and cooperative locking.-
- AlicenseNot gradedqualityAmaintenanceEmpower any MCP-compatible AI Agent(MCP Client) with engineering-grade capabilities to understand, modify, run, and deliver real-world code repositories.993Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI coding assistants to manage persistent memory, search project context, generate tests, review architecture, and orchestrate workflows through 15 MCP tools, enhancing context-aware code generation.-
TDQS
Scored across 20 tools
Several tools have genuinely overlapping territory: tandem_start vs tandem_continue (both begin task/goal execution), tandem_review vs tandem_review_run (both produce review bundles/runs), and tandem_result vs tandem_reply vs tandem_wait (all mediate interacting with a running task). The very detailed descriptions help an agent differentiate them, but the boundaries are subtle enough that misselection is plausible.
Every tool uses the same tandem_ prefix with snake_case verb_noun or noun forms (tandem_start, tandem_result, tandem_reply, tandem_cancel, tandem_list). Minor noun-only names like tandem_channel or tandem_scope remain fully readable and predictable within the established convention.
Twenty tools is on the heavy side for the rubric's 16-25 'borderline heavy' band. The domain is genuinely complex (task orchestration, review lifecycle, context sharing, channels, diagnostics), so most tools earn a place, but the surface is larger than an agent can comfortably hold.
The lifecycle is well covered: starting, continuing, waiting, reading results, replying, cancelling, listing, plus review, findings, artifacts, context publication/export/import, channels, receipts, and diagnosis. Few obvious dead ends exist, though some operations (e.g. task mutation nuances) lean on one large multi-action tool rather than dedicated endpoints.