About unicum.gg
unicum.gg is a free, open-source World of Tanks statistics tracker for players, clans and tanks across EU, NA and Asia. It provides leaderboards and game data through its website, public API and remote MCP server.
Key features
- 01Player ratings and win-rate leaderboards
- 02Per-tank records and Marks of Excellence
- 03Clan rankings, members and war data
- 04Tank specifications and update changes
- 05Map and server-population data
- 06Public API documented with OpenAPI
Use cases
- 01Compare player ratings and win rates
- 02Review clan rankings and membership
- 03Look up tank specifications and mark thresholds
- 04Retrieve World of Tanks data through MCP
MCP support
Its remote MCP server exposes every public API endpoint as a tool, without requiring an API key. MCP clients can connect at https://unicum.gg/api/mcp.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://unicum.gg/api/mcpclaude mcp add --transport http gg-unicum-wot-stats https://unicum.gg/api/mcp{"mcpServers":{"gg-unicum-wot-stats":{"type":"http","url":"https://unicum.gg/api/mcp"}}}Open in Cursor{"servers":{"gg-unicum-wot-stats":{"type":"http","url":"https://unicum.gg/api/mcp"}}}Open in VS Code{"mcpServers":{"gg-unicum-wot-stats":{"type":"http","url":"https://unicum.gg/api/mcp"}}}{"mcpServers":{"gg-unicum-wot-stats":{"serverUrl":"https://unicum.gg/api/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
106| Parameter | Type | Required | Description |
|---|---|---|---|
| tag | string | Yes | Clan tag. |
| region | enum | Yes | Game server region.eu | na | asia |
Details
From the project READMEunicum.gg
Free, open-source World of Tanks stats tracker. Player profiles, clan pages, leaderboards. WN7, WN8, WNX. No ads.
Live at unicum.gg.
Use it
- Player stats: WN8, WNX and win rate leaderboards, per-tank records, Marks of Excellence
- Clan stats: rankings, members, Stronghold and Clan Wars
- Tank stats: specifications, mark thresholds, buffs and nerfs across updates
- Maps and server population
- Public API: the same data the site reads, documented with OpenAPI
MCP server
Every API endpoint is also a tool on a remote MCP server, no key needed. It is listed in the official MCP Registry as gg.unicum/wot-stats.
{
"mcpServers": {
"unicum": { "url": "https://unicum.gg/api/mcp" }
}
}
Stack
Next.js 16, React 19, TypeScript, PostgreSQL via Drizzle, Tailwind v4, shadcn/ui, Recharts.
Monorepo
pnpm workspace. Dependencies flow one way, no cycles:
@unicum.gg/wargaming ──▶ @unicum.gg/shared ──▶ @unicum.gg/core ──▶ apps/web (server) + apps/worker
│ HTTP API
@unicum.gg/sdk ◀───────┘
└──▶ web front + apps/bot
| Package / app | Role |
|---|---|
packages/wargaming | Neutral Wargaming API SDK (client, rate limiting, full response types) |
packages/shared | Client-safe foundations: env, constants, db schema, pure domain math and types |
packages/core | Server-only: db pool, redis, crons, repositories, WG fetchers, auth |
packages/sdk | Fluent client for our own public API, types generated from the OpenAPI spec |
apps/web | The Next.js site and public API |
apps/worker | Standalone cron runner |
apps/bot | Discord bot (/player, /clan) |
wargaming, shared and sdk are imported from their package barrel (import { Region } from "@unicum.gg/wargaming"). core is deliberately not a barrel: its modules have import-time side effects (db pool, auth secret assert), so server code imports the specific subpath it needs (@unicum.gg/core/db, ...). The front end and the Discord bot never import core; they consume the API through @unicum.gg/sdk and types through @unicum.gg/shared.
Run locally
pnpm install
pnpm env:init # generates .env.local from env.ts; fill in the values
pnpm dev
pnpm env:init reads env.ts and writes a .env.local with every required key. If a .env.local already exists it is backed up to .env.local.<timestamp>.bak first, so nothing is lost.
Get the three WG application IDs at developers.wargaming.net (one ID can be reused across regions).
Database
for f in apps/web/drizzle/0*.sql; do psql "$DATABASE_URL" -f "$f"; done
Contributing
Issues and PRs welcome. Read AGENTS.md first. It is the project's contributing guide and covers the non-obvious foot-guns (schema factory pattern, migration workflow, cron loop, WG fetch and rate limits).
License
AGPL v3. Copyright (C) 2026 Antoine Kingue.
Not affiliated with Wargaming.net.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.