sc2-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SC2_API_BASE | No | Site origin (for local development). | https://www.starcraft2.ai |
| SC2_API_TOKEN | No | Use this token instead of the browser sign-in. | |
| SC2_MCP_NO_BROWSER | No | Set to 1 to print the sign-in URL instead of opening a browser. | |
| SC2_MCP_CREDENTIALS | No | Where the token is saved. | ~/.config/sc2-mcp/credentials.json |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Sign in to the user's StarCraft2.ai account. Opens the site's sign-in page in the browser (OAuth with PKCE); the user approves there and this tool finishes. Required before any other tool. If the browser didn't open, show the user the URL from the result. |
| logoutA | Sign out of StarCraft2.ai on this computer: revokes this device's token and deletes it locally. |
| get_accountA | The signed-in user's mineral balance (StarCraft2.ai credits), claimed SC2 profile, and where to buy more minerals. |
| search_sc2_knowledgeA | Search StarCraft2.ai's StarCraft II knowledge base — Liquipedia unit/building/ability data, current patch notes, strategy and matchup articles, and pro-game insights — the same sources the AI Coach cites. Use it to answer general SC2 questions (unit stats, counters, build orders, patch changes, matchup advice); answer from the passages and cite their URLs. Free. |
| upload_replayA | Upload a StarCraft II replay (.SC2Replay) — or a Brood War .rep — to StarCraft2.ai from a local file path or a download URL. The site parses it and it is attributed to the signed-in user. Returns the replay id and whether an AI Coach report already exists. Free. On Windows the default replay folder is Documents\StarCraft II\Accounts\…\Replays\Multiplayer; on macOS ~/Library/Application Support/Blizzard/StarCraft II/Accounts/…/Replays/Multiplayer. |
| list_my_replaysA | The signed-in user's uploaded replays on StarCraft2.ai, newest first, with whether each has an AI Coach report. Free. |
| get_analysisA | Read a replay's details and its AI Coach report if one exists. If this session started a coach run that is still going, waits for it (up to wait_seconds) and returns the report when it lands. Free — never spends minerals. |
| analyze_replayA | Run StarCraft2.ai's AI Coach on an uploaded replay. COSTS 1 MINERAL (the site's paid credits) unless the replay already has a report, which is returned free. Refuses to spend unless confirm_spend is true — tell the user the price and their balance and get a yes first. A run takes 3–7 minutes: this waits up to wait_seconds, then returns and the run continues; call get_analysis to collect it. Failed runs are refunded by the site. |
| ask_about_replayA | Ask StarCraft2.ai's coach a follow-up question about a replay that has an AI Coach report (it can check the replay's numbers and the knowledge base). The first 3 questions per replay are free; after that the site needs 1 mineral per 20 more, bought with unlock_more_questions (ask the user first). Shows the remaining free/unlocked questions. |
| unlock_more_questionsA | Spend 1 MINERAL to unlock 20 more follow-up questions on one replay (same price as the website). Refuses unless confirm_spend is true — only after the user agreed to spend the mineral. |
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 10 tools
Each tool targets a distinct action or resource: auth (login/logout), account info, knowledge search, replay upload/list, report reading, coach run, follow-up Q&A, and paid unlocks. The only potential overlaps (get_analysis vs analyze_replay, search_sc2_knowledge vs ask_about_replay) are clearly separated by descriptions as read vs run and general vs replay-specific.
All names use snake_case and mostly follow verb_noun (get_account, upload_replay, list_my_replays, analyze_replay). The bare verbs login/logout are a minor deviation but still unambiguous and consistent within the auth pair.
10 tools is well within the typical 3–15 range and each tool maps to a distinct step in the account/replay analysis workflow. No tool feels redundant or missing from a scope perspective.
The surface covers the core lifecycle: authentication, account info, knowledge search, replay upload/list, report retrieval, coach analysis, follow-up questions, and paid unlocks. Minor gaps exist (e.g., no delete-replay or direct mineral purchase tool), but they are workaroundable or external to the main workflow.