Skip to main content
Glama

specter-skills

npm version node license

Build your game backend by talking to Claude.

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.

No SDK to learn. No API docs to read. Install it, then ask.

You:    "Add Specter to my game — silent login, a coins wallet, and a daily
         quest 'play 3 matches' that rewards 100 coins."
Claude: ...writes the integration code, sets up the quest in your backend, done.

Contents


Related MCP server: Sprixen MCP server

What's inside

This one package ships two halves of the same product:

What it is

What it does

🧠 Skills

Knowledge Claude reads

Claude writes correct Specter integration code — right endpoints, headers, response handling, and all the platform's gotchas baked in.

🛠️ MCP server

A tool Claude can run

Claude acts on your backend — inspect a project, verify your setup, and create currencies, items, tasks, leaderboards, battle passes, and more, straight from chat.

Skills work in Claude Code, Claude Desktop, the Claude Agent SDK, and any other skills-aware host. The MCP server works in any MCP-compatible host (Claude Desktop, Claude Code, …).


Quickstart

1. Install the skills in your game project:

npx specter-skills init

2. Get your API key from console.specterapp.xyz (Project → API Keys).

3. Ask Claude to build something:

"Add Specter email login and a gem currency to my Unity game."

The right skill activates automatically and Claude writes the integration. That's it.

💡 Want Claude to also set up the backend for you (create currencies, quests, leaderboards)? Add the MCP server and ask "create a gems currency and a daily login quest in my Specter project."


Installation

# Interactive — choose skills and where to install them
npx specter-skills init

# Install everything into this project's .claude/skills/
npx specter-skills install

# Install specific skills
npx specter-skills install specter specter-economy

# Install globally (available in all your projects)
npx specter-skills install --global

# Install into a custom directory (Agent SDK / other hosts)
npx specter-skills install --dir ./skills

Command

What it does

npx specter-skills init

Interactive: pick skills + target (project or global)

npx specter-skills install [names…]

Install named skills (default: all). Flags: --global, --dir <path>

npx specter-skills update

Re-install your skills at the latest version

npx specter-skills list

Show which skills are available and which you have installed

Skills are copied into .claude/skills/ (project) or ~/.claude/skills/ (global). They're plain files you can commit to your repo.


The skills

Skill

What it covers

specter

Start here — platform overview, the auth model, base URLs, the response envelope, and every error code.

specter-players

Sign-up & login (email, username, silent device ID, Google, Apple, Steam, Discord, Facebook), tokens, account linking, player profiles & custom data, friends.

specter-economy

Currencies & wallets, items, bundles, stores & purchases, inventory, gacha / loot boxes with pity, and real-money gaming (deposits / withdrawals).

specter-progression

Tasks, missions, achievements, daily quests & streaks, task-rule design, custom events, battle passes, XP & level systems.

specter-competitions

Leaderboards, tournaments, instant battles, prize distribution, and schedules.

specter-multiplayer

Skill-based matchmaking, parties, match sessions, and the full real-time Socket.io event contract.

specter-admin

Configure the game via admin APIs — projects, currencies, items, tasks, live-ops, members. Used by the MCP server to set things up for you.

Each skill has a concise guide plus per-endpoint references (request fields, response examples) generated directly from Specter's API, and ready-to-paste JavaScript / Unity examples where useful — so the code Claude writes stays accurate.


The MCP server

The same package ships an MCP server, specter-mcp, that lets Claude inspect and configure a Specter backend directly. The skills teach Claude the API; the MCP server lets it use the API.

"What currencies does my project have?" · "Is my setup working?" · "Create a gems currency and a daily quest that rewards 100 coins."

Setup

The easy way — npx specter-skills init offers to set this up for you (it writes the config, no JSON editing). Or run it any time:

# Claude Desktop
npx specter-skills mcp

# Claude Code (registers it for all your projects)
npx specter-skills mcp --code

