Bicameral
Related Servers
Alternatives to Bicameral
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables Claude to collaborate with Gemini for code reviews, second opinions, and iterative software development. It facilitates multi-step workflows including PRD creation and code generation through an AI orchestration framework.27 npm1MIT
- AlicenseAqualityBmaintenanceEnables orchestrating a multi-AI workflow where Claude Code implements a task, Codex reviews the changes read-only, and Claude reconciles the feedback, then runs tests and waits for user approval before committing.51MIT
- AlicenseAqualityBmaintenanceEnables Claude Code to submit code, diffs, plans, and security or edge-case questions to Codex, Gemini, and GPT-OSS for read-only review, verifying each quoted line against the real files so fabricated findings are filtered before Claude reads them. It also runs multi-family councils that surface agreement, falls back across models when quotas run out, and supports optional hooks that block git push until edits have been reviewed.104MIT
- AlicenseBqualityDmaintenanceEnables Codex to manage a local Claude Code companion through MCP, implementing a dual-agent workflow where Codex handles reasoning and review while Claude Code performs engineering tasks.181MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to escalate complex analysis to Gemini for multi-model reasoning over large codebases, logs, and traces, with capabilities for execution-flow tracing, cross-system impact analysis, performance bottleneck detection, hypothesis testing, and iterative AI-to-AI dialogue.MIT
- AlicenseAqualityDmaintenanceEnables adversarial collaboration between Claude and GPT for automated code critique, verification, and multi-round debate to improve output quality.3MIT
TDQS
Scored across 10 tools
Each tool maps to a distinct phase of the bicameral workflow: pre-flight introspection, plan critique, diff review, run lifecycle, and per-step execution control. Despite some review/check overlap, the described targets (working tree diff vs. applied step edit vs. draft plan) are clearly separated.
All tools share the consistent bicameral_ prefix and snake_case style, and most use verb-like names (begin, execute, check, review, finish). The noun-style names status and stats deviate slightly from the otherwise action-oriented pattern, but the overall scheme is predictable and readable.
Ten tools is well-scoped for a multi-stage editing workflow. Each lifecycle phase has a dedicated tool, and there is no sense of redundancy or unnecessary bloat.
The tool surface covers the full workflow: gather context, review before planning, critique a plan, start a run, execute steps, self-check edits, accept/reject changes, finish, and inspect stats. There are no obvious dead ends or missing lifecycle operations for the stated purpose.