Configure a Specter game backend from chat: economy, progression, leaderboards, multiplayer.
Configure a Specter game backend from chat: economy, progression, leaderboards, multiplayer. Exposed over MCP by the specter mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
specter-skills teaches Claude everything about Specter — the game backend platform — so you can add player accounts, an in-game economy, daily quests, leaderboards, tournaments, battle passes, and real-time multiplayer to your game in plain English, and get correct, working code plus the ability to configure your backend without ever opening the dashboard.
The server ships on npm as specter-skills, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Everything the assistant can do here goes through one of these:
specter_verify_setup — Smoke-test the project: auth, currencies, events, tasksspecter_list_events — List custom events (with their ids) that trigger tasksspecter_get_player_state — Read the test player's tasks, wallet, and inventoryspecter_send_event — Fire a custom event (the same call your game makes) to trigger achievementsspecter_test_achievement — End-to-end: read status → fire the event → re-read → report whether the task progressedspecter_generate_client_code — Generate ready-to-paste game code (JS or Unity C#) wired with your real api-key + event slugspecter_create_event — A custom event that triggers achievementsspecter_create_match — Multiplayer match template (format / outcome / game)specter_schedule_liveops — Schedule a leaderboard / competition livespecter_grant_reward — Grant items / currencies to a playerspecter_login — Browser sign-in (above)Setup — The Setup tool exposed by this serverYou will need 5 environment variables: SPECTER_ENV, SPECTER_ALLOW_MUTATIONS, SPECTER_PROJECT_ID, SPECTER_API_KEY, SPECTER_ADMIN_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Specter's toolset — specter_verify_setup, specter_list_events, specter_get_player_state and 11 more — is a fair guide to whether it matches your workflow. It is maintained by dirtcubeinteractive; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| specter_verify_setup | Smoke-test the project: auth, currencies, events, tasks |
| specter_list_events | List custom events (with their ids) that trigger tasks |
| specter_get_player_state | Read the test player's tasks, wallet, and inventory |
| specter_send_event | Fire a custom event (the same call your game makes) to trigger achievements |
| specter_test_achievement | End-to-end: read status → fire the event → re-read → report whether the task progressed |
| specter_generate_client_code | Generate ready-to-paste game code (JS or Unity C#) wired with your real api-key + event slug |
| specter_create_event | A custom event that triggers achievements |
| specter_create_match | Multiplayer match template (format / outcome / game) |
| specter_schedule_liveops | Schedule a leaderboard / competition live |
| specter_grant_reward | Grant items / currencies to a player |
| specter_login | Browser sign-in (above) |
| Setup | The Setup tool exposed by this server. |
| Tools | The achievement tools resolve friendly names for you — pass event as an event slug/name, rewards as [{currency:"gems", quantity:50}] (or item/bundle/marker), and the tool resolves them to the right ids. Creating an achie |
| Configuration | The Configuration tool exposed by this server. |
{
"mcpServers": {
"specter-skills": {
"command": "npx",
"args": ["-y", "specter-skills"],
"env": {
"SPECTER_ENV": "your-value",
"SPECTER_ALLOW_MUTATIONS": "your-value",
"SPECTER_PROJECT_ID": "your-value",
"SPECTER_API_KEY": "your-value",
"SPECTER_ADMIN_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| SPECTER_ENV | Configuration value read at startup. | Optional |
| SPECTER_ALLOW_MUTATIONS | Configuration value read at startup. | Optional |
| SPECTER_PROJECT_ID | Configuration value read at startup. | Optional |
| SPECTER_API_KEY | Credential the server authenticates with. | Yes |
| SPECTER_ADMIN_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.