code-quorum
Related Servers
Alternatives to code-quorum
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables multi-model LLM council reviews and parallel sidecar conversations within Claude, allowing Claude to orchestrate structured reviews from various AI models and fold their responses back into the session.686 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to read each other's conversation history read-only and sanitized, so you can continue work across different tools without re-explaining context.MIT
- FlicenseNot gradedqualityBmaintenanceAllows users to manage multiple remote AI coding agents from a single Claude Code session, with a controlled execution model where operations require moderator approval.-
- FlicenseAqualityAmaintenanceEnables coding agents to perform workspace-confined file operations, read-only Git inspection, and structured shell commands, while requiring out-of-band human approval for mutations and external executions and maintaining an audit trail.143-
- AlicenseNot gradedqualityCmaintenanceEnables independent code review and multi-round discussions between Claude and Codex, allowing either agent to inspect project files read-only and exchange feedback without modifying the repository.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to consult a multi-model deliberation council before irreversible, high-stakes decisions, returning structured architectural decision records with consensus and dissenting risks.-
TDQS
Scored across 6 tools
Each tool has a clearly distinct function: planning, brainstorming, validation, code review, research, and result retrieval. There is no overlap in purpose; descriptions reinforce the boundaries.
All tools follow a uniform 'q_' prefix with an action verb (plan_start, brainstorm_start, validate_start, review_start, research, await). The two non-start tools still share the prefix and verb style, making the pattern predictable.
Six tools is well-scoped for a code-quality council suite: four distinct run types plus research and a blocking retrieval. Each tool earns its place without redundancy or bloat.
The core lifecycle (start runs, retrieve results) is fully covered, and research supports the workflow. Minor gaps exist—no job-listing or cancellation tool—but agents can work around them by awaiting each job, so the surface remains practical.