Gameheim

AI assistants

Use Gameheim with your AI assistant

If you already work with Claude, ChatGPT or Cursor, connect it to your Gameheim project. Your assistant can then read and update tasks, bugs and design decisions, and search the project documentation, while you keep talking to it the way you do today. It runs on your own subscription.

What you can ask

A few examples from producers, designers, QA and programmers. Write them in your own words: the assistant picks the right Gameheim tool.

  • Which blocker bugs are still open in OFT, and who is working on them?
  • Here are my notes from today’s meeting: create a task for each action item and assign it.
  • Report this crash as a bug, with the log I am pasting, and create the task that fixes it.
  • What did we decide about the inventory system, and why?
  • What is left for me this week? Move the task I just finished to done.
  • Search the wiki: how do we name level streaming volumes?

Before you start

  • Your role needs the External apps (MCP & API) permission. Your LEAD grants it in the role editor; read-only accounts cannot connect apps.
  • An assistant can do only what you can do, and only in the projects you choose when you connect.
  • Nothing can be deleted through Gameheim’s tools.

The address of Gameheim for your assistant is:

https://api.gameheim.com/api/mcp

Connect your assistant

Menus change from one release to the next: if a step does not match what you see, follow the assistant’s own guide linked in each box.

Claude Code

  1. Add the server from your terminal.
  2. In Claude Code, run /mcp, pick gameheim and choose Authenticate. Your browser opens Gameheim to confirm the connection.
Terminal
claude mcp add --transport http gameheim https://api.gameheim.com/api/mcp
Claude Code documentation

Claude (claude.ai and Claude Desktop)

  1. Open Customize, then Connectors.
  2. Click +, then Add custom connector, paste the Gameheim address and click Add.
  3. Click Connect: Claude opens Gameheim to confirm the connection.
  4. On Team and Enterprise plans an Owner adds the connector once in Organization settings, Connectors; each member then clicks Connect.
Claude (claude.ai and Claude Desktop) documentation

ChatGPT

  1. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.
  2. In Settings, Security and login, turn on Developer mode.
  3. Create a developer-mode app for a remote MCP server with the Gameheim address and OAuth authentication.
  4. ChatGPT opens Gameheim in a popup to confirm the connection: allow popups for chatgpt.com.
ChatGPT documentation

Cursor

  1. Add Gameheim to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for every project.
  2. Cursor asks you to sign in the first time it uses the server.
mcp.json
{
  "mcpServers": {
    "gameheim": {
      "url": "https://api.gameheim.com/api/mcp"
    }
  }
}
Cursor documentation

VS Code

  1. Add Gameheim to .vscode/mcp.json in your workspace.
  2. VS Code asks you to sign in when it first starts the server.
.vscode/mcp.json
{
  "servers": {
    "gameheim": {
      "type": "http",
      "url": "https://api.gameheim.com/api/mcp"
    }
  }
}
VS Code documentation

Your data

What a tool returns becomes part of your conversation with the assistant, and so reaches its provider (for example Anthropic or OpenAI) under your agreement with them. That is why the permission is granted by your LEAD, and why you choose the projects each app can reach.

Every change an assistant makes is recorded in the audit log with the app that made it.

Tools

For the technically curious: Gameheim connects through the Model Context Protocol (MCP), and these are the tools your assistant can call. Tasks, bugs and decisions have a key such as OFT-12, OFT-BUG-5 or OFT-DEC-3. Texts are Markdown.

Projects

ToolDoesNeeds
list_projectsProjects you can work on, with their code.projects:read
get_projectMembers, open milestones and systems of a project.projects:read
create_systemAdd a system that bugs and decisions are filed under.bugs:manage

Tasks

ToolDoesNeeds
list_tasksTasks of a project, with filters.tasks:read
get_taskA task with its description and latest comments.tasks:read
create_taskCreate a task.tasks:write
update_taskChange the fields of a task.tasks:write
set_task_statusMove a task to another status or set its progress.tasks:write
add_task_commentComment on a task.tasks:write

Bugs

ToolDoesNeeds
list_bugsBugs of a project, with filters.bugs:read
get_bugA bug with symptom, reproduction, cause and fix.bugs:read
create_bugReport a bug.bugs:write
update_bugChange the fields of a bug.bugs:write
set_bug_statusMove a bug to another status.bugs:write
create_task_from_bugCreate the task that fixes a bug, already linked.bugs:read, tasks:write
link_bug_taskLink a task to a bug.bugs:write, tasks:read
unlink_bug_taskRemove the link between a task and a bug.bugs:write, tasks:read

Decisions

ToolDoesNeeds
list_decisionsDesign decisions of a project, with filters.decisions:read
get_decisionA decision with its rationale and rejected alternatives.decisions:read
create_decisionRecord a decision. Linking bugs also needs bugs:read.decisions:write
update_decisionChange the fields of a decision.decisions:write
set_decision_statusMove a decision to another status.decisions:write
link_decision_bugLink a bug to a decision.decisions:write, bugs:read

Knowledge

ToolDoesNeeds
search_project_knowledgePassages of the wiki and documents that match a question.knowledge:read

Workflows for your team

Bug triage, meeting notes turned into tasks, decision records and project knowledge search, role by role: see AI assistants for game projects.

Building your own integration?

The same operations are available as a REST API, in preview. See the API reference.