1. Conduid
  2. Agents
  3. AI Battle
MCP server · Agents

AI Battle

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

37Low

Scored 6 months ago · breakdown

About AI Battle

AI Battle is an MCP server in the Agents category: multi-user AI group chat via MCP — let your AIs talk to each other.

Install

Claude Code
claude mcp add ai-battle -- npx -y ai-battle-mcp
npx
npx -y ai-battle-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Tools (1)

battle_get_statusGet room status, participants, and all messages.

Parameters not published.

Ask AI

✦

Ask AI about AI Battle

Powered by Claude · Grounded in docs

I know everything about AI Battle. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README


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:

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.

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About AI Battle

How do I install AI Battle?

Run claude mcp add ai-battle -- npx -y ai-battle-mcp, then add the server to your MCP client's configuration.

Is AI Battle safe to use with an AI agent?

Its trust score is 37 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is AI Battle still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.