MCP server for Pyxel, a retro game engine for Python
Connect Pyxel MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for Pyxel, a retro game engine for Python. The pyxel mcp mcp server is what makes that connection.
An MCP server for observing programs built with Pyxel. It runs trusted local scripts headlessly and returns structured state, pixels, assets, audio, and frame differences.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
validate — Syntax errors and recognizable Pyxel code patternsrun — Headless frames, scheduled input, logs, and state, screen_image, screen_grid, or video snapshotspyxel_info — Installed versions, paths, examples, and resource URIsread_palette — Palette colors and image-bank indices in useread_image — Image-bank pixels and an optional PNG renderread_tilemap — Tile coordinates, source bank, usage counts, bounds, and an optional renderread_audio — A rendered sound or music WAV plus measurable audio datadiff_frames — Pixel differences between two PNG filesInstallation goes through your MCP client rather than a global install: point it at pyxel-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Pyxel MCP's toolset — validate, run, pyxel_info and 5 more — is a fair guide to whether it matches your workflow. It is maintained by kitao; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Pyxel MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| validate | Syntax errors and recognizable Pyxel code patterns. |
| run | Headless frames, scheduled input, logs, and state, screen_image, screen_grid, or video snapshots. |
| pyxel_info | Installed versions, paths, examples, and resource URIs. |
| read_palette | Palette colors and image-bank indices in use. |
| read_image | Image-bank pixels and an optional PNG render. |
| read_tilemap | Tile coordinates, source bank, usage counts, bounds, and an optional render. |
| read_audio | A rendered sound or music WAV plus measurable audio data. |
| diff_frames | Pixel differences between two PNG files. |
{
"mcpServers": {
"pyxel": {
"command": "uvx",
"args": ["pyxel-mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.