agent-discussion-mcp
Connects to OpenAI-compatible chat completion endpoints for running role-based agents, proposals, critiques, and judge verdicts.
Provides a test suite runnable with pytest for the MCP server's development.
Persists agent profiles and append-only session audit events (proposals, critiques, verdicts, errors) in a SQLite database with WAL mode.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@agent-discussion-mcprun a discussion with the architect, DBA, and security agents on our schema design"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
agent-discussion-mcp
Model Context Protocol (MCP) server for reusable role-based agents, structured multi-agent debates, peer critiques, and independent judge consensus.
Supports Solo execution with tag routing and bounded Discussion mode: independent proposals, parallel critique, an independent judge, bounded revision rounds, and SQLite event logs with WAL mode.
See dsaa.md for the original project vision and architectural notes (Russian).
β¨ Features
Role Profiles ("Gems"): Reusable agent profiles with custom roles, system prompts, model overrides, routing tags, temperature, and output token limits.
Solo Execution (
run_solo): Run single-agent tasks directly by agent name or automatically route by tag matching without guessing on ambiguity.Structured Discussion Mode (
run_discussion):Independent Proposals: Participating agents draft proposals in parallel without seeing other agents' work.
Peer Critique: Agents review all proposals and produce structured critiques (strengths, concerns, questions).
Independent Judge: A designated judge evaluates the blackboard and decides consensus vs. no-consensus with a defensible final answer and confidence score.
Bounded Revision: If no consensus is reached, agents revise their proposals addressing critiques for up to
max_rounds.
Shared Token Budget: Dynamic token reservation and settlement preventing token overrun in concurrent calls.
Event Sourcing & Audit Log: Monotonic append-only SQLite log (
session_events) recording all proposals, critiques, verdicts, and errors in WAL mode.Transient Error Resilience: Exponential backoff with jitter on network/HTTP status errors (408, 409, 429, 5xx) and fallback verdict if a judge fails.
Client Progress Reporting: Native MCP progress notifications (
ctx.report_progress) during multi-round debates.
Related MCP server: Executive Cortex MCP
π Quick Start
Installation & Running
# Clone the repository
git clone https://github.com/ewanni/agent-discussion-mcp.git
cd agent-discussion-mcp
# Install dependencies with uv
uv sync --extra test
# Configure provider settings
export AGENT_DISCUSSION_API_KEY="your-openai-or-compatible-key"
export AGENT_DISCUSSION_BASE_URL="https://api.openai.com/v1"
export AGENT_DISCUSSION_MODEL="gpt-4o-mini"
# Run the MCP server over stdio
uv run agent-discussion-mcp(Note: legacy API_AGENT_* environment variables and api-agent-mcp CLI binary are also supported for backwards compatibility).
π οΈ MCP Tools & Resources
Tools
create_agent: Register a new agent profile (name, role, system_prompt, model, tags, temperature, max_output_tokens).update_agent: Modify fields of an existing profile.list_agents: Inspect all registered profiles (omits private system prompts / credentials).run_solo: Execute a task with a named agent or tag-routed agent.run_discussion: Run a bounded debate with 2β5 participant agents, a separate judge, round limit (1β5), and a shared completion token budget.
Resources
agent://profiles/{name}: Read a specific agent profile configuration as JSON.
βοΈ Configuration & Environment Variables
Variable | Fallback (Legacy) | Default | Description |
|
|
| API key for OpenAI-compatible endpoint |
|
|
| Base URL for |
|
|
| Default model for agents without custom override |
|
|
| SQLite database path for profiles and session audit events |
|
|
| HTTP request timeout in seconds |
π§ͺ Testing & Development
Run the test suite with pytest:
uv run pytestπΊοΈ Roadmap
β Solo mode and profile registry
β Bounded Discussion with independent proposals, critics, judge, blackboard, and output-token budget
β³ Subagent verification and resumable background execution for long-running discussions
π License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Durable agent-to-agent handoffs and shared scratchpad for multi-agent workflows.
Memory, reflection and safety for AI agents. Hosted or local, no vector database.
177Build, validate, and deploy multi-agent AI solutions from any AI environment.
- ParleyOAuthdev.weldra
Coordination hub for AI coding agents: message teammates, ask humans, audit every event.
Related MCP Servers
- AlicenseAqualityDmaintenanceMulti-advisor debate, institutional memory, trust scoring, and cognitive governance for AI agents, all running locally.515 npm1MIT
- -licenseNot gradedqualityNot gradedmaintenanceEnables local task planning and execution with DAG-based plans, multiple reasoning methods, and persistence for AI agents.-
- AlicenseNot gradedqualityAmaintenanceRun dynamic, multi-agent workflow scripts β agent(), parallel(), pipeline() β over real coding agents (Claude Code and OpenAI Codex), with deterministic journaling, resume, token budgets, and git-worktree isolation.7Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables multi-agent code review and iterative improvement loop using different LLM backends, with deterministic scoring and audit trail.5MIT