home / mcp / c64 bridge mcp server

C64 Bridge MCP Server

Provides an MCP server to drive a Commodore 64 Ultimate/VICE via REST APIs and local IO, for program execution, memory access, and system control.

Installation
Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "chrisgleissner-c64bridge": {
      "command": "npx",
      "args": [
        "-y",
        "c64bridge@latest"
      ]
    }
  }
}

You run an MCP server that talks to a real Commodore 64 hardware setup or a simulated one, enabling AI-assisted control, scripting, and experimentation over safe, documented interfaces. This guide shows you how to use the C64 Bridge MCP server, install it, and configure reliable local or remote access so you can drive BASIC, memory, I/O, SID, printers, and more from your preferred MCP client.

How to use

You connect to the server from an MCP client (for example, an IDE or automation tool that speaks the MCP protocol). Start the server with one of the supported runtimes, then call the exposed tools to upload programs, read memory, reset the machine, control the SID, manage drives, and perform maintenance tasks. Use the standard IO-based channel for low-latency, local integration, or enable HTTP access when you need to reach the server from another host. For common workflows, you typically upload a PRG or BASIC program, run it, monitor the screen output, and verify memory and system state through the provided tools.

How to install

Prerequisites: you need Node.js 24+ and npm installed on your system.

Choose one of the run methods below. Each method starts the MCP server and makes it ready to accept MCP calls.

Run with npx (zero setup)

npx -y c64bridge@latest

Run locally with npm (project‑local)

Create a local project, install the package, and start the server with Node.

mkdir -p ~/c64bridge && cd ~/c64bridge
npm init -y
npm install c64bridge
node ./node_modules/c64bridge/dist/index.js

Run from source (contributing/testing)

Clone the source, install dependencies, and start the server as you would during development.

git clone https://github.com/chrisgleissner/c64bridge.git
cd c64bridge
npm install
npm start

Available tools

c64_config

Configuration management and diagnostics for the Ultimate hardware, including reading and writing settings, diagnostics, and snapshots.

c64_disk

Manage disk images and drives, including mounting, listing, and creating images.

c64_drive

Control drive power, mode, and ROM operations for the emulated or hardware unit.

c64_extract

Extract memory contents, sprites, and firmware health information to analyze or reuse data.

c64_graphics

Create PETSCII art and manage graphics-related assets.

c64_memory

Read and write memory ranges, read the screen, and monitor text output.

c64_printer

Interact with printer output and character definitions for on-device printing.

c64_program

Upload, run, and batch manage PRG/CRT programs on the target machine.

c64_rag

Provide reference lookup for BASIC and assembly snippets from the knowledge base.

c64_sound

Control SID playback, composition, and analysis workflows.

c64_stream

Manage streaming sessions from the Ultimate hardware for remote targets.

c64_system

Power, reset, and background task control for the machine.