Build GameMaker projects with AI in Cursor
An MCP (Model Context Protocol) server that brings GameMaker Studio development directly into your AI-powered workflow. Create YYP projects, add scripts, objects, and sprites using natural language in Cursor IDE.
This server exposes GameMaker project manipulation as MCP tools, letting you:
- Create new GameMaker YYP projects from scratch
- Add GML scripts with your code
- Create objects with event definitions
- Import sprite animations from image sequences
- List and manage project resources
- Maintain proper YYP/YY file structure automatically
All through natural language conversations with AI in Cursor.
This project is built on the excellent work by Butterscotch Shenanigans, the indie game studio behind Crashlands, Levelhead, and other amazing games. They've open-sourced their entire GameMaker tooling suite called Stitch.
Specifically, this MCP server uses:
- @bscotch/yy - Robust parsing and writing of GameMaker YY/YYP files
- Their extensive TypeScript type definitions for GameMaker resources
- Their battle-tested approach to programmatic GameMaker project manipulation
Without their incredible open-source contributions to the GameMaker ecosystem, this project wouldn't be possible. Thank you, Butterscotch Shenanigans! 🧈
This MCP server was created while building Soulbound, a game project that needed better AI-assisted GameMaker development workflows in Cursor. The goal was simple: make Cursor understand GameMaker projects so it could help write GML code, create objects, and manage resources without breaking the YYP structure.
Instead of manually creating GameMaker resources and switching between the IDE and Cursor, this tool lets you stay in the AI-powered flow and have Cursor handle the tedious project setup work.
This MCP server bridges GameMaker Studio development with modern AI-assisted workflows:
-
Foundation: Built on Butterscotch's @bscotch/yy library, which provides safe, validated reading and writing of GameMaker's JSON-like YY/YYP file formats.
-
MCP Protocol: Implements the Model Context Protocol from Anthropic, which allows AI assistants to call structured tools via a standard interface.
-
Cursor Integration: Configured to run as a stdio-based MCP server that Cursor can launch and communicate with, exposing GameMaker operations as callable tools.
-
Type Safety: Written in TypeScript with full type definitions from the @bscotch packages, ensuring robust file generation.
-
Architecture: Each tool (create_project, add_script, etc.) follows a consistent pattern:
- Validate parameters with Zod schemas
- Load existing YYP or create new project structure
- Generate proper YY resource files
- Update YYP resource registry
- Write everything back using Butterscotch's safe write methods
The result: You can now say "create a player object with a step event" in Cursor, and the AI will generate a proper GameMaker object with all the right YY file structure, registered in the YYP, ready to open in GameMaker Studio.
Born from real game development needs, this tool makes AI-assisted GameMaker development actually practical.
- create_project - Scaffold a new .yyp project
- add_script - Create a GML script and register it in the YYP
- add_object - Create a .yy object with optional event stubs
- add_sprite_from_images - Import frames from a directory and register a sprite
- list_resources - Enumerate resources by type (scripts, objects, sprites)
- Node.js 18+
- npm or pnpm
- Cursor IDE
- Clone and install dependencies:
cd /Users/webb/Repos/mcp-yyp
npm install- Build the server:
npm run build- Test with MCP Inspector (optional but recommended):
npm run inspectThis opens the MCP Inspector to validate your tools before using them in Cursor.
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"gm-maker": {
"command": "node",
"args": ["/Users/webb/Repos/mcp-yyp/dist/index.js"],
"env": {}
}
}
}Add to .cursor/mcp.json in your workspace:
{
"mcpServers": {
"gm-maker": {
"command": "node",
"args": ["${workspaceFolder}/dist/index.js"]
}
}
}For development with hot-reload:
{
"mcpServers": {
"gm-maker": {
"command": "npx",
"args": ["tsx", "/Users/webb/Repos/mcp-yyp/src/index.ts"]
}
}
}After adding the configuration, restart Cursor to load the MCP server.
Once configured, you can use natural language in Cursor to interact with GameMaker projects:
"Create a new GameMaker project called MyGame at /Users/webb/Projects/MyGame"
Or explicitly:
Call gm-maker.create_project with { "projectDir": "/Users/webb/Projects/MyGame", "name": "MyGame" }
"Add a script called player_movement to my GameMaker project at /Users/webb/Projects/MyGame"
Or with code:
Call gm-maker.add_script with {
"projectDir": "/Users/webb/Projects/MyGame",
"scriptName": "player_movement",
"code": "function move_player(spd) {\n x += spd;\n}"
}
"Create an object called obj_player with a Create event in my project"
Or explicitly:
Call gm-maker.add_object with {
"projectDir": "/Users/webb/Projects/MyGame",
"objectName": "obj_player",
"events": [{"eventType": 0, "eventNum": 0}]
}
Common GameMaker event types:
0= Create1= Destroy2= Alarm3= Step4= Collision8= Draw
"Import PNG frames from /Users/webb/Assets/portal as a sprite called spr_portal"
Or explicitly:
Call gm-maker.add_sprite_from_images with {
"projectDir": "/Users/webb/Projects/MyGame",
"spriteName": "spr_portal",
"framesDir": "/Users/webb/Assets/portal"
}
"Show me all scripts in my GameMaker project"
Or explicitly:
Call gm-maker.list_resources with {
"projectDir": "/Users/webb/Projects/MyGame",
"kind": "scripts"
}
npm run dev- Run in development mode with tsxnpm run build- Build for productionnpm run start- Run built versionnpm run inspect- Open MCP Inspector for testing
gm-maker/
├── src/
│ ├── index.ts # MCP server entrypoint
│ └── gm/
│ ├── types.ts # TypeScript types
│ ├── yyp.ts # YYP project operations
│ ├── scripts.ts # Script creation
│ ├── objects.ts # Object creation
│ └── sprites.ts # Sprite creation
├── dist/ # Built output
├── package.json
├── tsconfig.json
└── README.md
- @modelcontextprotocol/sdk - MCP protocol implementation
- @bscotch/yy - Safe GameMaker YY/YYP file parsing and writing
- zod - Runtime type validation
This server uses the stdio transport protocol to communicate with Cursor. Each tool:
- Validates input parameters using Zod schemas
- Loads the existing YYP file (or creates a new one)
- Performs file system operations for the resource
- Updates the YYP resource list
- Writes the updated YYP back to disk
The @bscotch/yy library ensures all YY/YYP files maintain proper structure and don't get corrupted.
Current limitations:
- Sprite metadata (width, height, bbox) uses defaults - manual adjustment may be needed
- No support for rooms, sounds, or other advanced resources yet
- Event GML files are created with stub comments
Potential enhancements:
- Add
update_scriptto modify existing script code - Add
delete_resourcefor removing resources - Add
create_roomfor room creation - Add
build_projectusing GameMaker CLI/Igor - Integration with @bscotch/gml-parser for code refactoring
- Butterscotch Stitch Monorepo - The foundation this project is built on
- @bscotch/yy Package - GameMaker file parsing/writing
- Model Context Protocol - The protocol specification
- Cursor MCP Documentation - How to use MCP in Cursor
- GameMaker Manual - Official GameMaker documentation
- Butterscotch Shenanigans - The studio behind the tooling
- Butterscotch Blog - Great articles on GameMaker workflows
This is an experimental project exploring AI-assisted GameMaker development. Contributions, ideas, and feedback are welcome!
Areas for improvement:
- Additional resource types (rooms, sounds, shaders, etc.)
- Better sprite metadata handling
- GML code parsing and refactoring
- Project build automation
- Integration with GameMaker CLI/Igor
MIT License - See LICENSE file for details
- Butterscotch Shenanigans for creating and open-sourcing Stitch
- Anthropic for the Model Context Protocol
- Cursor for pioneering AI-first IDE experiences
- The GameMaker community for being awesome
Built with ☕ while developing Soulbound. Created for the GameMaker community. Made possible by Butterscotch Shenanigans' amazing open-source tools.