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
Add the server from your terminal.
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
The first time, your assistant opens Gameheim in the browser. Sign in, check the name of the app and where it will send you back, choose what it may do and in which projects, then confirm with your password (and your verification code, if two-step verification is on).
You can disconnect an app at any time in Integrations, AI assistants. Your LEAD sees the apps connected in the organization and can disconnect them too. A connection closes by itself after 90 days without use and after one year in any case.
Permission
Allows
projects:read
See projects, members, milestones and systems. Always included.
tasks:read
Read tasks and their comments.
tasks:write
Create and edit tasks, change their status, comment.
bugs:read
Read bugs.
bugs:write
Report and edit bugs, change their status, link tasks.
bugs:manage
Manage bug tracker settings, such as creating systems. Needs the bug settings permission.
decisions:read
Read design decisions.
decisions:write
Record and edit decisions, link bugs.
knowledge:read
Search the wiki and the documents you can read.
Assistants ask first for read access only. When one needs to write, it asks you to approve the extra permission.
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
Tool
Does
Needs
list_projects
Projects you can work on, with their code.
projects:read
get_project
Members, open milestones and systems of a project.
projects:read
create_system
Add a system that bugs and decisions are filed under.
bugs:manage
Tasks
Tool
Does
Needs
list_tasks
Tasks of a project, with filters.
tasks:read
get_task
A task with its description and latest comments.
tasks:read
create_task
Create a task.
tasks:write
update_task
Change the fields of a task.
tasks:write
set_task_status
Move a task to another status or set its progress.
tasks:write
add_task_comment
Comment on a task.
tasks:write
Bugs
Tool
Does
Needs
list_bugs
Bugs of a project, with filters.
bugs:read
get_bug
A bug with symptom, reproduction, cause and fix.
bugs:read
create_bug
Report a bug.
bugs:write
update_bug
Change the fields of a bug.
bugs:write
set_bug_status
Move a bug to another status.
bugs:write
create_task_from_bug
Create the task that fixes a bug, already linked.
bugs:read, tasks:write
link_bug_task
Link a task to a bug.
bugs:write, tasks:read
unlink_bug_task
Remove the link between a task and a bug.
bugs:write, tasks:read
Decisions
Tool
Does
Needs
list_decisions
Design decisions of a project, with filters.
decisions:read
get_decision
A decision with its rationale and rejected alternatives.
decisions:read
create_decision
Record a decision. Linking bugs also needs bugs:read.
decisions:write
update_decision
Change the fields of a decision.
decisions:write
set_decision_status
Move a decision to another status.
decisions:write
link_decision_bug
Link a bug to a decision.
decisions:write, bugs:read
Knowledge
Tool
Does
Needs
search_project_knowledge
Passages 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.