llm-sparring
Related Servers
Alternatives to llm-sparring
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceLets coding agents such as Claude Code, Kiro CLI, and Antigravity CLI call the locally installed Codex CLI as an independent debate partner, with per-question model and reasoning-effort selection. Supports asynchronous polling of long replies, cancellation of a turn, read-only project exploration, and resuming saved conversations in later sessions.6125 npm1MIT
- AlicenseAqualityDmaintenanceEnables adversarial collaboration between Claude and GPT for automated code critique, verification, and multi-round debate to improve output quality.3MIT
- AlicenseAqualityBmaintenanceTwo AIs. One answer. ChatGPT and Claude discuss with each other until they agree, through your own signed-in CLIs: no API keys. Both read your project (never change it) and search the web. Plugin for Claude Code, Codex, Claude Desktop and the ChatGPT app.8377 npm6MIT
- AlicenseAqualityBmaintenanceEnables Claude Code and OpenAI Codex CLI to act as bidirectional partners by letting each ask the other for code review, explanations, planning, performance analysis, and implementation help. It also provides background job tools for starting, observing, waiting on, and cancelling delegated tasks.6116 npm1MIT

LLM Council MCPofficial
AlicenseNot gradedqualityDmaintenanceEnables Claude Code to consult external LLMs (GPT, Gemini) through multi-turn sessions for second opinions, parallel consultations, and web-grounded research.MIT- AlicenseAqualityDmaintenanceEnables Claude Code to delegate tasks to OpenAI's Codex CLI (GPT-5.4) with structured execution traces, parallel execution, session persistence, and adversarial code review.15MIT
TDQS
Scored across 5 tools
The debate_* tools form a clear sequential lifecycle (open → turn → verdict) and are hard to confuse with anything else. The only real overlap is between gpt_critique and synthesize, since both ship text to GPT and return structured feedback; their descriptions distinguish 'rank my issues' from 'give an independent answer and merge', but an agent could still reach for the wrong one on a borderline request.
The debate_open/turn/verdict trio is a clean, predictable noun_action pattern. However gpt_critique (provider-prefixed) and synthesize (bare verb) break that pattern, so the set mixes three naming conventions even though each name is individually readable.
Five tools is well matched to a 'second opinion' server: one critique tool, a three-step debate protocol that genuinely needs separate open/turn/end calls, and one synthesis tool. Nothing feels padded or missing at the count level.
The debate surface is complete (start, iterate, conclude) and both one-shot tools return actionable output. Minor gaps: no way to list or resume existing debate_ids, and no explicit abort/close path for a debate abandoned mid-round, which could leave dangling state.