Llm Council vs Forge

Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
🤖 Coding Agents
F
Forge
TT-Wang
🤖 Coding Agents
SummaryMulti-LLM deliberation with anonymized peer review. Runs a 3-stage council: parallel responses → anonymous ranking → synthesis. Based on Andrej Karpathy's LLM Council concept.Structured planning, parallel execution in git worktrees, and deep validation for Claude Code. Turns a one-line objective into a validated DAG of modules executed by worker agents, each self-checked and cross-module-reviewed before merge-back. 7 MCP tools: validate, validateplan, memoryrecall, memorysave, iterationstate (per-run scoped, with stagnation/velocity/oscillation detection), forgelogs, sessionstate. Stdio-only. Zero telemetry.
Quality signal25/100 (Emerging)28/100 (Emerging)
Install pathRemote · highnpx · low
Engagement 2 0 0 8 0 0 0 37
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView Llm CouncilView Forge
More alternatives to Llm CouncilMore alternatives to ForgeCoding Agents category

Other servers like Llm Council