Scorezilla MCP

What isco-tec/scorezilla-mcp MCP server does

The isco-tec/scorezilla-mcp MCP server exposes Scorezilla account and leaderboard operations to MCP-compatible development assistants. It can inspect the games associated with the authenticated developer, enumerate boards within a game, retrieve leaderboard rankings, and return key information suitable for integration work.

It also supports provisioning. A bootstrap operation creates a game and its first board together, then returns a widget embed, SDK code, and a plain-language recommendation. Separate creation tools support cases where the game already exists or where additional boards, games, or key pairs are needed. The full secret key is not returned by the MCP server; a newly minted secret is shown once, and existing secret material must be obtained from the Scorezilla dashboard.

How it works

The client starts the package as a local stdio MCP process and supplies a Scorezilla bearer token through the environment. The server sends requests to the Scorezilla API, which defaults to https://api.scorezilla.dev. A base URL can be changed for staging or self-hosted deployments.

The isco-tec/scorezilla-mcp MCP server includes a read-only mode. With --read-only, write tools are not registered, preventing the connected assistant from creating resources or changing supported configuration. Without that flag, the server provides read operations plus resource creation and configuration-update operations described by the project documentation.

Generated integration examples can be tailored by identity approach, OAuth usage, client-only or server-validated anti-cheat handling, and target server language. The available language choices are TypeScript, Python, Go, and C#.

Setup and configuration

The package requires Node.js 20 or newer and network access to the Scorezilla API. Install it through npm with the package command shown below:

npx -y @scorezilla/mcp

Create an MCP token in the Scorezilla dashboard and provide it as SCOREZILLA_TOKEN. Tokens are bearer credentials scoped to the issuing developer, so they should not be committed to source control or pasted into shared conversations. The README notes that a token stored in a client configuration file is plaintext and should be protected accordingly.

SCOREZILLA_BASE_URL provides the same API-origin override as --base-url; a command-line value takes precedence. SCOREZILLA_BETA_TOKEN is only needed when a Scorezilla team member supplies a closed-beta token. The command also supports --version and --help.

Tools and capabilities

The isco-tec/scorezilla-mcp MCP server documents these operations:

• List games and boards to discover existing Scorezilla resources.
• Read public keys, secret-key prefixes, and the top entries on a board.
• Generate SDK snippets and widget embed output for a board.
• Bootstrap a game and initial leaderboard in one operation.
• Create games, add boards to existing games, and mint new key pairs.
• Update supported board and game configuration, including score bounds, retention, and browser-submit origin rules.

Board creation accepts options such as sort direction, score type, retention, and score bounds. Destructive editing, deletion, and key revocation remain dashboard-only according to the provided documentation.

Limitations and notes

The service is described as being in closed beta, and access requires a token issued through the Scorezilla dashboard. The MCP server does not expose a game’s full secret key through its responses. It also depends on network access to the configured API origin, so it is not an offline leaderboard tool.

The repository is licensed under MIT. The README names Claude Code and Cursor as client examples and says the package can be pointed at other MCP-compatible clients; client-specific configuration details may differ.