Use Claude or ChatGPT for game project management
For producers, QA testers and designers who already use an AI assistant and want it to work on the real project instead of pasted fragments. You get concrete workflows that save time on triage, meeting notes and decision records, how access is limited, and what Gameheim offers inside the app when you do not use an external assistant.
Why AI assistants struggle with game project management
Most people on a game team already ask an AI assistant to summarize meeting notes, draft a task list or rewrite a bug report. The trouble is what the assistant does not know. It has never seen your bug list, your milestones or the decisions your team made in March, so every answer depends on what you copy into the chat.
- Copy and paste in both directions. You paste the bug list in, the assistant writes twelve tasks, and you create them one by one by hand. The time saved in writing is spent in transcription.
- Stale context. The list you pasted this morning is already out of date by the afternoon triage.
- Confident answers without sources. Ask "why did we remove the double jump?" and a general assistant will guess. Only your own records hold the real reason.
- Access is all or nothing. Giving a tool a shared account or a copy of the whole project is hard to justify to a lead, a publisher or a client with a non-disclosure agreement.
The Model Context Protocol (MCP) is an open standard that lets an assistant call tools on another service, with your permission. An MCP server for game development gives the assistant live, limited access to the project, so it can read the current state and make changes you ask for, under your account.
How Gameheim connects your AI assistant to the project
Gameheim runs an MCP server. Claude, ChatGPT, Cursor and VS Code can connect to it as a custom connector, and then work with the project in your name. The step-by-step setup for each assistant is on the AI assistants page; this article covers what to do once connected and how access is controlled.
What the assistant can reach
- Projects: the list of projects, their members, open milestones and systems.
- Tasks: list, read, create and edit tasks, change their status and progress, comment.
- Bugs: list with filters, read symptom, steps, cause and fix, report and edit bugs, change their status, create the fix task and link or unlink tasks.
- Decisions: list and read decision records, record and edit them, change their status (including superseding), link bugs.
- Project knowledge: search the wiki pages and documents you can read, and get the matching passages.
How access is limited
- Your LEAD decides who can connect. Connecting needs the External apps (MCP & API) permission, which is not part of the default member role. Read-only accounts can never connect an app.
- Your permissions, never more. The assistant can do only what your role allows. If your role changes, its access changes with it.
- Only the projects you choose. When you connect, you pick All projects I have access to or Only some projects.
- Only the permissions you tick. You can untick what the app does not need. Assistants ask for read access first and ask you to approve write access when they need it.
- Nothing can be deleted. No tool deletes a task, bug, decision or anything else.
- Connections expire. A connection closes after 90 days without use, and after one year in any case. You and your LEAD can disconnect it at any time.
Audit trail
Every change an assistant makes goes through the same checks as a change made in the web app, and is recorded in your name: it shows up in the bug history, the activity and the Audit Log like any other edit, and in the Audit Log the row also names the app, for example via Claude. Connecting and disconnecting an app are recorded in the Audit Log as External app connected and External app disconnected. For how the audit log works, see audit log and account security.
How to connect an AI assistant to Gameheim
The flow is the same for every assistant: add the Gameheim address as a remote MCP server, then approve the connection in Gameheim. Menus inside each assistant differ; the AI assistants page has the exact steps for Claude, Claude Code, ChatGPT, Cursor and VS Code.
- A Gameheim account with the External apps (MCP & API) permission. LEAD accounts have it.
- If your organization requires two-step verification, it must be set up on your account before you connect.
- An assistant that supports remote MCP servers with sign-in (OAuth).
Get the permission from your LEAD
Your LEAD opens Roles & Permissions, edits the role that should connect assistants and ticks External apps (MCP & API):
use. Without it, the consent screen says the app cannot be connected and asks you to contact your LEAD.Copy the Gameheim address
In Gameheim, open Integrations in the sidebar, then Details on the AI assistants card. Under Connect an app, click Copy next to the address.
Add Gameheim to your assistant
In your assistant, add a custom connector (remote MCP server) and paste the address. The assistant then opens Gameheim in your browser. Follow the steps for your assistant on the AI assistants page.
Approve the connection
Gameheim shows Connect <app> to your Gameheim account? Check the name of the app, whether it is marked Verified or Unverified app, and the address under Returns to. Under Permissions, untick what the app does not need. Under Projects, choose All projects I have access to or Only some projects.
Under Confirm it's you, enter your password and, if two-step verification is on, a code. Click Connect. The request is valid for 10 minutes and can be used once.
Start with a read-only question
Ask something like "list my projects in Gameheim" or "which bugs are open in OFT?". When you later ask for a change, the assistant asks you to approve the write permission it needs.
Review or disconnect your apps
The same Integrations, AI assistants page lists Your connected apps, with the projects each one can reach and when it was last used. Disconnect stops an app at once; connecting it again asks for your consent. A LEAD also sees Apps connected by your team and can disconnect any of them, or all at once.
Workflows for producers: status checks and meeting notes to tasks
Always name the project by its code, so the assistant does not have to guess. Keys such as OFT-12 (task), OFT-BUG-5 (bug) and OFT-DEC-3 (decision) work in any request.
- "In OFT, list the tasks due before Friday that are not done yet, grouped by assignee."
- "Here are the notes from the milestone review. Propose one task per action item for the Alpha 2 milestone, with assignee and estimate. Show me the list first, then create them."
- "OFT-44 is finished: set it to done and add a comment that the fix is in the next build."
Workflows for QA: bug triage with an AI assistant
- "List the open bugs in OFT with severity Crash or Blocker that have no fix task yet."
- "Turn this playtest note into a bug in OFT: severity Major, system Combat, with symptom and numbered steps to reproduce. Then create the fix task and assign it to Marco."
- "OFT-BUG-31 describes the same problem as OFT-BUG-28: mark 31 as a duplicate of 28."
- "Read OFT-BUG-12 and rewrite its steps to reproduce so each step is one action, starting from a named save."
The assistant writes to the same fields as the web form, so the result follows your team's conventions. For what makes a good report, see bug tracking for game development.
Workflows for designers: decision records and project knowledge search
- "From this discussion, record a decision in OFT: what we decided, the rationale, and the alternatives we rejected. Status Decided, system Combat."
- "What did we decide about the inventory size, and is it in the code yet?"
- "Link OFT-BUG-40 to decision OFT-DEC-7: the bug is a consequence of that choice."
- "Search the OFT wiki and documents: what is our naming convention for level streaming volumes?"
Project knowledge search returns passages only from wiki pages and documents you are allowed to read. For how to keep decisions useful, see game design decision log.
Good practice when an assistant writes to your project
- Ask for a preview before bulk changes. "Show me the tasks before you create them" costs one message and avoids cleaning up twelve tasks by hand, since nothing can be deleted through the assistant.
- Connect only the projects you work on. Fewer projects means less project data in the conversation.
- Tick only the permissions you use. A designer who only reads bugs and records decisions does not need write access to tasks.
- Check the keys in the answer. The assistant reports the keys of what it created (for example
OFT-BUG-57); open one or two to confirm the result.
What an assistant cannot do through Gameheim
- Delete anything.
- Reach projects you did not choose when connecting, or do anything your role does not allow.
- Work with version control, file locks, crash reports, bug attachments, chat, calendar or the other areas of Gameheim: the tools cover projects, tasks, bugs, decisions and knowledge search.
- Change bug settings, unless you granted the manage permission for bugs and your role holds it. With it, the assistant can add systems.
AI features inside Gameheim
You do not need an external assistant for everything. When AI is available for your organization, people whose role holds AI: use get these features in the web app:
| Where | What it does |
|---|---|
| Wiki, Ask AI | Opens the Project Knowledge Assistant: ask a question about the project wiki and documents, and get an answer with its Sources, limited to what you can access. |
| Wiki editor, AI Assistant | Continue, Improve, Expand, Summarize, Translate or Write text in a page. Use project knowledge grounds Write, Expand and Continue on the project wiki and documents. |
| P4 Workspace submit, Generate with AI | Turns a couple of lines about what you did into a changelist description that follows a Description template of the project. |
The wiki shows, as a percentage, how much of the AI usage included in the plan the studio has used in the current billing cycle. For writing and organizing the design document, see game design document wiki.
Troubleshooting
| What you see | Why, and what to do |
|---|---|
| <app> can't be connected | Your role does not hold External apps (MCP & API), or your account is read-only. Ask your LEAD. |
| Set up two-step verification first | Your organization requires it. Set it up in Gameheim, then start the connection again from the assistant. |
| This request has expired | Connection requests last 10 minutes and work once. Start again from the assistant. |
| Choose at least one project | With Only some projects, tick at least one project. |
| The assistant cannot find a project | The project was not chosen when you connected, or you are not a member of it. Disconnect the app and connect it again to choose other projects. |
| The assistant says it is not allowed to do something | Either you did not grant that permission when connecting (approve it when the assistant asks), or your role does not allow it in Gameheim either. |
| The app stopped working | It was disconnected by you or your LEAD, or it expired after 90 days without use. Connect it again. |
Frequently asked questions
Can I use Claude or ChatGPT for game project management?
Yes. Connect the assistant to Gameheim as a custom connector and it can read and update tasks, bugs and design decisions, and search the project wiki and documents. It works with your own permissions and only in the projects you choose, so you can ask about open blockers or turn meeting notes into tasks without copying data back and forth.
What is an MCP server in game development?
MCP, the Model Context Protocol, is an open standard that lets an AI assistant call tools on another service. An MCP server for a game project exposes things like the bug list, tasks and design decisions as tools, so the assistant reads the current state of the project and makes changes you request, instead of relying on text you paste into the chat.
Is it safe to connect an AI assistant to our game project?
In Gameheim the LEAD decides who can connect, and each connection is limited to the permissions of the person, the projects they pick and the permissions they tick. Nothing can be deleted through the assistant, and connections expire. Keep in mind that tool results reach the assistant provider under your own agreement with them.
Can an AI assistant delete tasks or bugs in Gameheim?
No. The Gameheim tools can create, edit, change status, link and comment, but none of them deletes anything. If an assistant creates something by mistake, fix or close it in the web app, where deleting still requires the right permission. Asking the assistant to show a preview before bulk changes avoids most clean-up.
How do I disconnect an AI assistant from Gameheim?
Open Integrations, then AI assistants, and click Disconnect next to the app under Your connected apps. It stops working at once, and connecting it again asks for your consent. A LEAD can disconnect the apps of any member of the organization, one at a time or all together, from the same page.