Runtime Inspection
Query every instance, variable, layer, room, and data structure in your running game. No manual breakpoints needed.
MCP Server for GameMaker
AI-Powered Runtime Debugging
for GameMaker
Connect Claude, Cursor, or VS Code directly to your running GameMaker game. Inspect instances, capture screenshots, simulate input, and debug in real time.
What You Get
A comprehensive MCP server that gives your AI assistant full runtime access to your GameMaker game.
Screenshot Capture
Capture the game screen, GUI layer, or any surface. Compare screenshots to detect visual regressions.
Input Simulation
Simulate keyboard, mouse, and gamepad input. Automate input sequences for repeatable testing scenarios.
Game Control
Pause, resume, step frame-by-frame, and adjust game speed. Full control over execution flow.
Performance Profiling
Track FPS, memory, draw calls, step timing, and texture page utilization. Find bottlenecks fast.
Dynamic GML Execution
Run arbitrary GML code in the running game. Evaluate expressions, patch behavior, and test fixes live.
Architecture
Clean two-layer design with zero overhead in release builds.
AI Client MCP Server GameMaker
(Claude, Cursor, (Node.js, stdio) (GML Extension)
VS Code)
| | |
| --- MCP Protocol ---> | |
| tool call (JSON) | |
| | --- TCP/JSON-RPC 2.0 ---> |
| | request to GML runtime |
| | |
| | <--- response (JSON) ------ |
| | instance data, vars, etc |
| <--- MCP response ----- | |
| structured result | |
Port: stdio Port: 6705 (TCP) #macro MCP_ENABLED
Debug config only
How We Compare
Existing GameMaker MCPs only search documentation. We connect to your running game.
| Capability | Other GameMaker MCPs | GameMaker MCP Pro |
|---|---|---|
| Documentation search | Yes | Yes |
| Runtime instance inspection | No | Yes |
| Variable read/write | No | Yes |
| Screenshot capture | No | Yes |
| Input simulation | No | Yes |
| Game control (pause/step) | No | Yes |
| Performance profiling | No | Yes |
| Dynamic GML execution | No | Yes |
| Physics / collision tools | No | Yes |
| Total tools | 1-5 | 254 |
40 Tool Categories
254 tools organized across every aspect of your GameMaker runtime.
Audio Extended11
Instance10
Drawing10
Buffer10
Variable8
Path8
Documentation8
Timeline7
Shader7
Room7
Input7
Debug7
Variable History6
Tilemap6
Test Framework6
State Debug6
Skeleton6
Screenshot6
Project6
Project File6
Physics6
Particle6
Layer6
GC / Memory6
Game Control6
Filesystem6
Data Structures6
Camera6
Audio6
Animation6
Analytics6
Surface5
Room Settings5
Profiling5
Font5
Collision5
Random4
Code Quality4
Alarm4
Accessibility3
How It Works
Three steps to connect your AI assistant to your running game.
1
Install the Extension
Copy the GML scripts and obj_mcp_server into your GameMaker project. Build the Node.js server with npm install && npm run build.
2
Configure Your AI Client
Point Claude Code, Cursor, or VS Code to the MCP server entry point. The server communicates via stdio with your AI and TCP with your game.
3
Run Your Game
Launch your GameMaker project in Debug config. The MCP extension auto-connects and your AI can now inspect, control, and debug your game in real time.
See It in Action
Watch how GameMaker MCP Pro connects Claude to a running game for real-time debugging.
Simple Pricing
One-time purchase. All 254 tools. All future updates.
GameMaker MCP Pro
$5
One-time payment — not a subscription
- 254 runtime debugging tools
- 40 tool categories
- Screenshot and recording capture
- Input simulation (keyboard, mouse, gamepad)
- Game control (pause, step, speed)
- Dynamic GML execution
- Performance profiling suite
- Zero overhead in release builds
- Works with Claude Code, Cursor, VS Code
- All future updates included
Frequently Asked Questions
Common questions about GameMaker MCP Pro.
What AI clients work with GameMaker MCP Pro?
GameMaker MCP Pro works with any MCP-compatible AI client, including Claude Code (CLI), Claude Desktop, Cursor, Windsurf, and VS Code with Copilot. Any tool that supports the Model Context Protocol can connect.
Does it affect my release builds?
No. The MCP extension is controlled by a
#macro MCP_ENABLED flag and only activates in Debug configuration. Release builds have zero overhead — no network code, no MCP logic is compiled in.
Which GameMaker versions are supported?
GameMaker MCP Pro supports GameMaker 2024 and later (LTS and Beta). It uses standard GML and the built-in TCP networking functions, so it works on all supported platforms.
How is this different from other GameMaker MCPs?
Other GameMaker MCPs only provide documentation search (typically 1-5 tools). GameMaker MCP Pro connects directly to your running game with 254 tools across 40 categories for runtime inspection, screenshot capture, input simulation, game control, physics debugging, performance profiling, and more.
Can I use it for automated testing?
Yes. You can simulate keyboard, mouse, and gamepad input, capture screenshots for visual regression testing, inspect game state assertions, and step through frames one at a time. It's ideal for AI-assisted testing workflows.
Is the source code included?
Yes. You get the full source for both the Node.js MCP server (TypeScript) and the GameMaker GML extension. You can inspect, modify, and extend it to fit your project's needs.