Skip to content
MCP server

C64 Bridge

Run programs, read memory and play sound on a Commodore 64 or VICE from an AI client

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI, self-hosted, Linux
Runs
Locally
Version
1.2.0
Listing updated
today

Similar MCP servers

About C64 Bridge

C64 Bridge is an open-source MCP server for developer tools. It runs locally on your machine and is started by your AI client.

C64 Bridge points an AI client at real Commodore 64 hardware or an emulator. It targets the C64 Ultimate, Ultimate 64 and U2-family cartridges, and can switch to a VICE emulator session at runtime, so one conversation can move between hardware and emulation. The tools are grouped by area rather than one per action, for example c64_program, c64_memory, c64_graphics and c64_sound.

What an agent can do includes running BASIC, 6510 assembly and PRG or CRT files, reading and writing memory including screen polling, driving disks, drives and printers, and composing, generating and verifying SID music. Built-in resources, skills and retrieval give the assistant background on classic C64 programming and on Ultimate features such as REU, CPU turbo, ten SIDs, LED control, UCI networking and full-colour border graphics.

It runs over stdio, with an optional HTTP bridge for manual inspection, needs Node.js 24 or newer, and reads backend settings from a config file or environment variables. A VS Code agent mode is documented. The README shows a GPL-2.0 licence badge.

Install

Run in a terminal

claude mcp add c64bridge --env C64BRIDGE_HTTP_TOKEN='<C64BRIDGE_HTTP_TOKEN>' --env C64U_PASSWORD='<C64U_PASSWORD>' --env U2_PASSWORD='<U2_PASSWORD>' --env GITHUB_TOKEN='<GITHUB_TOKEN>' -- npx -y c64bridge

Add to claude_desktop_config.json

