LabscoMCP early access ↗
dirtcubeinteractiveMCP SERVER

Specter Skills

Describe a game economy or a daily quest in plain English and have it created in your Specter backend.

by dirtcubeinteractive ↗ERP & Vertical Business SystemsCommunity

LABSCO SUMMARY

Create tools stay off unless your setup turns them on.

Most of this surface writes to live game configuration — currencies, quests and leaderboards that players are already touching — so those tools load only when SPECTER_ALLOW_MUTATIONS is true, and your client asks you to confirm each one before it runs. The test-player tools are the unusual part: specter_test_achievement fires the same event your game fires, then re-reads the state, so you find out whether a quest rule works instead of assuming it does.

What it is

One npm package with two halves: a set of skills that teach Claude the Specter game-backend API — players, economy, progression, competitions, multiplayer — and an MCP server, specter-mcp, that lets it act on a project. The skills make the integration code correct; the server inspects and configures the backend so you are not clicking through the dashboard.

What you get

  • specter_verify_setup smoke-tests a project across auth, currencies, events and tasks
  • specter_list_currencies, specter_list_events, specter_list_tasks and specter_list_progression_systems read back what already exists
  • specter_create_currency, specter_create_task, specter_create_mission, specter_create_leaderboard and specter_create_battlepass build economy, progression and competition content
  • specter_send_event and specter_test_achievement fire a real client event as a sandboxed test player and report whether the task actually progressed
  • specter_generate_client_code emits ready-to-paste JavaScript or Unity C# wired to your api-key and event slug
  • specter_admin_call and specter_client_call reach any endpoint that has no dedicated tool

Requirements

  • Node.js 18+ and a Specter project.
  • Runs over stdio as npx -y -p specter-skills specter-mcp (package specter-skills, version 0.11.1).
  • The Claude Desktop config in Installation leaves SPECTER_ALLOW_MUTATIONS at false; Specter's setup helper, npx specter-skills mcp (or --code for Claude Code), sets it to true.
  • SPECTER_ENV in your config picks staging or production, and defaults to staging.
  • Read tools need a one-time browser sign-in for that same environment. Run npx -y -p specter-skills specter-mcp login in a terminal for staging, or SPECTER_ENV=production npx -y -p specter-skills specter-mcp login for production. It saves a revocable token to ~/.specter/credentials.json — no api-key to paste. With create tools on, Claude can start the sign-in for you through specter_login.

Setup effort

One command — npx -y -p specter-skills specter-mcp

See installation options