The High Council
Related Servers
Alternatives to The High Council
- AlicenseAqualityDmaintenanceEnables role-based, multi-model AI orchestration by assigning specialized expert roles to a hybrid panel of local and cloud LLMs, generating unified advisory council reports for complex tasks.65 npm1MIT
Related Servers
- AlicenseAqualityDmaintenanceEnables structured multi-model AI planning sessions across multiple CLI coding tools, orchestrating independent planning, peer review, and final synthesis.161MIT
- AlicenseNot gradedqualityBmaintenanceEnables orchestrating a panel of frontier AI models that independently propose, critique, revise, and converge on a single agreed answer to a problem, using existing vendor subscriptions or API keys.15 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to run structured multi-persona debates over high-stakes decisions and merge their positions into an explainable consensus, complete with logged dissenting minority opinions. It runs as a zero-dependency Python MCP server or importable module, compatible with Claude Desktop, Cursor, and custom agent frameworks.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables external MCP clients like Claude Desktop, Claude Code, Cursor and Zed to hand work to a local crew of AI agents that plan, write, check and fix code in a folder, while also acting as an MCP client that can use their tools. Runs locally with user-supplied keys, approval-gated commands, diffable and undoable runs.AGPL 3.0
- AlicenseBqualityCmaintenanceEnables reusable role-based agents, solo execution, and bounded multi-agent discussions with independent proposals, peer critiques, judge consensus, revision rounds, token budgeting, and SQLite audit logging.5MIT
- FlicenseAqualityDmaintenanceEnables a host AI agent to trigger a multi-agent debate, running N-rounds where agents critique each other's answers, then synthesizes a consensus recommendation with ranked options.3-
TDQS
Scored across 23 tools
Most tools are distinguishable (run lifecycle vs. tree vs. contract vs. reporting), but several boundaries blur. `verdict_stats`, `metrics_report` and `spend_report` all return windowed aggregates derived from run folders with overlapping figures (amendment/withdrawal rates appear in two), and the family of two-call gate tools (`stop_decide`, `tree_decide`, `price_raise`, plus `submit_stage`, `repair_reply`) requires reading long descriptions to pick correctly.
Every name is snake_case, so the surface reads consistently. The only deviation is word order: most are verb_noun (`list_runs`, `start_run`, `pause_run`) but a few are noun_verb (`run_status`, `tree_status`, `contract_read`, `contract_amend`), which is a minor inconsistency rather than a real problem.
23 tools is at the heavy end for a single server, though the scope (harness runs, external stages, repairs, contracts, recursive trees, telemetry, pricing) is genuinely broad. A few could reasonably be folded together, notably the three windowed report tools and the near-identical quote/answer gate tools.
The lifecycle is well covered end to end: discover chains, price them, start, poll, pause, resume, read artifacts, answer external stages and repairs, plus contract and tree decision paths and spend/telemetry reporting. Minor gaps exist — there is no explicit cancel/abort of a run and no task listing alongside `write_task` — but agents can work around these.