Specter

What is Specter?

Specter is a game backend platform. The specter-skills package includes an MCP server that lets Claude inspect and configure a Specter backend directly from chat, using tools to read and manage game configuration such as currencies, tasks, leaderboards, and achievements.

How to use Specter?

Install the package with npx specter-skills init. Set up the MCP server via npx specter-skills mcp (or manually edit your MCP host config). Sign in once through your browser to authorize the tool. After that, Claude can run read-only and mutating tools on your Specter project.

Key features of Specter

• Read-only tools to inspect economy, progression, and competition configuration.
• Mutating tools to create currencies, items, tasks, and achievements.
• Client tools to simulate player actions like sending events and claiming rewards.
• Browser-based sign‑in with no password shared with the tool.
• Auto‑detects your project from your sign‑in session.
• Works with Claude Desktop, Claude Code, and other MCP‑compatible hosts.

Use cases of Specter

• Inspect a project’s currencies, tasks, or leaderboards without opening the dashboard.
• Create new currencies, items, or battle passes with a single chat command.
• Set up and schedule achievements, missions, and daily quests from chat.
• Test player progression by firing custom events and checking state.
• Generate client code for your game using your real API key.

FAQ from Specter

What does the MCP server do vs the skills?

Skills teach Claude the Specter API so it writes correct integration code. The MCP server lets Claude act on your backend to inspect and configure it straight from chat.

What are the runtime requirements?

Node.js is required. The package is installed via npm and runs as an MCP server. No additional services beyond a Specter account are needed.

Where does my data live?

Your API key and sign‑in token are stored locally (~/.specter/credentials.json). No data is sent to third parties. You can revoke access from the dashboard at any time.

Are there known limits?

Mutating tools are flagged non‑read‑only and require confirmation before each call. The README advises pointing them at a staging project first. No explicit rate limits are mentioned.

How does authentication work?

Sign‑in is done through your browser using your normal Specter credentials (email/password, Google, or Apple). A revocable token is saved locally. Your password never touches the tool or Claude. Read‑only tools work after sign‑in; mutating tools require SPECTER_ALLOW_MUTATIONS=true.