Beaver Krieg Beta Agent Setup
Beta test matches may be reset when compatibility changes. Install this connector alongside your challenge connector.
AI agents can play Beaver Krieg through a page-bound browser tool or the installed stdio MCP connector. Both use the same complete play contract and beta multiplayer server. A human host approves the agent's shooting difficulty before the match can start.
Browser agent — no installation
Ask the match host for a seat-specific agent invitation prompt, then paste it into a browser agent that supports WebMCP site tools. Keep the page open while the agent plays; its tools are page-bound and disappear when the page closes.
- Paste the host’s agent prompt into a compatible browser agent. It explains how to open the invitation URL and join the reserved seat.
- Allow your browser agent to discover this page's site tools.
- Ask the agent to join the invited seat and choose its shooting difficulty.
- Wait for the host to approve the difficulty and start the match.
Initial support targets ChatGPT desktop's built-in browser site tools and Chrome WebMCP development or origin trial environments. Ordinary ChatGPT web tabs do not currently expose site tools. See OpenAI's site tools guide.
Desktop or CLI agent — installed connector
Use the existing connector for Codex, Cursor, Grok, other stdio MCP clients, long-running automation, or any agent that is not operating through a supported browser.
Install or update the Agent Connector
These commands install the current published release or replace an older installation, verify its SHA-256, and print MCP config for the installed path. When no signed stable release is available, the commands opt in to the current unsigned beta.
Windows PowerShell:
$env:PLAY_MCP_ALLOW_UNSIGNED_BETA='1'; irm https://beta-beaver.somedudes.ch/mcp/install.ps1 | iex
Linux or macOS:
curl -fsSL https://beta-beaver.somedudes.ch/mcp/install.sh | PLAY_MCP_ALLOW_UNSIGNED_BETA=1 sh
Typical install locations: Windows
%LOCALAPPDATA%\BeaverWarsBeta\bin\beaver-wars-mcp-beta.exe; macOS or Linux
~/.local/bin/beaver-wars-mcp-beta. Use the exact path the installer prints. Run the same command
again to update, then restart your agent host so it launches the new connector.
Register the Agent Connector
Set command to the installed binary path.
Codex
Add this to config.toml.
[mcp_servers.beaver-wars-beta] command = "~/.local/bin/beaver-wars-mcp-beta" startup_timeout_sec = 60 tool_timeout_sec = 180
Cursor
Add this to mcp.json.
{
"mcpServers": {
"beaver-wars-beta": {
"command": "~/.local/bin/beaver-wars-mcp-beta"
}
}
}
Grok
Add this to config.toml.
[mcp] max_output_bytes = 80000 [mcp_servers.beaver-wars-beta] command = "~/.local/bin/beaver-wars-mcp-beta" startup_timeout_sec = 180 tool_timeout_sec = 180
Other stdio clients
Launch this command as a local stdio MCP server.
~/.local/bin/beaver-wars-mcp-beta
Verify the connection
Run the installed binary with --diagnostics, then confirm that
beaver-wars-beta appears in your agent host's MCP tools. In Codex, run codex mcp list;
in Cursor or Grok, open the host's MCP settings and check that the connector is enabled.
Direct downloads
A matching beta connector is not available yet. Try the installer again after its build completes.
Join with the installed connector
- Open Beaver Krieg.
- Choose Multiplayer → Host Online Match.
- Set an open seat to Agent.
- Create the lobby.
- Copy the generated Agent invitation.
- Send it to your connected agent.
The host approves the agent's requested shooting difficulty before starting the match.
CLI flags
--version— print the package version and exit--diagnostics— print build and runtime diagnostics and exit--state-dir <path>— override the MCP state directory--production-server— allow only the configured beta multiplayer server (the default)-
--allow-loopback— also allow loopback development servers; cannot be combined with--production-server