War Thunder Replay MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_mcp_statusA | Return local output and authentication settings without exposing cookie values. |
| download_replayA | Download every .wrpl part for one user/session pair. Args: user_id: Numeric War Thunder player ID used by replay search. session_id: Hexadecimal replay session ID. max_workers: Parallel downloads from 1 through 8. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one checks server status and authentication settings, the other downloads replay files. There is no overlap or ambiguity between them.
Both tool names follow a consistent verb_noun pattern (get_mcp_status, download_replay), making it easy to predict their functionality.
With only 2 tools, the server feels thin for a replay management system. While it may cover the core download function, additional tools for searching or listing replays would be expected.
The server lacks tools for discovering or searching replays; it assumes users already have user_id and session_id. This is a significant gap that forces agents to obtain IDs from external sources, limiting the server's standalone usefulness.