{
  "mcpServers": {
    "c64bridge": {
      "command": "npx",
      "args": [
        "-y",
        "c64bridge"
      ],
      "env": {
        "C64BRIDGE_HTTP_TOKEN": "<C64BRIDGE_HTTP_TOKEN>",
        "C64U_PASSWORD": "<C64U_PASSWORD>",
        "U2_PASSWORD": "<U2_PASSWORD>",
        "GITHUB_TOKEN": "<GITHUB_TOKEN>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "c64bridge": {
      "command": "npx",
      "args": [
        "-y",
        "c64bridge"
      ],
      "env": {
        "C64BRIDGE_HTTP_TOKEN": "<C64BRIDGE_HTTP_TOKEN>",
        "C64U_PASSWORD": "<C64U_PASSWORD>",
        "U2_PASSWORD": "<U2_PASSWORD>",
        "GITHUB_TOKEN": "<GITHUB_TOKEN>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "c64bridge": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "c64bridge"
      ],
      "env": {
        "C64BRIDGE_HTTP_TOKEN": "<C64BRIDGE_HTTP_TOKEN>",
        "C64U_PASSWORD": "<C64U_PASSWORD>",
        "U2_PASSWORD": "<U2_PASSWORD>",
        "GITHUB_TOKEN": "<GITHUB_TOKEN>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "c64bridge": {
      "command": "npx",
      "args": [
        "-y",
        "c64bridge"
      ],
      "env": {
        "C64BRIDGE_HTTP_TOKEN": "<C64BRIDGE_HTTP_TOKEN>",
        "C64U_PASSWORD": "<C64U_PASSWORD>",
        "U2_PASSWORD": "<U2_PASSWORD>",
        "GITHUB_TOKEN": "<GITHUB_TOKEN>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "c64bridge": {
      "command": "npx",
      "args": [
        "-y",
        "c64bridge"
      ],
      "env": {
        "C64BRIDGE_HTTP_TOKEN": "<C64BRIDGE_HTTP_TOKEN>",
        "C64U_PASSWORD": "<C64U_PASSWORD>",
        "U2_PASSWORD": "<U2_PASSWORD>",
        "GITHUB_TOKEN": "<GITHUB_TOKEN>"
      }
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • LOG_LEVELLogger verbosity.
  • C64BRIDGE_CONFIGPath to the C64 Bridge configuration file.
  • C64BRIDGE_ALLOWED_DIRSAdditional directories allowed for host file paths in tool arguments, separated by the path delimiter; * disables the check.
  • C64BRIDGE_ACCESSAccess mode limiting which operations may be called.
  • C64BRIDGE_HTTP_TOKENBearer token required by the optional HTTP transport.
  • C64BRIDGE_DIAGNOSTICS_KEEPNumber of diagnostics files kept at startup (files older than 30 days are always removed).
  • C64BRIDGE_VERBOSE_SCHEMASet to 1 to include full per-operation schemas in tools/list.
  • C64_MODEActive backend (c64u/U64 hardware, u2/U2-family cartridge, or vice emulator).
  • C64U_HOSTUltimate 64 host name or IP address.
  • C64U_PORTUltimate 64 REST port.
  • C64U_PASSWORDUltimate 64 network password sent as X-Password.
  • U2_HOSTU2/U2+/U2+L host name or IP address when C64_MODE=u2.
  • U2_PORTU2-family REST port when C64_MODE=u2.
  • U2_PASSWORDU2-family network password sent as X-Password.
  • VICE_BINARYVICE emulator binary to launch.
  • VICE_VISIBLELaunch VICE with a visible window when possible.
  • VICE_WARPEnable VICE warp mode.
  • GITHUB_TOKENGitHub token for optional RAG discovery against GitHub.

Tools this server provides (17)

Taken from the project documentation; the running server may differ.

c64_batch
Grouped C64 Bridge tool: batch.
c64_config
Grouped C64 Bridge tool: config.
c64_debug
Grouped C64 Bridge tool: debug.
c64_disk
Grouped C64 Bridge tool: disk.
c64_drive
Grouped C64 Bridge tool: drive.
c64_extract
Grouped C64 Bridge tool: extract.
c64_graphics
Grouped C64 Bridge tool: graphics.
c64_input
Grouped C64 Bridge tool: input.
c64_memory
Grouped C64 Bridge tool: memory.
c64_printer
Grouped C64 Bridge tool: printer.
c64_program
Grouped C64 Bridge tool: program.
c64_rag
Grouped C64 Bridge tool: rag.
c64_select_backend
Grouped C64 Bridge tool: select backend.
c64_sound
Grouped C64 Bridge tool: sound.
c64_stream
Grouped C64 Bridge tool: stream.
c64_system
Grouped C64 Bridge tool: system.
c64_vice
Grouped C64 Bridge tool: vice.

What it does

Hardware and emulator
Drives C64 Ultimate, Ultimate 64, U2-family devices and VICE, switchable at runtime.
Program runners
Runs BASIC, 6510 assembly, PRG and CRT files.
Memory access
Raw reads and writes plus screen polling.
SID music tools
Playback, composition, generation and verification.
Disk, drive and printer tools
Manages disks, files, drives and printer workflows.
Built-in C64 knowledge
Resources, prompts and retrieval for safer coding help.
HTTP bridge
Optional endpoint for inspecting tools by hand.

Good for

  • Have an assistant write and run a BASIC or assembly program on real hardware
  • Poke and inspect memory while debugging a demo
  • Render graphics or generate SID music and play it on a C64 Ultimate
  • Test the same program on hardware and in VICE in one session
  • Mount a disk image and list its contents

Pricing

Open source

Free and open source

C64 Bridge FAQ

Which machines does it support?

C64 Ultimate and Ultimate 64 (c64u), U2, U2+ and U2+L cartridges (u2), and the VICE emulator.

What do I need to run it?

Node.js 24 or newer; start it with npx -y c64bridge@latest and add a backend configuration.

Can I switch between hardware and VICE?

Yes, c64_select_backend switches at runtime when both are configured.

What licence is it under?

The README shows a GPL-2.0 badge.

Which transport does it use?

stdio, with an optional HTTP bridge for manual inspection.

Is C64 Bridge free?

Yes. C64 Bridge is open source, so you can use and self-host it for free.

How do I add C64 Bridge to Claude Code?

Run this command in your terminal: claude mcp add c64bridge --env C64BRIDGE_HTTP_TOKEN='<C64BRIDGE_HTTP_TOKEN>' --env C64U_PASSWORD='<C64U_PASSWORD>' --env U2_PASSWORD='<U2_PASSWORD>' --env GITHUB_TOKEN='<GITHUB_TOKEN>' -- npx -y c64bridge

What are the best alternatives to C64 Bridge?

The closest alternatives to C64 Bridge are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.

Where this comes from

  • Description: written from the project's README.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers