AI assistants (MCP)

The Kraty MCP server lets an AI assistant work with Kraty for you. One server does two jobs:

• Integrate the SDK. In your game's codebase, the assistant detects the engine, installs the right Kraty SDK, creates a test key, wires up events, leaderboards and rewards, and checks that Kraty sees your players.
• Run your live ops. From chat: create events from templates, tune leaderboards, add currencies and items, simulate loot tables and bots, look up players, and review what's live.

It acts as you, with your role in the studio, through a personal key. Everything it changes is in the audit log, marked as made via MCP.

Set it up

claude mcp add --scope user --transport http kraty https://api.kraty.io/mcp \
  --header "Authorization: Bearer kraty_pk_..."

{
  "mcpServers": {
    "kraty": {
      "url": "https://api.kraty.io/mcp",
      "headers": { "Authorization": "Bearer kraty_pk_..." }
    }
  }
}

{
  "inputs": [
    { "type": "promptString", "id": "kraty-key", "description": "Kraty personal key", "password": true }
  ],
  "servers": {
    "kraty": {
      "type": "http",
      "url": "https://api.kraty.io/mcp",
      "headers": { "Authorization": "Bearer ${input:kraty-key}" }
    }
  }
}

{
  "mcpServers": {
    "kraty": {
      "serverUrl": "https://api.kraty.io/mcp",
      "headers": { "Authorization": "Bearer kraty_pk_..." }
    }
  }
}

{
  "mcpServers": {
    "kraty": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.kraty.io/mcp", "--header", "Authorization:${KRATY_AUTH}"],
      "env": { "KRATY_AUTH": "Bearer kraty_pk_..." }
    }
  }
}

Integrating the SDK

Open your game project in your assistant and ask it to integrate Kraty. It follows the same path every time:

1. Reads the project to detect the platform: Unity, TypeScript/JavaScript, Flutter, or a Node or Python game backend.
2. Calls get_sdk_setup, which returns your game's context (API URL, existing keys) plus the full SDK guide for that platform, straight from these docs.
3. Creates a test key with create_api_key and puts it where the guide says. Client keys go in one config spot; server keys go in environment variables, never in git.
4. Installs the SDK at the documented version, creates one client at startup, and wires the flows your game needs.
5. Generates a typed constants file with generate_keys_file (C#, TypeScript, Dart or Python), so your code uses KratyKeys.Events.WildRace.Key instead of hand-typed strings.
6. After you run the game, calls check_integration to confirm Kraty saw your test player.

Live keys for your release build are created by you in the dashboard. See API keys.

Running live ops

The assistant uses the same admin API as the dashboard, with the same validation. It works the safe way by default:

• Templates first. New events come from the template gallery (race, milestone track, league with divisions, daily login streak) where one fits.
• Test before live. New events go to staging, which only test keys see. It can drive the test environment with run_test_action (end a window now, roll a leaderboard over, inject scores, add bots) without waiting for the clock.
• It asks before touching live players. Making an event live, editing a live event, taking one offline, changing a live guild config, moderating a live guild, or granting to, adjusting or banning a live player all need your explicit confirmation first.

What your key can do

A personal key acts as you, with your current role in the studio it was made for. Change your role and the key changes with it; leave the studio and it stops working.

Some things stay in the dashboard, where you're signed in, whatever your role:

Test API keys and test webhooks can be created through MCP; that's what integration needs.

Read-only keys can list and read everything your role can see, and nothing else. The assistant only sees read tools with one.

Managing keys

• Regenerate or Revoke from the AI & MCP page. The old key stops working immediately.
• The page shows when and from which client your key was last used.
• Owners and admins see every member's key on the same page and can revoke any of them, for example when someone leaves or a key may have leaked.
• Removing a member from the studio revokes their key.
• Every change made with a key is in the audit log under your name, with via: "mcp" in the actor details.

Tools

search_event_catalog explains what an event name means (Lava Quest, Sky Race, King's Cup, Team Battle, season pass, regional or Halloween leaderboards, …): its rules and typical numbers in top games, what its screens usually look like (layout and motion, never art style, which is your game's), and whether Kraty builds it from a template, from an event config, or doesn't support it yet. Co-op kinds (team chest, alliance raid, team tournament, team race, team league, partner event, country cup) are built from the team templates. Besides the templates in the dashboard gallery, the MCP can create a set of agent-only templates (item sprint, group, weekly, flash, weekend, milestone and holiday tournaments, end-game league, step collector, personal sprint, daily quests). They don't appear in the gallery yet, but the events they create show up in the dashboard like any other. When an event runs is your call: the MCP asks, and uses the dates or cadence you give. If you give none, the event gets the template's default schedule (modeled on what top games run for that kind) and the MCP tells you which one it used, so you can change it before the event goes live.

get_event_standings reads any event's current (or a past) window: every board with ranks and scores and, on team events, every team with its score, goal and milestones; pass an eventTeamId for one team's members and milestone payouts. Team events are created like any other (create_event_from_template with a team template, or create_event with a teams block, see get_config_schema("event_teams")), and run_test_action drives them in the test environment: inject_event_scores seats sim players in teams through the real pipeline, set_team_roster, contribute_event_team, recompute_event_team, retry_team_payout.

get_config_schema returns the exact JSON Schema the API validates each payload with, and the registered event types, score formulas, reward policies and bot building blocks. call_admin_api reaches any studio admin route that has no dedicated tool, with the same checks as the dashboard.

Fewer tools

Some clients cap how many tools they load (Cursor, for one). Add a toolsets query to the URL to load one half:

• https://api.kraty.io/mcp?toolsets=integrate: SDK integration only.
• https://api.kraty.io/mcp?toolsets=manage: live ops only.

Using a personal key in scripts

The key also works directly against the studio-scoped admin API, with the same rules:

curl https://api.kraty.io/admin/v1/studios/<studio-slug>/games \
  -H "Authorization: Bearer kraty_pk_..."

It's limited to /admin/v1/studios/<its studio>/… and to 600 requests a minute (240 a minute on /mcp).

Troubleshooting