The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Overwatch AIO MCP listing page.
English | 한국어
Query Overwatch 2 hero meta, public player stats, evidenced rankers, replay codes, official patch notes, and OWCS Korea data from an MCP client or a standalone agent skill. Both interfaces share ten read-only query operations and one SQLite store, with source URLs, observation dates, applied filters, cache state, and warnings preserved in every result.
Use it to compare heroes by region and rank, inspect public BattleTag profiles, retrieve curated ranker/replay evidence, connect patch changes to the available data period, and keep ranked statistics separate from esports metrics. Data is fetched only when requested; there is no scheduled collector, game-client automation, or private-profile access.
Built with Python 3.11+ and uv. Choose the skill, MCP server, or both.
Download releases · Distribution and registry guide
The legacy
v0.3.1MCPB keeps its originalOverwatch AIO MCPdisplay label. Version0.3.2and later use theOverwatch 2 Data MCP Serverlabel. Published release assets remain immutable.
| Interface | Use it for | Installation |
|---|---|---|
| Agent skill | Let Codex select queries and interpret evidence | Root skill and basic Python dependencies |
| MCP server | Call ow_* tools from an MCP client | The mcp extra and a client registration |
| Both | Choose the interface for each environment | Both installations can share one DB |
The skill runs its CLI independently. MCP does not require a skill installation. There is no automatic switching or duplicate execution.
Use the skills CLI for a project installation:
Add --global for a personal installation. Python and uv are needed for queries; Node.js is only needed for this installer. Use the skill directory reported by the installer.
Alternatively, ask Codex's Skill Installer:
Install the skill at the root of BK927/overwatch-aio as overwatch-aio-skill. Use the specified commit if I provide one.
For a pinned installation, use its script with your local Codex skills path:
The Skill Installer's default personal directory is ~/.codex/skills/overwatch-aio-skill. Invoke $overwatch-aio-skill or ask an Overwatch data question. Your database, caches, and development environment are not distributed.
Example requests:
MCPB-compatible clients supporting the UV runtime (manifest 0.4) can install the .mcpb file from a GitHub release. Dependencies are prepared at first launch. The source installation below works with clients using ordinary stdio or Streamable HTTP configuration.
Clone the repository or use an installed skill directory. Replace <project-directory> with its absolute path:
The default transport is stdio. Use the MCP JSON example or Codex TOML example. Codex also accepts:
For Streamable HTTP, start the server and connect to http://127.0.0.1:8765/mcp:
--host and --port change the listen address. The default is local-only 127.0.0.1:8765. The server has no built-in authentication; public hosting requires separate authentication and TLS. See the official Codex MCP guide for client configuration.
Keep --extra mcp in MCP launch commands and in uv sync commands for environments used by MCP. A plain uv sync can remove optional dependencies. The skill command stays unchanged.
| Environment | Status | Requirements and limits |
|---|---|---|
| Local desktop, stdio | Supported | Primary setup. The MCP client starts the process and the per-user SQLite database persists locally. |
| Local desktop, Streamable HTTP | Supported | Keep the default loopback bind unless an authenticated gateway is already in place. The server itself has no authentication. |
| Private home server | Operator-managed only | Use a service manager, one durable SQLite database, backups, and TLS plus authentication at a trusted reverse proxy or private network boundary. Do not expose the raw MCP port. |
| Raspberry Pi 4 Model B (2 GB RAM) | Tested hardware only | This records the hardware used for testing; it is not a recommendation, minimum requirement, or performance guarantee. |
| Google Compute Engine VM | Manual, unverified | A single VM with persistent disk can host the process, but no image or Terraform module is provided. Add TLS/auth, backups, single-writer DB ownership, and live upstream egress checks. |
| Cloudflare Tunnel | Possible operator-managed ingress; unverified | Tunnel can sit in front of a home server or VM after authentication is designed and tested. It is only ingress to that running host, not a Cloudflare Workers runtime. |
| Google Cloud Run | Unsupported as-is | Local SQLite is instance-local and the repository has no stateless container/storage design. External durable storage, authentication, and lifecycle changes are required. |
| Cloudflare Workers | Unsupported as-is | The current CPython MCP SDK and local SQLite design are not a Worker deployment. A port needs a stateless HTTP handler, Worker-native storage, and Worker-compatible authentication. |
Remote and home-server operation is only an operator deployment pattern—not a built-in hosted service. Binding to a non-loopback address is unsafe unless requests first pass through operator-controlled authentication and TLS and the database is stored durably.
| Tool | Capability |
|---|---|
ow_catalog | Heroes, maps, modes, tiers, regions, and supported filters |
ow_meta | Hero rates, map/tier/region comparisons, and stored observations |
ow_players_search | Public name and BattleTag search |
ow_player_get | Public profile and career/hero/role statistics |
ow_rankers_search | Locally curated, evidenced ranker registry |
ow_replays_search | Public replay discovery and stored evidence filters |
ow_replay_get | Replay details and recorded playback evidence |
ow_patches | Official patch notes and replay compatibility notices |
ow_esports | OWCS Korea hero, match, map, ban, and team data |
ow_status | Source health and stored coverage; offline by default |
Both interfaces publish the same input/output schemas. MCP returns the result as structuredContent and JSON text. Only status=error sets isError=true; empty, stale, and partial results retain their quality status and warnings. overwatch-aio-mcp schema exports the contracts. Use the local curation CLI for evidence writes.
Example filters.json:
Omitting the file supplies {}; --input-file - reads stdin. UTF-8 and UTF-8 BOM are supported. Stdout contains one JSON object; diagnostics go to stderr. Exit codes are 0 for ok/empty/stale/partial, 1 for execution failure, and 2 for invalid input. Inspect status and warnings. The query guide provides more examples in Korean.
DB selection is --db → OW_DB_PATH → ~/.overwatch-aio-skill/overwatch.db. The default is shared by processes running as the same user, independently of installation directories. Use absolute paths for existing records. Place --db after the executable name, before query or serve.
Existing caches, meta observations, players, replays, and manual evidence remain readable. SQLite WAL and transactions support concurrent skill writes and MCP reads. The old collection_jobs table is preserved but unused. There is no automatic database move or deletion. History contains observations made on request; unobserved periods are not backfilled. Cached responses do not create new observations. Replay recheck flags from invalidation notices update when patches are queried. HTTP cache retention is bounded to 256 entries, 64 MiB, and seven days.
The repository is BK927/overwatch-aio; the Python distribution and skill remain overwatch-aio-skill. Existing skill commands work unchanged. Older MCP users can keep overwatch-aio-mcp serve after updating their path and adding --extra mcp. Point --db at the old data/overwatch.db explicitly if needed.
ASIA mean the Korean server?No. ASIA is a provider region label, not proof of a Korean match server. OWTICS KOREA is also a provider grouping; results keep those labels distinct from evidenced player identity.
No. ow_rankers_search searches the locally curated registry and returns its recorded evidence. It does not claim complete, live Top 500 coverage.
No. A public code alone does not prove current playability. Playback state is reported only when an operator has registered evidence; this project does not launch or control Overwatch 2.
There is no scheduler. Refreshing queries contact their public sources on demand. Stored observations, curated evidence, and compatible cached/status queries remain available according to each operation's offline behavior, but cannot become fresher while offline.
It does not bypass private profiles. Public hosting is not turnkey: the current HTTP server has no built-in auth, so an operator must provide TLS, authentication, durable storage, access controls, and backups.
Sources include OverFast, Blizzard hero statistics and patch notes, OWTICS, OWReplays, and OWCS Korea releases. Requests to these services can include query filters and public player identifiers needed for the selected operation.
This is an unofficial community project and is not affiliated with or endorsed by Blizzard Entertainment. Overwatch and related marks belong to their respective owners.
CI covers Windows/Linux × Python 3.11/3.13 × skill-only/MCP installations. It checks dependency isolation, shared contracts, real stdio/HTTP connections and shutdown, and shared DB access. Live upstream checks are separate and opt-in:
Implementation specification · Verification record · Source contracts · SQLite schema