SSyncDev

Warapp-mcp Server

war.app (Warzone) game advisor — games, maps, bonuses, routes, live board, picks, turns and chat

Local serverstdio

What is the Warapp-mcp Server?

Warapp-mcp is an MCP integration. War.app (Warzone) game advisor — games, maps, bonuses, routes, live board, picks, turns and chat.

Packages and local setup

The published npm package is @chrischall/warapp-mcp, version 0.5.0. Its declared MCP transport is stdio.

The package declares WARAPP_EMAIL (required): The email address you sign in to war.app with.; WARAPP_API_TOKEN (required): Your war.app API token, from https://war.app/API/GetAPIToken while signed in.; WARAPP_WS_PORT: fetchproxy bridge concentrator port for the live-game tools. Defaults to the fleet-shared 37149.; WARAPP_ENV_FILE: Optional dotenv file with WARAPP_EMAIL / WARAPP_API_TOKEN (default ~/.config/warapp-mcp/.env); WARAPP_TRANSPORT: How the live-game tools reach war.app: auto (default, direct when a session is linked else the browser bridge), direct, or fetchproxy.; WARAPP_SESSION_FILE: Where the linked direct-transport session is stored (default /session.json). Local-only, file mode 0600.; WARAPP_PLAYER_RECORD: The name-free cross-game record of how other players kept truces (salted hashes, no names). On by default; set off to turn it off.; WARAPP_PLAYER_PROFILE: Opponent profiling: counts of what each opponent did on the turns your boards showed (gameplay only, no names or chat), kept per game, and folded name-free (salted-hash keys) into counts across finished games. On by default; set off to turn it off..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.5.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
WARAPP_EMAILThe email address you sign in to war.app with.Yes
WARAPP_API_TOKENYour war.app API token, from https://war.app/API/GetAPIToken while signed in.Yes
WARAPP_WS_PORTfetchproxy bridge concentrator port for the live-game tools. Defaults to the fleet-shared 37149.Check documentation
WARAPP_ENV_FILEOptional dotenv file with WARAPP_EMAIL / WARAPP_API_TOKEN (default ~/.config/warapp-mcp/.env)Check documentation
WARAPP_TRANSPORTHow the live-game tools reach war.app: auto (default, direct when a session is linked else the browser bridge), direct, or fetchproxy.Check documentation
WARAPP_SESSION_FILEWhere the linked direct-transport session is stored (default /session.json). Local-only, file mode 0600.Check documentation
WARAPP_PLAYER_RECORDThe name-free cross-game record of how other players kept truces (salted hashes, no names). On by default; set off to turn it off.Check documentation
WARAPP_PLAYER_PROFILEOpponent profiling: counts of what each opponent did on the turns your boards showed (gameplay only, no names or chat), kept per game, and folded name-free (salted-hash keys) into counts across finished games. On by default; set off to turn it off.Check documentation