GameFrame
Never ship a broken balance patch again.
GameFrame is Git for game design. It gives game studios version control, visual diffs, and branching for game design documents, balance spreadsheets, and narrative files. Eleven AI review personas analyze every change and flag cross-document impact before a balance patch ships broken. GameFrame includes an MCP server for AI agents (Claude Code, Codex, Cursor, etc.) so design data is queryable and editable directly from the agent layer. GameFrame is live at getgameframe.com.
What it does.
- ◇Version control plus visual diffs for GDDs and balance spreadsheets
- ◇11 AI review personas with cross-document impact analysis
- ◇MCP Server for AI agents (Claude Code, Codex, Cursor)
- ◇Branching workflow modeled on Git
- ◇Studio-grade access controls and audit trail
Pricing.
Free for individuals
Per editor / month
Per editor / month
Contact sales
Common questions.
What problem does GameFrame solve?
GameFrame stops broken balance patches from shipping. Game studios edit GDDs, balance spreadsheets, and narrative docs in parallel without proper version control. GameFrame brings Git-style branching, diffs, and AI cross-document review to that workflow.
Is GameFrame for code or for design?
GameFrame is for design. It versions GDDs, balance tables, narrative documents, and the relationships between them. Code stays in your existing Git host.
What does the MCP server do?
The MCP server exposes GameFrame design data to AI agents like Claude Code, Codex, and Cursor. The agent can query a balance table, propose a change, or open a branch directly from the chat surface.