# C64 Bridge [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/chrisgleissner/c64bridge  
**GitHub Stars:** 39  
**npm Downloads (last month):** 1180  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/c64-bridge

## Description
MCP server for Commodore 64 Ultimate hardware and VICE emulator control.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "c64-bridge": {
    "command": "npx",
    "args": ["-y","c64bridge@latest"],
    "env": {
      "C64_MODE": "",
      "C64U_HOST": "",
      "VICE_BINARY": "",
      "VICE_DIRECTORY": "",
      "VICE_VISIBLE": "",
      "VICE_WARP": ""
    }
  }
}
```

**Requires environment variables:** `C64_MODE`, `C64U_HOST`, `VICE_BINARY`, `VICE_DIRECTORY`, `VICE_VISIBLE`, `VICE_WARP` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What C64 Bridge MCP server does

The C64 Bridge MCP server gives an AI client a common interface for working with Commodore 64 environments. It can target C64 Ultimate or Ultimate 64 hardware, U2-family cartridges, VICE, or a combination of these backends. When multiple backends are configured, the active target can be changed during a conversation.

The available operations cover program execution, memory access, graphics, sound, input, disk and drive activity, printer workflows, system tasks, debugging, and streaming. The server also includes resources and prompts intended to support C64-related workflows, plus knowledge retrieval through its RAG functionality.

Typical uses include running BASIC, 6510 assembly, PRG, or CRT programs; reading and writing memory; polling the screen; controlling peripherals; and working with SID music. The exact behavior depends on the selected backend and its connection to the host system.

## How it works

C64 Bridge MCP server is implemented with the official TypeScript Model Context Protocol SDK. An MCP client starts the process and communicates with it over stdio, which is the normal mode for local AI integrations. The server probes the selected target and runs connectivity checks at startup.

An optional HTTP bridge is available for manual inspection. The tool interface is organized into named groups, including `c64_program`, `c64_memory`, `c64_graphics`, `c64_sound`, `c64_disk`, `c64_drive`, `c64_input`, `c64_debug`, and `c64_select_backend`. Other groups cover configuration, extraction, printers, streaming, system functions, VICE control, batching, and RAG.

The backend modes are `c64u` for C64U or U64 hardware, `u2` for U2, U2+, or U2+L cartridges, and `vice` for the VICE emulator. Runtime selection makes it possible to use hardware and emulation through the same MCP conversation when both are configured.

## Setup and configuration

Install Node.js 24 or later and npm before starting. The shortest installation path runs the published package with:

```bash
npx -y c64bridge@latest
```

Alternatively, install the npm package locally and start its compiled entry point, or clone the repository and use its build and start commands for development or testing.

After installation, configure one or more backends. The repository documents configuration-file lookup order, merge behavior, backend-specific settings, and runtime overrides. The VS Code installation example includes `C64_MODE`, `C64U_HOST`, `VICE_BINARY`, `VICE_DIRECTORY`, `VICE_VISIBLE`, and `VICE_WARP`; these values select the target and describe the local VICE setup in that example.

Connect the running process from VS Code, Cursor, Claude Code, or another MCP client. The project supports Linux, macOS, and Windows according to its platform badge.

## Tools and capabilities

- Execute BASIC, 6510 assembly, PRG, and CRT programs.
- Read and write raw C64 memory and poll screen state.
- Render graphics and manage sound-related operations.
- Play, compose, generate, and verify SID music.
- Work with disks, drives, files, printers, input, and system tasks.
- Debug, stream, batch operations, extract data, and retrieve C64 knowledge.
- Select between configured C64 hardware, U2-family hardware, and VICE backends.

## Limitations and notes

The server requires a reachable configured target for hardware or emulator operations. Hardware connections need the relevant C64U/U64 or U2-family device, while VICE requires an installed emulator and its configured binary and support directory.

The documented quick start expects Node.js 24.x. The HTTP bridge is described as optional and intended for manual inspection; stdio is the primary local integration mode. No specific C64 program, disk image, or hardware device is bundled by the server.

_Full upstream README: https://allmcps.com/mcp/c64-bridge/readme_