Then restart your MCP host and the specter tools appear. (Claude Desktop and Claude Code are different apps with separate configs — pick the one you actually use.)

Add to your MCP host config (e.g. Claude Desktop's claude_desktop_config.json):

{
  "mcpServers": {
    "specter": {
      "command": "npx",
      "args": ["-y", "-p", "specter-skills", "specter-mcp"],
      "env": {
        "SPECTER_ENV": "staging",
        "SPECTER_ALLOW_MUTATIONS": "true"
      }
    }
  }
}

Read-only tools work immediately; creating things needs a one-time sign-in — no api-key or project ID to configure.

Signing in (no password needed)

To create anything, Claude needs to act as you — so you authorize it once through your browser. The first time it's needed, Claude runs the specter_login tool (or run it yourself in a terminal):

npx -y -p specter-skills specter-mcp login

What happens:

  1. Your browser opens the Specter dashboard.

  2. You sign in however you normally do — email/password, Google, or Apple.

  3. You approve a consent screen ("Allow specter-mcp to manage your projects").

  4. Done — a revocable token is saved locally (~/.specter/credentials.json). You stay signed in.

Your password and social credentials never touch the tool or Claude. Revoke access anytime from the dashboard. Manage the session with specter-mcp whoami and specter-mcp logout.

ℹ️ Run specter-mcp commands from any folder except the specter-skills source folder itself (npx gets confused there).

Tools

Read-only — always available, safe to run:

Tool

Purpose

specter_verify_setup

Smoke-test the project: auth, currencies, events, tasks

specter_list_currencies · _items · _bundles · _stores

Inspect economy content

specter_list_events

List custom events (with their ids) that trigger tasks

specter_list_tasks · _leaderboards · _tournaments · _battlepasses

Inspect progression & competitions

specter_list_progression_systems · _markers

Inspect level systems & markers

Read tools use your browser sign-in (run specter_login once) — no separate api-key to configure.

Client / runtime — act as a sandboxed test player to exercise the game-facing /v2/client API and prove your config works:

Tool

Purpose

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_get_reward_history · specter_claim_reward

List pending rewards, and claim on-claim task rewards (grant-reward-by-source)

specter_generate_client_code

Generate ready-to-paste game code (JS or Unity C#) wired with your real api-key + event slug

Mutating — opt-in (SPECTER_ALLOW_MUTATIONS=true), gated behind your confirmation:

Tool

Creates / does

specter_create_currency · _item · _bundle · _store

Economy content

specter_create_currency_conversion · _currency_policy

Exchange rates + balance/decay/earning-cap policies

specter_create_event

A custom event that triggers achievements

specter_create_task

A single-objective achievement

specter_create_mission · _step_series · _time_series

The 3 grouped achievement types (pool / sequential / streak)

specter_schedule_achievement · _stop_achievement · _delete_achievement

Activate / halt / delete an achievement (the create→schedule two-step)

specter_create_battlepass · _level_system · _progression_marker

Progression content

specter_create_match

Multiplayer match template (format / outcome / game)

specter_create_leaderboard · _competition

Competitions

specter_edit_currency · _edit_task · _update_entity

Edit existing entities (rename, retune, disable, …)

specter_schedule_liveops

Schedule a leaderboard / competition live

specter_grant_reward

Grant items / currencies to a player

specter_admin_call · specter_client_call

Escape hatches — call any /v1 admin or /v2/client endpoint that lacks a dedicated tool (match config, members, games, reward-sets, tags, friends, purchases, …), using the bundled API references for the shape

specter_login

Browser sign-in (above)

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 achievement does not make it live — call specter_schedule_achievement to activate it.

Mutating tools change live game configuration, so they're flagged non-read-only and your MCP host asks for confirmation before each one. Point them at a staging project first.

Your project is auto-detected from your sign-in — there's no project ID to look up. (Only set SPECTER_PROJECT_ID if your organisation has several projects and you want to pin one.)

Configuration

All configuration is via env vars in your MCP host config:

Variable

Required

Default

Purpose

SPECTER_ENV

—

staging

staging or production

SPECTER_ALLOW_MUTATIONS

—

false

true enables the create / mutate tools

SPECTER_API_KEY

optional

—

Client api-key. Not needed after sign-in — the dev key from your login is reused. Set it only if you want read tools to work before signing in.

SPECTER_PROJECT_ID

optional

—

Auto-discovered from your sign-in. Only set it if your organisation has multiple projects and you want to pin one.

SPECTER_ADMIN_TOKEN

optional

—

For CI / non-interactive use instead of browser sign-in


Things to ask Claude

Once installed, just describe what you want — the right skill (and MCP tool) kicks in automatically:

  • "Add silent device login and a coins wallet to my game."

  • "Set up a daily quest: play 5 matches → reward 200 coins. Create it in my Specter project and give me the client code."

  • "Create a premium gem currency and a starter store that sells a 'Sword' item for 100 gems."

  • "Add a weekly leaderboard with top-10 prize distribution."

  • "Build a battle pass with 30 tiers."

  • "Add skill-based matchmaking with parties — show me the WebSocket events to handle."

  • "Why am I getting a 429 from Specter?"

  • "Is my Specter project set up correctly?"


Checking the version & updating

# Latest version published on npm
npm view specter-skills version

# Which skills you have installed (and their versions)
npx specter-skills list

# Update your installed skills to the latest
npx specter-skills update

npx caches packages for ~24h. If update pulls an old version, force the latest with npx specter-skills@latest update. The MCP server (npx … specter-mcp) always fetches the latest published version the same way.


Requirements

  • Node.js 18+

  • A Specter project + API key (console.specterapp.xyz)

  • A skills-aware Claude host (Claude Code, Claude Desktop, or the Agent SDK) for the skills; an MCP-compatible host for the server


Troubleshooting

Symptom

Fix

specter-mcp: command not found

Run it from a folder other than the specter-skills source folder (e.g. cd ~ first).

No api-key available

Set SPECTER_API_KEY, or run specter-mcp login (its dev key is then reused).

Multiple projects on a create tool

Tell Claude which project (it's auto-detected when you have one).

Create tools don't appear

Set SPECTER_ALLOW_MUTATIONS=true and restart your MCP host.

Browser login times out

Re-run specter-mcp login; if the browser didn't open, use the printed URL.

Skills don't activate

Confirm they're installed (npx specter-skills list) and your host loads .claude/skills/.

401 / 402 / 429 from the API

See the specter skill's error reference (auth, billing, rate limits).



  • Endpoint references are generated. npm run generate regenerates skills/*/references/endpoints{,/-index}.md from gamestarz_dashboard_backend/docs/api/ (override the source dir with SPECTER_DOCS_DIR). Unmapped endpoint docs fail the build, so the skills can't silently drift from the API.

  • Secret linter. npm run lint:secrets (also runs on prepublishOnly) blocks secrets and internal hostnames from being published.

  • Hand-written content lives in each skill's SKILL.md and the non-generated references/*.md. The MCP server lives in mcp/src/.

Releasing

npm version patch        # or minor / major
npm run generate         # refresh references
npm publish --access public

The files allowlist ships bin/, skills/, mcp/src/*.mjs, and README.md. Skills and the MCP server publish together as the single specter-skills package.

Available Tools

46 tools
specter_admin_callCall any admin (v1) endpointA

Escape hatch for the dashboard/admin API: POST to any /v1 admin endpoint that lacks a dedicated tool (e.g. match/add, member/invite/send, reward-set/create, games/add, tag/create, ugc-leaderboard/create, app-event/custom/subscribe-all, bulk-upload/*). Find the exact path + request body in the specter-admin references (references/endpoints-index.md and admin-endpoints.md). projectId is auto-injected when omitted. MUTATES live config — ALWAYS confirm with the user first, treat any path containing '/delete' as destructive, and prefer staging.

Inputs: path (required), body, injectProjectId.

specter_claim_rewardClaim a pending reward (test player)A

Claim the test player's pending reward(s) from a source — this is how a game claims an ON-CLAIM task/mission reward after it completes (grant-reward-by-source). It grants the reward to the wallet/inventory and flips its status pending → completed. Identify the source by its slug/id and type.

Inputs: source (required), type, instanceId.

specter_client_callCall any client (v2) endpointA

Escape hatch for the game-facing API: POST to any /v2/client/* endpoint as the sandbox test player. Use for client calls that lack a dedicated tool (e.g. player/me/get-inventory, friends/send-request, stores/default-purchase, leaderboards/get-rankings, competitions/enter). Find the exact path + body in the client-api-index / curated-client-api references. asPlayer=true (default) sends the test-player token; false = api-key-only catalog reads.

Inputs: path (required), body, asPlayer.

specter_create_battlepassCreate battle pass (admin)A

Create a battle pass. tiers (free/premium rewards per tier) go in fields. MUTATES live game config — confirm with the user and prefer staging.

Inputs: name (required), battlepassId (required), levelSystemId (required), fields, +1 more.

specter_create_bundleCreate bundle / loot box (admin)A

Create a bundle. For a gacha/loot box set isGacha + pity fields in fields; contents/prices go in fields too. MUTATES live game config — confirm with the user and prefer staging.

Inputs: name (required), typeId (required), fields, projectId.

specter_create_competitionCreate competition / tournament (admin)A

Create a competition. competitionFormatTypeMasterId: 2=tournament, 3=instant battle, 4=paid challenge, 5=bracket. For match-based (sourceTypeId 1) pass matchId+gameId in fields; entry prices/prizes/schedule also go in fields. MUTATES live game config — confirm with the user and prefer staging.

Inputs: name (required), competitionId (required), isSpecialEvent (required), competitionFormatTypeMasterId (required), +2 more.

specter_create_currencyCreate currency (admin)A

Create a virtual or real-money currency. type is "virtual" (in-game, e.g. coins/gems) or "real" (real-money). currencyId (slug) is auto-derived from the name if omitted. MUTATES live game config — confirm with the user and prefer staging.

Inputs: name (required), code, type, fields, +4 more.

specter_create_currency_conversionCreate currency conversion (admin)A

Define an exchange rate from one currency to another (e.g. 100 gems → 1 gold). Pass currencies by slug/name; the tool resolves them to the integer ids the API needs. MUTATES live game config — confirm and prefer staging.

Inputs: source (required), target (required), conversionRate (required), isEnabled, +2 more.

specter_create_currency_policyCreate currency policy (admin)A

Attach a policy to a currency: "balance_limits" (min/max a player can hold), "currency_decay" (lose a % over time), or "earning_caps" (max earnable per period). Pass the currency by slug/name. MUTATES live game config — confirm and prefer staging.

Inputs: currency (required), policyType (required), rate, period, +9 more.

specter_create_eventCreate custom event (admin)A

Create a custom event that tasks/achievements can be triggered by (e.g. "boss_defeated"). Create the event BEFORE the task that references it. eventId (slug) is auto-derived from the name. MUTATES live game config — confirm with the user and prefer staging.

Inputs: name (required), fields, eventId, projectId, +2 more.

specter_create_itemCreate item (admin)A

Create an inventory item. Properties (consumable/equippable/...), prices, unlock conditions go in fields. MUTATES live game config — confirm with the user and prefer staging.

Inputs: name (required), typeId (required), fields, projectId.

specter_create_leaderboardCreate leaderboard (admin)A

Create a leaderboard. prizeDistributionRule/prize config goes in fields. outcomeType: 1=high_score, 2=time_trial, 4=position_weighting, 5=cumulative_score. sourceType: 1=match, 2=statistics, 3=custom. MUTATES live game config — confirm with the user and prefer staging.

Inputs: sourceTypeId (required), leaderboardId (required), leaderboardOutcomeTypeMasterId (required), name, +3 more.

specter_create_level_systemCreate level / progression system (admin)A

Create a level system. levelSystemTypeId: 1=XP-based, 2=event-based. levelDetails is the per-level config. MUTATES live game config — confirm with the user and prefer staging.

Inputs: name (required), levelDetails (required), levelSystemTypeId (required), rewardGrantScheduleType (required), +2 more.

specter_create_matchCreate match template (admin)A

Create a multiplayer match template (the config a real-time session is based on). format is single/multi/team; outcome is how a winner is decided (highest score, fastest time, finish position). The game is resolved by name/slug. Matchmaking rules (team size, MMR) go in fields. MUTATES live game config — confirm and prefer staging.

Inputs: name (required), format (required), outcome (required), game, +3 more.

specter_create_missionCreate mission (task pool) (admin)A

Create a MISSION: a pool of tasks where players see/complete a subset per cycle (typeId 1). Use for "daily missions", "rotating challenges", "pick N of these". For sequential use specter_create_step_series; for streaks use specter_create_time_series. Each task in tasks is created inline. MUTATES live game config — confirm and prefer staging.

Inputs: name (required), tasks (required), fields, projectId, +7 more.

specter_create_progression_markerCreate progression marker (admin)A

Create a progression marker (a named counter like XP or trophies). MUTATES live game config — confirm with the user and prefer staging.

Inputs: name (required), fields, projectId.

specter_create_step_seriesCreate step series (sequential) (admin)A

Create a STEP SERIES: ordered tasks where each unlocks the next (typeId 2). Use for "quest lines", "tutorial chains", "finish step 1 before step 2". The order of tasks (or each task's sortingOrder) defines the sequence. MUTATES live game config — confirm and prefer staging.

Inputs: name (required), tasks (required), fields, projectId, +5 more.

specter_create_storeCreate store (admin)A

Create a store. Categories/contents/platforms go in fields (storeCategories[]). MUTATES live game config — confirm with the user and prefer staging.

Inputs: name (required), storeId (required), fields, projectId.

specter_create_taskCreate task / achievement (admin)A

Create a SINGLE-objective achievement (a "task"/"quest"/"objective" — one trigger, one reward). For multi-objective achievements use specter_create_mission (a pool), specter_create_step_series (sequential), or specter_create_time_series (streaks). event is the trigger event (slug/name, resolved automatically). rewards grants currencies/items/markers (by slug/name). recurring captures cadence intent (actual go-live is via scheduling). MUTATES live game config — confirm with the user and prefer staging.

Inputs: name (required), event (required), fields, taskId, +9 more.

specter_create_time_seriesCreate time series (streak) (admin)A

Create a TIME SERIES: per-window recurring tasks, e.g. a daily login streak (typeId 3). Use for "streaks", "login N days in a row", "weekly recurring that resets on miss". stageLength is the window count (e.g. 7) and interval its unit (e.g. "day"). MUTATES live game config — confirm and prefer staging.

Inputs: name (required), tasks (required), interval (required), stageLength (required), +9 more.

specter_delete_achievementDelete an achievement (admin)A
Destructive

Soft-delete a single task (kind="task") or a group (kind="mission"|"step_series"|"time_series"). Provide refs (slugs/names/ids). DESTRUCTIVE — confirm with the user first, and prefer staging.

Inputs: kind (required), refs (required), projectId.

specter_edit_currencyEdit currency (admin)A

Update an existing currency (name, description, code, type, …). Identify it by slug/name. MUTATES live game config — confirm and prefer staging.

Inputs: currency (required), code, name, type, +3 more.

specter_edit_taskEdit task / achievement (admin)A

Update an existing single task's name, description, rewardClaim, recurrence, or businessLogic (identify it by slug/name). To CHANGE REWARDS, delete and recreate the task — task/edit uses diff-semantics on rewards that aren't reliably expressible here. MUTATES live game config — confirm and prefer staging.

Inputs: task (required), name, fields, projectId, +4 more.

specter_generate_client_codeGenerate game-side client codeA
Read-only

Generate ready-to-paste game integration code (v2 client REST) wired with this project's real client api-key + a real event slug. Covers login, firing events, reading tasks, and wallet. JS works anywhere; C# is dependency-free Unity (the official Specter Unity SDK is recommended for production).

Inputs: language (required), projectId.

specter_get_player_stateRead the test player (tasks, wallet, inventory)A
Read-only

Sign in the sandbox test player and read their task/achievement status, wallet balances, and inventory. Use to inspect what a player currently sees, or to check an achievement's progress.

Inputs: include.

specter_get_reward_historyRead the test player's reward historyA
Read-only

Read the test player's reward history — including PENDING rewards waiting to be claimed (on-claim tasks). Filter by status ('pending' shows claimable). Each entry has sourceType + sourceId (e.g. the task), amount, and status (pending → completed).

Inputs: limit, status, rewardGrant.

specter_grant_rewardGrant reward to a player (admin)A

Grant items/bundles/currencies/markers to a player. rewardDetails is an array; each entry has rewards: {items[],bundles[],currencies[],progressionMarkers[]}. MUTATES live game config — confirm with the user and prefer staging.

Inputs: userId (required), rewardDetails (required), fields.

specter_list_battlepassesList battle passesA
Read-only

List the battle passes configured in this Specter project. Returns ids/slugs you can reference when creating other entities. Requires a one-time browser sign-in (specter_login).

Inputs: limit, search, projectId.

specter_list_bundlesList bundles / loot boxesA
Read-only

List the bundles / loot boxes configured in this Specter project. Returns ids/slugs you can reference when creating other entities. Requires a one-time browser sign-in (specter_login).

Inputs: limit, search, projectId.

specter_list_currenciesList currenciesA
Read-only

List the currencies configured in this Specter project. Returns ids/slugs you can reference when creating other entities. Requires a one-time browser sign-in (specter_login).

Inputs: limit, search, projectId.

specter_list_eventsList custom eventsA
Read-only

List the custom events configured in this Specter project. Returns ids/slugs you can reference when creating other entities. Requires a one-time browser sign-in (specter_login).

Inputs: limit, search, projectId.

specter_list_itemsList itemsA
Read-only

List the items configured in this Specter project. Returns ids/slugs you can reference when creating other entities. Requires a one-time browser sign-in (specter_login).

Inputs: limit, search, projectId.

specter_list_leaderboardsList leaderboardsA
Read-only

List the leaderboards configured in this Specter project. Returns ids/slugs you can reference when creating other entities. Requires a one-time browser sign-in (specter_login).

Inputs: limit, search, projectId.

specter_list_markersList progression markersA
Read-only

List the progression markers configured in this Specter project. Returns ids/slugs you can reference when creating other entities. Requires a one-time browser sign-in (specter_login).

Inputs: limit, search, projectId.

specter_list_progression_systemsList level / progression systemsA
Read-only

List the level / progression systems configured in this Specter project. Returns ids/slugs you can reference when creating other entities. Requires a one-time browser sign-in (specter_login).

Inputs: limit, search, projectId.

specter_list_storesList storesA
Read-only

List the stores configured in this Specter project. Returns ids/slugs you can reference when creating other entities. Requires a one-time browser sign-in (specter_login).

Inputs: limit, search, projectId.

specter_list_tasksList tasks / achievementsA
Read-only

List the tasks / achievements configured in this Specter project. Returns ids/slugs you can reference when creating other entities. Requires a one-time browser sign-in (specter_login).

Inputs: limit, search, projectId.

specter_list_tournamentsList tournaments / competitionsA
Read-only

List the tournaments / competitions configured in this Specter project. Returns ids/slugs you can reference when creating other entities. Requires a one-time browser sign-in (specter_login).

Inputs: limit, search, projectId.

specter_loginAuthenticate for admin actionsA

Opens the Specter dashboard in the browser so the member can sign in (email/password, Google, or Apple) and authorize this tool. Required once before creating currencies/tasks. No password is ever shared with the tool.

Inputs: no named parameters.

specter_schedule_achievementSchedule an achievement live (admin)A

Activate a created task or task-group (mission/step-series/time-series) by setting its dates/recurrence. Pass exactly one of taskRef (single task) or groupRef (a group), by slug/name/id. Omitting startDate makes it go live immediately. MUTATES live game config — confirm and prefer staging.

Inputs: endDate, taskRef, groupRef, timezone, +3 more.

specter_schedule_liveopsSchedule a leaderboard / competition (live-ops) (admin)A

Schedule a leaderboard or competition live. Provide exactly one of competitionId / leaderboardId. Recurrence config goes in fields. MUTATES live game config — confirm with the user and prefer staging.

Inputs: endDate (required), startDate (required), fields, projectId, +2 more.

specter_send_eventFire an event as the test playerA

Send a custom event (by its slug) as the sandbox test player — the same event your game would fire. Use to trigger tasks/achievements and verify they respond. params are the event parameters (statistics/states) your rule references.

Inputs: event (required), params.

specter_stop_achievementStop an achievement (admin)A

Halt a live task or task-group (keeps the record; reversible by scheduling again). Pass exactly one of taskRef / groupRef. MUTATES live game config — confirm and prefer staging.

Inputs: taskRef, groupRef, projectId.

specter_test_achievementTest an achievement end-to-endA

Prove a configured task/achievement works: reads the test player's task status, fires the trigger event (with optional params), polls again, and reports whether the task progressed/completed. Use right after creating a task to verify it actually fires.

Inputs: event (required), times, params, taskId.

specter_update_entityUpdate an entity by id (admin)A

Generic editor for the long tail: update an item/bundle/store/leaderboard/competition/battlepass/level_system/marker/mission/step_series/time_series/event. Pass the entity's id (from the matching list_* tool) and the fields to change. MUTATES live game config — confirm and prefer staging.

Inputs: id (required), entity (required), fields (required), projectId.

specter_verify_setupVerify Specter setupA
Read-only

Smoke-test the configured Specter project: api-key validity, project info, currencies, test-player login, wallet provisioning, and tasks. Use this first to answer "is my Specter backend set up correctly?".

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 46 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., create vs list vs edit vs schedule for different entity types). However, the presence of generic escape hatches (specter_admin_call, specter_client_call) and a generic update tool (specter_update_entity) alongside specific edit tools introduces some ambiguity. Overall, well-disambiguated.

    Naming Consistency5/5

    All tools follow a consistent specter_verb_noun pattern (e.g., specter_create_currency, specter_list_items, specter_delete_achievement). Naming is predictable and easy to navigate.

    Tool Count3/5

    With 46 tools, the server covers a vast number of operations for a game backend. While comprehensive, the count feels high; multiple list tools and generic tools could be consolidated. Slightly over-scoped.

    Completeness4/5

    The tool surface covers most aspects of the Specter game backend: CRUD for key entities, player state, rewards, events, and testing. Minor gaps (e.g., no player creation tool) exist, but overall it provides a thorough set for configuration and verification.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to deploy multiplayer web games as playable URLs with rooms, live state sync, and leaderboards, all through a single tool call.
      4
      5
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with running games in real time — introspecting game state, simulating keyboard and mouse input to actually play, capturing screenshots, executing Lua code, hot-reloading files, and receiving push notifications when state changes.
      8
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding assistants to access documentation, live API tools, and workflow prompts for integrating a game/app backend service into Godot, Unity, and Unreal Engine projects, including auth, leaderboards, cloud saves, remote config, localization, news, gift codes, feedback, logs, crash reporting, email, and admin dashboard management.
      120
      275 npm
      MIT