MCP tools

The KiteFrost MCP server gives AI agents the general project tools (create_project, add_entity, query_context, generate, check_continuity, …) plus four tools that are specific to Game Narrative. Each Game Narrative tool takes a project_id (id or slug) and works only on a Game Narrative project; any other project returns Unknown or unauthorized project.

Setup

{
  "mcpServers": {
    "kitefrost": {
      "command": "kitefrost",
      "args": ["mcp"],
      "env": { "KITEFROST_API_KEY": "sk_your_key_here" }
    }
  }
}

Game Narrative tools

Tool	What it does	Same as REST
`gn_audit_files`	Audit `.ink` / `.yarn` files for continuity breaks. Transient and free; nothing is stored. Limits: 200 files, 2 MB.	`POST /v1/projects/{id}/game-narrative/continuity/audit-files`
`gn_build_lore_bible`	Build the project’s lore bible from its authored characters and quests. Read-only.	`POST /v1/projects/{id}/game-narrative/lore-bible/generate`
`gn_export_dialogue`	Export a dialogue graph as `json`, `ink`, or `yarn`.	`POST /v1/projects/{id}/game-narrative/dialogues/{graph_id}/export`
`gn_audit_cast`	Advisory check for characters that read too alike. Never blocks or changes anything.	`GET /v1/projects/{id}/game-narrative/characters/audit`

Each tool returns the same result as its REST route. For NPC dialogue generation, use the general generate tool or the REST/SDK dialogue routes.

Example: audit an Ink file

{
  "name": "gn_audit_files",
  "arguments": {
    "project_id": "my-game",
    "files": [{ "path": "act1.ink", "content": "=== start ===\nHooper: Hi.\n-> END" }],
    "sarif": false
  }
}

gn_export_dialogue returns {"format": "ink", "content": "..."} for Ink/Yarn and {"format": "json", "graph": {...}} for JSON.

Getting Started

Core Concepts

SDKs

API Reference

Updates

Errors

Setup

Game Narrative tools

Example: audit an Ink file

​Setup

​Game Narrative tools

​Example: audit an Ink file

Setup

Game Narrative tools

Example: audit an Ink file