Skip to content
VS Code

specter skills for VS Code

io.github.dirtcubeinteractive/specter-skills

Configure a Specter game backend from chat: economy, progression, leaderboards, multiplayer.

client:VS Code transport:stdio runtime:npm

Install specter skills in VS Code

.vscode/mcp.json

{
  "inputs": [
    {
      "type": "promptString",
      "id": "specter-env",
      "description": "SPECTER_ENV",
      "password": true
    },
    {
      "type": "promptString",
      "id": "specter-allow-mutations",
      "description": "SPECTER_ALLOW_MUTATIONS",
      "password": true
    },
    {
      "type": "promptString",
      "id": "specter-api-key",
      "description": "SPECTER_API_KEY",
      "password": true
    },
    {
      "type": "promptString",
      "id": "specter-project-id",
      "description": "SPECTER_PROJECT_ID",
      "password": true
    },
    {
      "type": "promptString",
      "id": "specter-admin-token",
      "description": "SPECTER_ADMIN_TOKEN",
      "password": true
    }
  ],
  "servers": {
    "specter-skills": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "specter-skills"
      ],
      "env": {
        "SPECTER_ENV": "${input:specter-env}",
        "SPECTER_ALLOW_MUTATIONS": "${input:specter-allow-mutations}",
        "SPECTER_API_KEY": "${input:specter-api-key}",
        "SPECTER_PROJECT_ID": "${input:specter-project-id}",
        "SPECTER_ADMIN_TOKEN": "${input:specter-admin-token}"
      }
    }
  }
}

VS Code prompts for each input the first time the server starts, so no secret is written to the file. VS Code docs

specter skills in other clients