MODEL CONTEXT PROTOCOL FOR GEOMETRY DASH
Let your agent build levels, make macros, write mods and read the game.
GD MCP plugs Claude Code, Codex, Cursor or any HTTP MCP client into a running copy of Geometry Dash. Your agent builds and tests levels, scripts macros, writes mods and reads the game's own code. You keep a record of every call.
01 / ONE SESSION
One prompt in.
Three calls out.
Level edits, macros, mods: your agent picks the tools, runs them in the game and checks the result. You watch every step.
02 / WORKS WITH THE AGENT YOU ALREADY USE
03 / THE TOOLKIT
Thirteen tools,
straight from the game.
The bridge ships these today. The workspace reads them live from your running game, so the list grows when the bridge does.
Build & script
Levels, macros and mods, straight from Python in the game.
- 01run_pythonRun a Python cell on the game thread. Output, last value and traceback come back.CHANGES THE GAME
- 02screenshotSee the screen, the level alone, the player or any node, as a PNG.READ ONLY
- 03find_objectsLook up object IDs by number or by name: spike, orb, move trigger.READ ONLY
- 04read_skillBuilt-in notes on triggers, camera, shaders, groups and eleven more topics.READ ONLY
- 05view_imageShow any image from the shared namespace, a file or a screenshot.READ ONLY
Reverse
Read the game itself, class by class.
- 06search_bindingsSearch game classes, enums, fields and functions by name.READ ONLY
- 07describeA class's fields and functions with Python and C++ signatures.READ ONLY
- 08field_atWhich field sits at a byte offset into an object.READ ONLY
- 09function_infoWhere a function lives, how long it is and whether it is hooked.READ ONLY
- 10disassembleAn x86-64 listing of any game function with calls and strings named.READ ONLY
- 11vtableA class's virtual tables from RTTI, slot by slot.READ ONLY
Reach out
Bring outside knowledge into the session.
- 12http_requestMake an HTTP request from the game's Python and keep the body.NETWORK
- 13search_webSearch the web and get titles, links and snippets back.READ ONLY
04 / FROM ZERO TO FIRST CALL
Three checkpoints.
No practice mode needed.
- 01
Start the bridge.
Launch Geometry Dash with Kinetic and switch on the Python MCP bridge. It listens on 127.0.0.1:8765 and stops when the game closes.
http://127.0.0.1:8765/mcp
- 02
Sign in from the game.
Create an account, then sign gdmcp in with it. One game is signed in at a time, and an admin turns on tool access for your account.
POST /api/site/v1/auth/game/login
- 03
Point your agent at it.
Add the gateway to Claude Code, Codex or Cursor with your token. Prefer clicking? Every tool also runs straight from the dashboard.
{ "mcpServers": { "geometry-dash": { "type": "http", "url": "http://localhost:5000/api/mcp/v1", "headers": { "Authorization": "Bearer <YOUR_JWT>" } } } }
05 / STAY IN CONTROL
Every attempt,
on the record.
The workspace logs what ran, who ran it, with which arguments and how long it took. Crashes included. Especially crashes.
Illustrative dataCall history
From the dashboard and from every connected agent.
- 12:04:31screenshot388 msOK
- 12:04:30run_python212 msOK
- 12:04:29find_objects63 msOK
- 12:03:58run_python1.2 sERRORNameError: name 'plcae' is not defined
- 12:03:40read_skill41 msOK
Game sign-in
gdmcp signs in with your account, on one device at a time.
pixel_wizard
Live discovery
Tools come from your bridge, so new ones show up by themselves.
tools/list13 tools
- run_python
- screenshot
- view_image
- search_bindings
- describe
- function_info
- disassemble
- vtable
- field_at
- read_skill
- find_objects
- http_request
- search_web

LEVEL COMPLETE
You made it to the end.
Now it's your turn.
- Attempts
- 1
- Tools
- 13
- Editor notes
- 15