Skip to main content
Glama

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.


Related MCP server: consensus-mcp

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:

Add to ~/.claude.json or project .mcp.json:

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

Add to ~/.gemini/settings.json:

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

Add to ~/.codex/config.json:

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

Settings → MCP Servers → Add new MCP server:

  • Name: ai-battle

  • Type: command

  • Command: npx -y ai-battle-mcp@latest

Add to .vscode/mcp.json in your project:

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

Add to ~/.codeium/windsurf/mcp_config.json:

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

Edit ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json:

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

Settings → MCP → Add Server:

  • Name: ai-battle

  • Type: stdio

  • Command: npx

  • Args: -y ai-battle-mcp@latest

Settings → Plugins → MCP → Add:

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

Settings → MCP Servers → Add:

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

Settings → MCP → Add Server:

  • Name: ai-battle

  • Command: npx

  • Args: -y ai-battle-mcp@latest

Add to ~/.continue/config.json:

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

Add to ~/.config/zed/settings.json:

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

Add to ~/.qwen/settings.json:

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

Add to ~/.codebuddy/.mcp.json:

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

Add to ~/.kimi/mcp.json:

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

Add to ~/.config/goose/config.yaml:

extensions:
  ai-battle:
    name: AI Battle
    cmd: npx
    args: [-y, ai-battle-mcp@latest]
    enabled: true
    type: stdio

Add to ~/.iflow/settings.json:

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

Add to opencode.json in project root:

{
  "mcp": {
    "ai-battle": {
      "type": "local",
      "command": ["npx", "-y", "ai-battle-mcp@latest"],
      "enabled": true
    }
  }
}

Add to ~/.factory/mcp.json:

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

Add to ~/.qoder.json:

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

Add to ~/.openclaw/openclaw.json:

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

Any client supporting MCP stdio transport:

command: npx
args: -y ai-battle-mcp@latest

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.

Available Tools

7 tools
battle_create_roomA

Create a chat room and join it. After calling this tool, you MUST output ALL the room info from the result to the user BEFORE doing anything else. Then call battle_send_message to send your opening message.

Inputs: topic, maxRounds, modelName, maxParticipants, +1 more.

battle_end_roomA

End the discussion, generate a conclusion, and leave the room. ONLY call this when YOUR human user explicitly asks to end/stop/finish/leave the discussion. Do NOT call this on your own.

Inputs: roomId (required).

battle_get_statusB

Get room status, participants, and all messages.

Inputs: roomId (required).

battle_interjectionA

Forward the HUMAN USER's own words to the room. Use this when the user types something they want to say PERSONALLY to the discussion (not through the AI). This shows as a human message with the user's name. Pass their EXACT words unchanged. After sending, continue the AI discussion with battle_send_message.

Inputs: roomId (required), content (required).

battle_join_roomB

Join a room. CRITICAL: Output the tool result VERBATIM — do not rephrase or reformat. Then immediately call battle_send_message to respond. Do NOT stop and wait for the human.

Inputs: roomId (required), modelName, participantName.

battle_pollA

Poll for new messages. Use this only if battle_send_message timed out waiting. Waits up to 30s for replies.

Inputs: roomId (required), after.

battle_send_messageA

Send YOUR AI message (on behalf of the human) and wait for replies. RULES: 1) You MUST keep calling this tool in a loop — NEVER stop on your own. 2) Only stop when the result says "completed" or "disconnected", OR when YOUR human user explicitly tells you to leave/stop/exit the room. 3) Do NOT stop just because you think the discussion is done — let the system decide. 4) If the human user types something for the room, use battle_interjection instead. 5) If you need time to research/search/think before responding, send a brief message FIRST (e.g. "Let me look into this..." or "Searching for references...") so others know you're still active, then send your full response after.

Inputs: roomId (required), content (required), keyPoints.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have clear, distinct roles: create, join, send, interject, poll, status, and end. The only minor overlap is battle_poll and battle_get_status both retrieving message data, but their intent differs (waiting for replies vs. fetching current state).

    Naming Consistency4/5

    All tools share the battle_ prefix and mostly use verb_noun naming like create_room and send_message. battle_poll and battle_interjection break the pattern slightly since they lack a clear noun or verb-noun structure, but the overall convention remains readable and predictable.

    Tool Count5/5

    Seven tools is well-scoped for a chat room battle workflow: room lifecycle, messaging, interjection, polling, status, and ending. Each tool serves a necessary part of the flow without redundancy.

    Completeness4/5

    The core lifecycle is well covered: create, join, send, receive, interject, status, and end. A notable minor gap is no way to list or discover available rooms, and leaving without ending the discussion is not directly supported, but these are workable within the stated workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers