Log inSubmit server
C64 Bridge logo

C64 Bridge

Control Commodore 64 hardware or VICE from an MCP client with tools for programs, memory, graphics, sound, storage, and input.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install C64 Bridge

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "c64-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "c64bridge@latest"
      ],
      "env": {
        "C64_MODE": "YOUR_VALUE_HERE",
        "C64U_HOST": "YOUR_VALUE_HERE",
        "VICE_BINARY": "YOUR_VALUE_HERE",
        "VICE_DIRECTORY": "YOUR_VALUE_HERE",
        "VICE_VISIBLE": "YOUR_VALUE_HERE",
        "VICE_WARP": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y c64bridge@latest

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked Today.

Overview

The C64 Bridge MCP server connects AI clients to C64 Ultimate, Ultimate 64, U2-family cartridges, and VICE emulator sessions. It exposes grouped MCP tools for running programs, accessing memory, working with graphics and sound, handling storage and peripherals, and retrieving C64 knowledge. Run it locally over stdio or use its optional HTTP bridge for manual inspection. Reach for it when an agent needs to develop, test, inspect, or operate Commodore 64 software across hardware and emulation.

Use cases

  • Run and inspect C64 programs from an AI client
  • Read and modify Commodore 64 memory
  • Switch between VICE and connected C64 hardware
  • Control SID playback and sound workflows
  • Automate disk, drive, printer, and input tasks

Key features

  • C64 Ultimate, Ultimate 64, U2-family, and VICE backends
  • Program execution for BASIC, 6510 assembly, PRG, and CRT
  • Memory access and screen polling
  • Graphics, sound, SID, input, and peripheral tools
  • Runtime backend switching
  • stdio transport with optional HTTP bridge

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

8/8 checks healthy over the last 43d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · c64bridge@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars39Stargazers on the source repository.
npm downloads1.2kPackage downloads in the last 30 days.
Last commit10d agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.

How C64 Bridge works

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:

Terminal
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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about C64 Bridge

C64 Bridge is an MCP server that connects AI clients to C64 Ultimate, Ultimate 64, U2-family cartridge hardware, and the VICE emulator. Its main tools run programs, read and write memory, control graphics, sound, input, disks, drives, printers, debugging, and backend selection.

Install Node.js 24 or later, then run `npx -y c64bridge@latest`. You can also install the npm package locally and start its compiled entry point, or clone the repository and use its build commands for development.

Yes, C64 Bridge works with Cursor through its stdio MCP configuration. The README includes a Cursor installation link with an `npx` command and example settings for C64 Ultimate and VICE.

Yes, it can switch backends at runtime when multiple targets are configured. Use the `c64_select_backend` tool to select C64U, U2-family hardware, or VICE for the current workflow.

The documented configuration includes `C64_MODE`, `C64U_HOST`, `VICE_BINARY`, `VICE_DIRECTORY`, `VICE_VISIBLE`, and `VICE_WARP`. The example values select a backend and describe the VICE executable, support directory, window visibility, and warp behavior.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewC64 Bridge AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/c64-bridge?style=directory)](https://allmcps.com/mcp/c64-bridge)
HTML Embed
<a href="https://allmcps.com/mcp/c64-bridge"><img src="https://allmcps.com/api/badge/c64-bridge?style=directory" alt="C64 Bridge on AllMCPs" /></a>