@irtio/mcp

Connect an MCP-compatible coding agent to irtio. The server provides tools to deploy rooms, manage projects, run local scenarios, and inspect logs, metrics, and saves over stdio.

Set up

Use Node.js 22. Sign in with the irtio CLI:

npx irtio login

Add this entry to your MCP client's server configuration:

{
  "mcpServers": {
    "irtio": {
      "command": "npx",
      "args": ["-y", "@irtio/mcp"]
    }
  }
}

Restart or reconnect the MCP client, then ask the agent to list your irtio projects. The server uses the credential saved by irtio login. You can sign in again without restarting the server; it reads credentials for each call.

For a global installation:

npm install --global irtio @irtio/mcp

Use irtio-mcp as the configured command with no arguments.

Tools

| Task | Tools | | --- | --- | | Inspect the account and projects | whoami, project_list, project_get | | Configure projects and origins | project_create, project_update, origin_list, origin_add, origin_remove | | Deploy and inspect versions | deploy, deployment_list, rollback | | Inspect live operation | rooms, logs, metrics, usage, match_status | | Read rankings | leaderboard, ratings | | Manage saves | save_list, save_restore | | Manage JWT signing secrets | jwt_secret_mint, jwt_secret_retire | | Run a local test scenario | scenario_run |

Deployments can drain or migrate live rooms. Restores and rollbacks can disconnect players and replace state; review the tool's scope before running it. Local builds and scenario scripts execute project code on your machine.

Credentials and endpoints

The server checks the CLI credential file first, then IRTIO_TOKEN for headless use. Keep tokens out of committed MCP configuration. Set IRT_CONTROL_URL in the server environment to select a control endpoint. JWT signing secrets are returned once when minted; store them on your server.

See the MCP reference for tool behavior and errors.