playdate-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLAYDATE_SIMCTL_PATH | No | Override the bundled playdate-simctl | |
| PLAYDATE_SIMCTL_AGENT_PATH | No | Value passed to --agent | |
| PLAYDATE_SIMCTL_TIMEOUT_MS | No | Positive timeout in milliseconds; defaults to 300000 | 300000 |
| PLAYDATE_SIMULATOR_APP_PATH | No | Value passed to --simulator-app | |
| PLAYDATE_SIMCTL_WORKING_DIRECTORY | No | Working directory for relative paths |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| playdate_runA | Run the project's mise build task, launch or find Playdate Simulator, inject the control agent, and load the PDX. This is the normal first call and reload workflow. |
| playdate_statusA | Find the selected Simulator, ensure its control agent is available, and return agent status. This may inject the agent when it is absent. |
| playdate_loadA | Load an existing PDX directory bundle without running a build task. |
| playdate_pressA | Press and release a button for a bounded duration. Lock toggles immediately and does not accept duration_ms. |
| playdate_set_buttonA | Hold or release one button for deterministic and simultaneous input sequences. |
| playdate_set_crankA | Set the crank position in degrees or set whether the crank is docked. |
| playdate_set_accelerometerB | Set the Simulator accelerometer x, y, and z values. |
| playdate_set_volumeA | Set volume to percent, or adjust it up or down by percent. Adjustment defaults to 10 percent when percent is omitted. |
| playdate_set_pausedA | Pause or resume the running game. |
| playdate_restartB | Restart the currently loaded game, resetting its runtime state. |
| playdate_toggle_lockB | Toggle the Simulator's Playdate lock state. |
| playdate_capture_screenshotA | Capture the 400 by 240 framebuffer to a new PNG path and return it as MCP image content. Existing files are never overwritten. |
| playdate_recordA | Start recording to a new GIF path or stop and finalize the active recording. Recording state belongs to the Simulator agent, not this MCP server. |
| playdate_toolbarA | Invoke an exact Simulator toolbar action. The gif action may open a Save Recording dialog; use playdate_record for non-interactive GIF capture. |
| playdate_injectA | Diagnostic primitive that finds the selected Simulator and ensures its control agent is available. Normal control tools inject automatically. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Most control tools target distinct inputs or actions, but playdate_status and playdate_inject heavily overlap in finding the Simulator and ensuring the agent is available. playdate_run and playdate_load are also closely related, though descriptions clarify their build/no-build distinction.
All tools share the playdate_ prefix and mostly use clear verb-first names like playdate_set_crank and playdate_capture_screenshot. Minor deviations like playdate_status and playdate_toolbar are noun-style rather than verb-style, but the overall pattern remains readable and predictable.
Fifteen tools is at the upper edge of well-scoped for a simulator-control server, and each tool covers a meaningful action or input surface. The redundant playdate_inject and broad playdate_toolbar add slight bulk but do not make the set feel bloated.
The tool surface covers the core Simulator lifecycle—build/run/load, restart, pause, status—plus key input methods, volume, lock state, screenshots, and recording. Minor gaps exist around advanced Simulator state or explicit simulator selection, but common workflows are fully supported.