cbm-mcp
Provides tools for debugging Commodore software in a locally running VICE emulator via VICE's text remote monitor, including CPU/memory/screen inspection, disassembly/assembly, execution control, breakpoints/watchpoints, state modification, media/file operations, profiling, and graphics export.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
CBM MCP: VICE Monitor
CBM MCP lets AI agents use the text monitor of a locally running VICE emulator. The recommended setup is a shared HTTP service: VICE accepts one monitor connection, so separate stdio servers can conflict or leave connections stuck.
Quick Start
You need Node.js 24+ and VICE with its text remote monitor enabled.
Start VICE with the text monitor (the executable name depends on your installation):
x64sc -remotemonitor -remotemonitoraddress ip4://127.0.0.1:6510For the recommended APM setup, install the project in your agent workspace:
apm install thred/cbm-mcpAPM configures the MCP endpoint and deploys the CBM MCP agent skill. Start the HTTP service separately and leave it running while using VICE:
npx --yes cbm-mcp@latest --httpIf you are not using APM, configure your MCP client to connect to:
http://127.0.0.1:3000/mcp
The HTTP service listens on 127.0.0.1:3000 by default. Set
CBM_MCP_HTTP_PORT to change the port. The service does not start VICE.
Keep it on loopback and use trusted clients; set CBM_MCP_HTTP_TOKEN to
require bearer authentication.
Shared HTTP Service
The HTTP service shares one VICE monitor connection across MCP sessions. Run only one service for a VICE instance, and remove any stdio configuration that could connect to the same emulator. Connecting to VICE pauses emulation; resume it deliberately when you are ready.
stdio (not recommended)
stdio is supported, but each MCP client starts its own server. Since VICE only
accepts one monitor connection, clients can interfere with one another or
encounter connection issues. For a single-client setup, run
npx --yes cbm-mcp@latest and configure the client to launch that command over
stdio.
Related MCP server: C64 Debug MCP
More Information
Development
Install dependencies and run the build and tests:
npm install
npm run build
npm test
npm run test:typecheckFor VICE-backed checks, start VICE with its text monitor and run
npm run test:live. This pauses the emulator and leaves it paused. The live
test is skipped by default.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Live browser debugging for AI assistants — DOM, console, network via MCP.
Persistent memory, hybrid search and a goal graph for AI agents, over stdio or remote HTTP.
Connect ChatGPT, Claude, Cursor or VS Code to your Windows PC: files, terminal, browser, apps.
AI Agent Utility Layer for agent safety, web monitoring, crypto research and tool discovery.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables autonomous debugging of Commodore 64 programs through the VICE emulator with semantic interpretation of C64-specific data structures, memory layouts, VIC-II states, and PETSCII encoding for AI-assisted 6502 assembly debugging.261MIT
- AlicenseAqualityDmaintenanceEnables AI-powered control and debugging of Commodore 64 programs via the VICE emulator, supporting memory operations, breakpoints, register access, and program loading.188 npmMIT
- AlicenseBqualityBmaintenanceEnables AI agents to code and debug Commodore PET software using the VICE emulator, with CLI and MCP tools for session control, screen reading, memory manipulation, and testing.441MIT
- AlicenseNot gradedqualityBmaintenanceLets AI clients control and program a Commodore 64, including running programs, reading/writing memory, rendering graphics, playing sound, and switching between C64 Ultimate hardware and VICE emulation.388 npm43GPL 2.0