AI & MCP integration

Connect AI assistants to your Killer games using the Model Context Protocol (MCP).

What is MCP?

The Model Context Protocol (MCP) is an open standard that lets AI clients discover and call tools exposed by a server. Our API implements MCP at /mcp so assistants like Claude, Cursor or Mistral can create games, add players, start parties and more.

Endpoint

The MCP endpoint lives on the API origin. If you self-host, replace the hostname accordingly.

Production

https://api.the-killer.online/mcp

Development

http://localhost:3001/mcp

Authentication

Admin tools need the game's private_token. Pass it in the Authorization header exactly as returned when the game is created. The token is a plain string (not Bearer prefixed).

Create a game first with create_game (no auth required) to obtain a private_token.

Available tools

These tools are exposed by the MCP server. Tools that write data require the game private token.

create_gameCreate a new game (no auth).
get_gameRead a game. Full record only with a valid token.
update_gameRename or reschedule a game.
start_gameStart a game now (needs at least 2 players).
delete_gameDelete a game and all its players.
list_playersList players of a game.
add_playerAdd a player to a game.
update_playerUpdate a player's name or action.
remove_playerRemove a player from a game.

Setup for your AI provider

Most MCP hosts accept an HTTP(S) server when you provide the endpoint URL and a static Authorization header. Choose your client below and copy the matching configuration. Replace YOUR_GAME_PRIVATE_TOKEN with the private token of the game you want to manage.

Claude Code

Claude Code supports remote HTTP MCP servers. Add it from the CLI or write the entry directly in your project .mcp.json or user ~/.claude.json.

{
  "mcpServers": {
    "killer-game": {
      "type": "http",
      "url": "https://api.the-killer.online/mcp",
      "headers": {
        "Authorization": "YOUR_GAME_PRIVATE_TOKEN"
      }
    }
  }
}

Claude Desktop

Claude Desktop currently expects a stdio or SSE server. For a Streamable HTTP endpoint, use a small stdio bridge such as mcp-remote.

{
  "mcpServers": {
    "killer-game": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.the-killer.online/mcp",
        "--header",
        "Authorization:${MCP_AUTH_TOKEN}"
      ],
      "env": {
        "MCP_AUTH_TOKEN": "YOUR_GAME_PRIVATE_TOKEN"
      }
    }
  }
}

Cursor

Cursor auto-detects Streamable HTTP from a url field. Add the entry to your project .cursor/mcp.json or global ~/.cursor/mcp.json.

{
  "mcpServers": {
    "killer-game": {
      "url": "https://api.the-killer.online/mcp",
      "headers": {
        "Authorization": "YOUR_GAME_PRIVATE_TOKEN"
      }
    }
  }
}

Mistral / Le Chat

In Le Chat or Mistral Work, go to Connectors → Add Connector → Custom MCP Connector, paste the server URL and choose HTTP Bearer Token authentication with your game token.

Any other MCP client

If your client accepts an HTTP MCP server, configure the URL and an Authorization header. For stdio-only clients, route requests through a local bridge that forwards JSON-RPC to the HTTP endpoint.

{
  "url": "https://api.the-killer.online/mcp",
  "headers": {
    "Authorization": "YOUR_GAME_PRIVATE_TOKEN"
  }
}

Restart your client after saving the configuration, then approve the server when prompted.

Security tips

The private token grants admin access to a game. Keep it secret, rotate it by deleting and recreating the game if needed, and always use HTTPS in production.

Resources

Interactive API documentation →LLM discovery index →