
start.gg MCP Server
io.github.tomo789由 GitHub 帳號 tomo789 發布v0.1.0更新於 Oct 24, 2026
MCP server for the start.gg GraphQL API: tournaments, events, entrants, sets, standings, streams
概覽
針對 start.gg GraphQL API 的唯讀 MCP 伺服器,讓助理查詢賽事、比賽項目、參賽者、對局、排名與直播串流。
- 可以做什麼
- 將 start.gg GraphQL API 包裝成 16 個唯讀工具,涵蓋遊戲與賽事搜尋、賽事與比賽項目詳情、含種子的參賽者、排名、正規化對局、單局角色與場地資料、選手、直播佇列,以及 start.gg 網址解析。輸出經過正規化(例如對局包含輪次、解碼後的狀態、參賽者、比分與勝者),並在建立請求前以 Zod 驗證輸入。另提供滑動視窗限流、含退避的重試,以及短效期記憶體快取。
- 適用情境
- 當助理需要回答關於 start.gg 上競技遊戲賽事的問題時使用:尋找即將舉行的賽事、查看參賽者與種子、回顧已完成對局與八強排名,或了解哪些直播串流被分配到對局。它與特定遊戲無關且為唯讀,適合查詢與彙報,而非管理賽程。
- 執行需求
- 以 npm 套件形式透過 stdio 在本機執行(npx startgg-mcp-server 或全域安裝);需要 Node.js 22 或更新版本。需要透過 STARTGG_TOKEN 環境變數提供 start.gg API 權杖。選用變數:STARTGG_RATE_LIMIT、STARTGG_TIMEOUT_MS、STARTGG_CACHE 與 STARTGG_ENABLE_WRITES。需要連線至 api.start.gg 的網路存取。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 start.gg MCP Server,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
startgg-mcp-server
A Model Context Protocol server for the start.gg GraphQL API. It lets MCP clients (Claude Code, Claude Desktop, and others) discover tournaments, inspect events, entrants, sets, standings, and streams for any game on start.gg using natural language.
What is this?
start.gg exposes a powerful but complex GraphQL API: entrants vs participants vs players, integer set states, complexity-limited pagination, epoch timestamps. This server wraps that API in a small set of MCP tools with:
- Normalized output — sets come back as
{ round, state: "COMPLETED", entrant1: { gamerTag, seed }, score, winnerEntrantId, ... }instead of raw GraphQL nesting - URL resolution — paste a start.gg URL, get tournament/event ids back
- Built-in rate limiting, retries, and caching tuned to start.gg's documented limits
The server is game-agnostic. Game-specific logic (e.g. Smash upset detection)
belongs in applications built on top — see
examples/smash-ultimate-watcher.
Features
- 16 read-only tools covering discovery, tournaments, events, players, streams, and URL resolution
- Input validation (Zod) on every tool — bad ids, oversized page sizes, and malformed URLs never reach the API
- Sliding-window rate limiter (default 75 req/60s vs start.gg's 80), retries with exponential backoff, and
Retry-Aftersupport - Short-TTL in-memory cache for metadata queries
- Typed error codes:
AUTH_ERROR,RATE_LIMITED,NOT_FOUND,INVALID_INPUT,STARTGG_GRAPHQL_ERROR,NETWORK_ERROR,INTERNAL_ERROR - GraphQL documents kept in
graphql/files, separate from code - The API token never appears in output, logs, or error messages
- Compact JSON output (no pretty-printing) to keep tool results small
Requirements
- Node.js >= 22
- A start.gg API token
Getting a start.gg API token
- Log in to start.gg
- Open developer settings (Profile → Developer Settings)
- Create a personal access token and copy it
Treat the token like a password. This server reads it only from the
STARTGG_TOKEN environment variable.
Installation
From npm (recommended)
Requires STARTGG_TOKEN in the environment; MCP clients normally launch it for you (see the next section).
From source
MCP client setup
Claude Code (CLI)
Running from a source checkout instead:
Claude Desktop
Add to claude_desktop_config.json:
From a source checkout, use "command": "node" and "args": ["/path/to/startgg-mcp-server/dist/cli.js"] instead.
Any MCP client that supports stdio servers works the same way: run
node dist/cli.js (or the startgg-mcp-server bin once installed via npm)
with STARTGG_TOKEN set.
Available tools
Discovery
Tournament
Event
Player
Utility
Tournament/event tools accept either a numeric id, a slug, or a full
start.gg URL. Scheme-less URLs (start.gg/tournament/...) and <t>/event/<e>
slugs are accepted too — you rarely need resolve_startgg_url explicitly, but
it is there when you want the ids.
Normalized set shape
Notes grounded in the live API:
roundNumber < 0means losers bracket;roundis the human-readable name- a score of
-1is start.gg's disqualification marker - unstarted "preview" sets have string ids like
"preview_3430499_2_0" statenames are decoded from the integerstateRaw; both are always returnedentrant1/entrant2use aplayersarray, so doubles/teams work unchanged
Games and characters
get_set_games (and get_event_sets with includeGames: true) add per-game
details when start.gg has them:
derivedCharacters summarizes unique character names per entrant in
first-appearance order across games. This is derived, not an API field.
Character and stage data only exists when the set was reported with it. In a
2026-09 sample, late rounds (Top 8 / streamed) had it on about 90% of completed
sets; early pools about 5%. An empty games array means not reported, not that
no games were played. Typical flow: get_event_sets (e.g. phaseIds for Top 8)
→ pick set ids → get_set_games. For many sets at once, get_event_sets with
includeGames: true.
Examples
Things to ask an MCP client once connected:
A standalone example application (videogame lookup → upcoming tournaments →
sets → upset candidates by seed difference) lives in
examples/smash-ultimate-watcher.
Environment variables
The API endpoint is deliberately not configurable through the environment: the
token is only ever sent to api.start.gg. When using the client as a library
(tests, tooling), inject apiUrl/fetchFn via the StartggClient constructor.
Out-of-range or non-numeric values for STARTGG_RATE_LIMIT / STARTGG_TIMEOUT_MS
fall back to the default and log a warning on stderr.
Without STARTGG_TOKEN the server still starts and lists tools, but every
call returns a clear AUTH_ERROR explaining how to fix it.
Security
- The token is read from the environment only, sent only to
api.start.gg, and never included in tool output, logs, or error messages - All tools are read-only; no mutations are implemented
.envfiles are git-ignored; use.env.exampleas a template- User-supplied input is schema-validated before any request is built
Rate limits
start.gg allows 80 requests per 60 seconds and at most 1000 objects per request. This server:
- keeps a sliding-window budget below the request limit (default 75/60s)
- retries
429(honoringRetry-After) and transient 5xx errors with exponential backoff, at most 3 retries — GraphQL errors are never retried - caps
perPageper tool so responses stay under the 1000-object complexity limit (sets are expensive: ~26+ objects each, henceperPage <= 30) - caps
fetchAllat 5 pages per tool (output is meant for an LLM context, so it stays around 100 KB of compact JSON) and reportstruncated: truewhen it stops early
Development
GraphQL documents live in graphql/*.graphql (one file per domain, multiple
named operations per file; requests select an operation via operationName).
Schema facts verified against the live API are recorded in
docs/startgg-api-notes.md — read it before
adding fields.
Testing
Unit tests cover the URL resolver, normalizers, input validation, pagination, GraphQL/HTTP error handling, the rate limiter, and the cache.
License
來源:README.md,提交 f991d32
工具
0版本歷史
1- v0.1.0最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分