C64 Bridge

Name: C64 Bridge
Author: chrisgleissner

by chrisgleissnerversion 1.0.7i★ –iRuns on your computer

Registry nameio.github.chrisgleissner/c64bridge

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: C64U_PASSWORD, U2_PASSWORD, GITHUB_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: LOG_LEVEL, C64BRIDGE_CONFIG, C64_MODE, C64U_HOST, C64U_PORT, C64U_PASSWORD, U2_HOST, U2_PORT, U2_PASSWORD, VICE_BINARY, VICE_VISIBLE, VICE_WARP, GITHUB_TOKEN

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "c64bridge": {
      "command": "npx",
      "args": [
        "-y",
        "c64bridge"
      ],
      "env": {
        "LOG_LEVEL": "your-value",
        "C64BRIDGE_CONFIG": "your-value",
        "C64_MODE": "your-value",
        "C64U_HOST": "your-value",
        "C64U_PORT": "your-value",
        "C64U_PASSWORD": "your-value",
        "U2_HOST": "your-value",
        "U2_PORT": "your-value",
        "U2_PASSWORD": "your-value",
        "VICE_BINARY": "your-value",
        "VICE_VISIBLE": "your-value",
        "VICE_WARP": "your-value",
        "GITHUB_TOKEN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add c64bridge --env LOG_LEVEL=your-value --env C64BRIDGE_CONFIG=your-value --env C64_MODE=your-value --env C64U_HOST=your-value --env C64U_PORT=your-value --env C64U_PASSWORD=your-value --env U2_HOST=your-value --env U2_PORT=your-value --env U2_PASSWORD=your-value --env VICE_BINARY=your-value --env VICE_VISIBLE=your-value --env VICE_WARP=your-value --env GITHUB_TOKEN=your-value -- npx -y c64bridge

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "c64bridge": {
      "command": "npx",
      "args": [
        "-y",
        "c64bridge"
      ],
      "env": {
        "LOG_LEVEL": "your-value",
        "C64BRIDGE_CONFIG": "your-value",
        "C64_MODE": "your-value",
        "C64U_HOST": "your-value",
        "C64U_PORT": "your-value",
        "C64U_PASSWORD": "your-value",
        "U2_HOST": "your-value",
        "U2_PORT": "your-value",
        "U2_PASSWORD": "your-value",
        "VICE_BINARY": "your-value",
        "VICE_VISIBLE": "your-value",
        "VICE_WARP": "your-value",
        "GITHUB_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "c64bridge": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "c64bridge"
      ],
      "env": {
        "LOG_LEVEL": "your-value",
        "C64BRIDGE_CONFIG": "your-value",
        "C64_MODE": "your-value",
        "C64U_HOST": "your-value",
        "C64U_PORT": "your-value",
        "C64U_PASSWORD": "your-value",
        "U2_HOST": "your-value",
        "U2_PORT": "your-value",
        "U2_PASSWORD": "your-value",
        "VICE_BINARY": "your-value",
        "VICE_VISIBLE": "your-value",
        "VICE_WARP": "your-value",
        "GITHUB_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

LOG_LEVEL env
Logger verbosity.
C64BRIDGE_CONFIG env
Path to the C64 Bridge configuration file.
C64_MODE env
Active backend (c64u/U64 hardware, u2/U2-family cartridge, or vice emulator).
C64U_HOST env
Ultimate 64 host name or IP address.
C64U_PORT env
Ultimate 64 REST port.
C64U_PASSWORD secret env
Ultimate 64 network password sent as X-Password.
U2_HOST env
U2/U2+/U2+L host name or IP address when C64_MODE=u2.
U2_PORT env
U2-family REST port when C64_MODE=u2.
U2_PASSWORD secret env
U2-family network password sent as X-Password.
VICE_BINARY env
VICE emulator binary to launch.
VICE_VISIBLE env
Launch VICE with a visible window when possible.
VICE_WARP env
Enable VICE warp mode.
GITHUB_TOKEN secret env
GitHub token for optional RAG discovery against GitHub.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account chrisgleissner, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32708 servers in this category
Published to the registry more recently than 95% of the other 32708 servers in this category
Basic checks equal to or better than 100% of the other 32708 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is C64 Bridge safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: C64U_PASSWORD, U2_PASSWORD, GITHUB_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.7) reached the registry 2 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, OpenTakeoff

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

OpenTakeoff

by Kentucky-ai

Construction takeoff for AI agents: load plans, set scale, measure, count, export with provenance.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

C64 Bridge

Your AI Command Bridge for the Commodore 64.

C64 Bridge is an MCP server for controlling and working with a Commodore 64 from an AI client.

It lets you run programs, read and write memory, render graphics, and play sound on a C64 Ultimate, Ultimate 64, or U2-family cartridge. You can also switch to a VICE emulator session, so one MCP conversation can span hardware and emulation.

It is built on the official TypeScript @modelcontextprotocol/sdk and supports both stdio for local AI integration and an optional HTTP bridge for manual inspection.

C64 Bridge is listed in the Official MCP Registry.

C64 Bridge
Contents
Overview
Features
Quick Start
1. Install Node.js 24+ and npm
2. Start the Server
3. Add Backend Configuration
4. Connect from an MCP Client
Configuration
Configuration File Order
Configuration Merge Rules
Backend Configuration: C64 Ultimate
Backend Configuration: U2-family
Backend Configuration: VICE
VICE Window Modes
Recommended VICE Configurations
Runtime Backend Switching
VS Code MCP Setup
Enable the C64 Agent
Optional Overrides
Environment Variables in MCP Client Configs
Runtime Environment Variable Reference
Server Runtime
C64 Ultimate
VICE Runtime
VICE Audio Capture
SID Playback
RAG
Testing
Claude Code
Example Workflow
HTTP Invocation
Build and Test
Documentation
Static MCP Interface
MCP API Reference
Tools
c64\_batch
c64\_config
c64\_debug
c64\_disk
c64\_drive
c64\_extract
c64\_graphics
c64\_input
c64\_memory
c64\_printer
c64\_program
c64\_rag
c64\_select\_backend
c64\_sound
c64\_stream
c64\_system
c64\_vice
Resources
Prompts

Overview

C64 Bridge gives an AI agent one place to drive program execution, memory access, graphics, sound, storage, printer workflows, and knowledge retrieval for a Commodore 64 environment.

The core workflow is simple:

Start the MCP server.
Point it at C64U/U64 hardware, a U2-family cartridge, VICE, or any configured combination.
Let the client call grouped MCP tools such as c64_program, c64_memory, c64_graphics, and c64_sound.
Switch backends at runtime with c64_select_backend when both are configured.

Features

Program runners for BASIC, 6510 assembly, and PRG or CRT execution
Full memory access, including raw reads and writes plus screen polling
System integration for drives, files, printers, and task orchestration
SID music tools for playback, composition, generation, and verification
Built-in knowledge resources and prompts for safer LLM workflows
Mixed runtime support for c64u (C64U/U64), u2 (U2/U2+/U2+L), and vice

Quick Start

If you want the shortest path, do these four things:

Install Node.js 24+ and npm.
Start the server.
Add backend configuration for C64U/U64, U2-family, VICE, or any combination.
Connect from VS Code or another MCP client.

1. Install Node.js 24+ and npm

Linux (Ubuntu or Debian):

Recommended:

sudo apt update

sudo apt install -y curl ca-certificates curl -fsSL https://deb.nodesource.com/setup_24.x | sudo -E bash - sudo apt install -y nodejs

Fallback:

sudo apt install -y nodejs npm

macOS:

brew install node@24

brew link --overwrite node@24

Windows:

# winget

winget install OpenJS.NodeJS.LTS

or Chocolatey

choco install nodejs-lts -y

Verify the installation:

node --version

Expected result: v24.x

2. Start the Server

Use one of the following entry points.

Run from npx with zero setup:

npx -y c64bridge@latest

Run from a local npm install:

mkdir -p ~/c64bridge && cd ~/c64bridge

npm init -y npm install c64bridge node ./node_modules/c64bridge/dist/index.js

Run from source for development or testing:

git clone https://github.com/chrisgleissner/c64bridge.git

cd c64bridge ./build install npm start

On startup, the server probes the selected target, performs connectivity checks, and then announces that it is running on stdio.

3. Add Backend Configuration

The server can run against one or more of:

C64U/U64 hardware (c64u)
U2, U2+, or U2+L (u2)
VICE (vice)

The detailed lookup order, merge rules, backend examples, and override model are in the Configuration section below.

4. Connect from an MCP Client

C64 Bridge ships a single canonical stdio entry point that every MCP client uses:

VS Code (GitHub Copilot) — see VS Code MCP Setup.
Claude Code (CLI and VS Code plugin) — see Claude Code.
Cursor, Visual Studio, VS Code Insiders — use the install badges at the top of this README.
Any other MCP client — point it at the same stdio server, with the environment variables documented in Runtime Environment Variable Reference and the registry manifest in mcp.json.

The startup command is the same across clients: npx -y c64bridge@latest for the published package, or node scripts/start.mjs from a local checkout. Select c64u, u2, or vice in the shared Configuration; clients only need the command.

Configuration

Configuration File Order

The server reads configuration in this order:

C64BRIDGE_CONFIG, if it points to a config file
.c64bridge.json in the project root
~/.c64bridge.json in the home directory

Configuration Merge Rules

Configuration is merged per backend section while scanning those files in order.

The first file that contains each backend section (c64u, u2, or vice) supplies that backend's configuration.
This allows a project-local .c64bridge.json to define c64u while ~/.c64bridge.json defines u2 or vice.

Backend Configuration: C64 Ultimate

Use this for a C64 Ultimate or Ultimate 64:

"c64u": { "host": "c64u", "port": 80, "networkPassword": "secret" } }

If no file is found, the default target is c64u:80 with no network password.
networkPassword is only needed when you enabled a password in the C64 Ultimate network settings.
C64U_HOST, C64U_PORT, and C64U_PASSWORD override the configured host, port, and network password.

Firmware Requirements for Native Input and Menu Screens

The following operations require recently added Ultimate REST endpoints. C64 Bridge detects or explains unavailable endpoints without exposing a raw firmware error.

Before choosing an endpoint-dependent operation, read c64://platform/status. It probes machine:input safely and reports whether it is available. When native input is unavailable, use key or write_text for ordinary C64 input instead of physical matrix events. machine:menu_screen can only be confirmed after an Ultimate menu is visible; its tool returns fallback guidance rather than a transport error when no matrix can be read.

c64_input keyboard, release_all, and state, plus hardware joystick, use machine:input. They require a C64U firmware version that provides this endpoint, or U64 firmware 3.15 or later. machine:input is not available on U2-family cartridges.
c64_system read_menu_screen uses machine:menu_screen; it requires a C64U firm

Only the beginning is shown; read the rest in the repo

C64 Bridge

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

OpenTakeoff

README from the maker

C64 Bridge

Contents

Overview

Features

Quick Start

1. Install Node.js 24+ and npm

or Chocolatey

2. Start the Server

3. Add Backend Configuration

4. Connect from an MCP Client

Configuration

Configuration File Order

Configuration Merge Rules

Backend Configuration: C64 Ultimate

Firmware Requirements for Native Input and Menu Screens