GameMaker

GM-Maker MCP Server exposes GameMaker Studio project manipulation as MCP tools that you can invoke from Cursor. It lets you create new GameMaker YY/PY projects, add GML scripts with your code, create objects (with optional event stubs), import sprite animations from image sequences, and list or manage resources within a YYP/YYP project. Each operation is implemented as a tool (for example create_project, add_script, add_object, add_sprite_from_images, list_resources) and validated with type schemas to ensure the correct resource structure is produced. You can drive these tools through natural language in Cursor or invoke them explicitly with a gm-maker prefix, for example Call gm-maker.add_script with { ... } to programmatically add a script to a project. The server maintains proper YYP structure and resource registration so that you can open the resulting project directly in GameMaker Studio.

To use it, configure the MCP server in Cursor (global, project-local, or development mode as described in the README). Once configured, you can issue natural-language actions like “Create a new GameMaker project called MyGame at /Users/you/Projects/MyGame” or “Add a script called player_movement to my GameMaker project” and the MCP server will generate the necessary YY/YYP files, update the resource registry, and write everything to disk. This enables a smooth AI-assisted workflow where Cursor handles high-level intent and the server produces valid GameMaker project artifacts that GameMaker can load without manual file fiddling.

Prerequisites:

• Node.js 18+
• npm or pnpm
• Cursor IDE

Setup steps:

1. Clone the repository and install dependencies:

# From your workspace root
cd /path/to/gm-maker
npm install

2. Build the server:

npm run build

3. (Optional) Test with MCP Inspector to validate tools before using in Cursor:

npm run inspect

4. Start or use the built server in Cursor by configuring the MCP server as described (global or local config). Typical runtime path after build is dist/index.js, which is invoked by Node when running the server.

Tips and notes:

• The server relies on @bscotch/yy for safe parsing and writing of YY/YYP files, so ensure you have GameMaker-compatible project structures when creating resources.
• If you encounter path issues in Cursor, use absolute paths in the workspace configuration or rely on workspaceFolder expansion (e.g., ${workspaceFolder}/dist/index.js).
• Use the MCP Inspector (npm run inspect) to validate tool schemas and arguments before pointing Cursor at the server.
• When using add_object or add_sprite_from_images, make sure the project directory exists or is created prior to resource registration to avoid write errors.
• The commands are designed to be idempotent: running the same operation twice will update resources consistently and re-register with the YYP. Ensure you provide unique resource names to avoid conflicts.
• If you extend the server, keep the Zod schemas in sync with the resource definitions to avoid runtime validation errors.