Rutherford MCP Server
Related Servers
Alternatives to Rutherford MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables a primary AI coding assistant to delegate tasks to multiple specialized CLI agents (such as Gemini, Claude, Codex, and Cursor) in parallel from a single prompt, sharing project context across all of them. It aggregates their outputs into one synthesized response while relying on the user's existing CLI tools and subscriptions.-
- FlicenseNot gradedqualityAmaintenanceEnables a primary AI coding assistant to delegate tasks to specialized sub-agents in parallel, share project context, and synthesize their responses. It uses existing local CLI tools and API subscriptions to coordinate Codex, Claude, Cursor, and Gemini without extra cost.-
- FlicenseNot gradedqualityNot gradedmaintenanceOrchestrates multiple AI models (Gemini, OpenAI, Claude, local models) within a single conversation context, enabling collaborative workflows like multi-model code reviews, consensus building, and CLI-to-CLI bridging for specialized tasks.-
- FlicenseNot gradedqualityAmaintenanceEnables a primary AI coding assistant to delegate tasks to specialized local CLI agents such as Gemini, Claude, Codex, and Cursor, coordinating shared context, parallel execution, and synthesized responses from within an IDE.-
- FlicenseNot gradedqualityAmaintenanceEnables a primary AI coding assistant to delegate tasks in parallel to specialized CLI-based agents such as Gemini, Claude, Codex, and Cursor, sharing the same project context across all of them. It then aggregates and synthesizes their outputs into a single response, using existing local tools and subscriptions with no extra configuration.-
- AlicenseBqualityFmaintenanceEnables orchestrating multiple AI CLI agents (Claude Code, Codex, Gemini CLI, Copilot CLI) through a unified MCP interface for task delegation, cross-agent comparison, and specialized tools like code review and debugging.149 npm14MIT
TDQS
Scored across 19 tools
Most tools target clearly distinct operations: delegation, multi-agent consensus, debate, jobs, setup, and diagnostics. The main overlap is deliberate: `plan` is a specialized `delegate`, and `review` is a specialized read-only `consensus`, while `list_jobs`, `activity`, `job_status`, and `job_result` are closely related but explicitly contrasted in their descriptions.
All names use consistent snake_case with no camelCase or casing chaos. They are mostly readable and predictable, though some are bare verbs/nouns (`delegate`, `consensus`, `doctor`) rather than uniformly verb_noun.
Nineteen tools is borderline heavy for a single server, driven by separate surfaces for delegation, deliberation, jobs, agent diagnostics, setup, discovery, and panels. Each tool has a role, but the set is broad enough that an agent must navigate many adjacent operations.
The surface covers the main lifecycle well: agent discovery/authentication/health, roles, delegation, planning, consensus, debate, review, job polling/cancellation/continuation, and setup. Minor gaps remain around explicit panel CRUD/session management, but core workflows are not dead-ended.