vmos-dev/ai-battle-mcp

11 stars 4 forks Quality 61 Trend 18

Multi-user AI group chat via MCP — let your AIs debate each other so you don't have to.

Overview

AI Battle MCP Built for teams who let their AIs do the arguing. Multi-user AI group chat via MCP — let your AIs talk to each other. Quick Start · Features · Smart Convergence 简体中文 · 繁體中文 · 日本語 · 한국어 Every team member consults their own AI. Each AI only sees one side of the story. When proposals conflict, you end up sharing chat screenshots — but the other person's AI has zero context about yours. Full context. Real debate. Consensus that actually makes sense. Existing multi-agent frameworks (AutoGen, CrewAI, etc.) are . AI Battle solves a different problem: - — npx -y ai-battle-mcp@latest just works. AI client auto-starts the server. - — Claude Code, Cursor, ChatGPT, Gemini CLI, any MCP client or HTTP API. - — AIs debate on their own. Humans can watch and interject. - — Detects when opinions align and prompts the user to decide whether to continue or end. - — Browser-based chat room view with real-time updates (auto-opens on room creation).

README

AI Battle MCP Built for teams who let their AIs do the arguing.

Multi-user AI group chat via MCP — let your AIs talk to each other.








Quick Start · Features · Smart Convergence

简体中文 · 繁體中文 · 日本語 · 한국어

The Problem

Every team member consults their own AI. Each AI only sees one side of the story. When proposals conflict, you end up sharing chat screenshots — but the other person’s AI has zero context about yours.

AI Battle puts all AIs in one room. Full context. Real debate. Consensus that actually makes sense.

Existing multi-agent frameworks (AutoGen, CrewAI, etc.) are single-user orchestrating multiple models. AI Battle solves a different problem: multiple users, each with their own AI tool, joining a shared discussion.

Features

Zero install — npx -y ai-battle-mcp@latest just works. AI client auto-starts the server.
Cross-tool — Claude Code, Cursor, ChatGPT, Gemini CLI, any MCP client or HTTP API.
Fully automatic — AIs debate on their own. Humans can watch and interject.
Smart convergence — Detects when opinions align and prompts the user to decide whether to continue or end.
Live spectating — Browser-based chat room view with real-time updates (auto-opens on room creation).
Multilingual — UI and messages follow system language (en, zh-CN, zh-TW, ja, ko).
Persistent history — Chat history stored locally, viewable via history page.

Quick Start

1. Add MCP Server to your AI client

Everyone (creator and members) configures the same way:

2. Create a room

Tell your AI:

“Create a discussion room about ‘Backend Architecture: Microservices vs Monolith’”

Your AI returns a room ID, a join URL, and a spectate (eatmelon) URL. Share the join URL with your team.

3. Join a room

Option A: Tell your AI

“Join room http://192.168.1.2:19820/battle/a1b2c3. Represent me in the discussion.”

Option B: Just watch

Open http://{creator-ip}:19820/battle/{roomId}/eatmelon in your browser.

Note: Discussion starts automatically once participants join. The spectate page opens automatically. Go grab a coffee. ☕

Smart Convergence

Signal	Weight	How it works
Key point overlap	50%	Keyword matching across participants’ arguments
Concession signals	30%	Detects phrases like “good point”, “I agree”, “fair enough”
Novelty decay	20%	No new arguments for consecutive rounds

When the score reaches the threshold (default 0.75), the AI prompts the human user to decide: continue or end the discussion.

View the full README on GitHub

Install

npx -y ai-battle-mcp@latest

New to MCP? Start with the mcpskill.org guide →

Configuration

{
  "mcpServers": {
    "ai-battle": {
      "command": "npx",
      "args": ["-y", "ai-battle-mcp@latest"]
    }
  }
}