MCP server

@peer10/mcp-server exposes the API as MCP tools — generated from the manifest as peer10_{domain}_{action} with singular domain tags, plus hand-written meta and changeset tools. Call peer10_introspect for the complete current list; it is generated from the same manifest as the tools, so it cannot drift.

Client configuration

// claude_desktop_config.json (or `claude mcp add` for Claude Code)
{
  "mcpServers": {
    "peer10": {
      "command": "npx",
      "args": ["tsx", "/path/to/peer10/packages/mcp-server/bin/peer10-mcp.ts"],
      "env": {
        "PEER10_BASE_URL": "https://peer10.com",
        "PEER10_API_KEY": "p10_live_..."
      }
    }
  }
}

Tool naming

peer10_season_list        peer10_season_getTimeline
peer10_team_create        peer10_player_update
peer10_changeset_preview  peer10_changeset_undo

Simulation-first — scoped honestly

Only the four peer10_changeset_* tools are simulation-first. Generated mutation tools call the API directly with the caller’s permissions — an agent operating on the old docs’ claim that every mutation returned a previewable changeset would have mutated real data believing it was previewing. For significant changes, drive the changeset tools.