Skip to main content
Glama
Sign In
VICE C64 Emulator MCP Server

VICE C64 Emulator MCP Server

by simen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to VICE C64 Emulator MCP Server

No user-submitted related servers found.

    Related Servers

    • C64 Debug MCP

      henols
      A
      license
      A
      quality
      D
      maintenance
      Enables AI-powered control and debugging of Commodore 64 programs via the VICE emulator, supporting memory operations, breakpoints, register access, and program loading.
      18
      8 npm
      MIT

    • vice64-mcp

      nutshot2000
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to fully control the VICE Commodore 64 emulator, including running programs, viewing the screen, sending input, reading/writing memory, setting breakpoints, and assembling 6502 code.
      MIT

    • cbm-mcp

      thred
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to debug Commodore software in a locally running VICE emulator through its text remote monitor, inspecting registers, memory and screens, disassembling code, setting breakpoints and watchpoints, controlling execution, and working with disk images, snapshots and exported graphics. Runs locally over stdio and includes safety guidance for state-changing operations.
      259 npm
      MIT

    • pet-tools-mcp

      nschneir
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to code and debug Commodore PET software using the VICE emulator, with CLI and MCP tools for session control, screen reading, memory manipulation, and testing.
      44
      1
      MIT

    • C64 Bridge

      chrisgleissner
      A
      license
      Not graded
      quality
      A
      maintenance
      Lets AI clients control and program a Commodore 64, including running programs, reading/writing memory, rendering graphics, playing sound, and switching between C64 Ultimate hardware and VICE emulation.
      154 npm
      41
      GPL 2.0

    • 80mcp

      avwohl
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to run CP/M, MP/M, and DOS packages on Z80/x86 emulators, inspect byte-exact results and files, and debug the emulators themselves over the Model Context Protocol.
      7
      GPL 3.0
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.9/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools have distinct purposes with clear boundaries, such as connect/disconnect for connection management, readMemory/readScreen for different memory views, and setBreakpoint/setWatchpoint for different debugging triggers. However, some tools like readScreen and renderScreen both provide screen representations, which could cause minor confusion about when to use each, though their descriptions clarify the differences.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, such as connect, disconnect, getRegisters, listBreakpoints, readMemory, and writeMemory. All names use lowercase with clear, descriptive verbs and nouns, making the set predictable and easy to understand.

    Tool Count3/5

    With 26 tools, the count is on the higher side for an emulator debugging server, which may feel heavy but is reasonable given the comprehensive coverage of debugging operations. It includes connection, execution control, memory access, breakpoints, screen rendering, and state management, though some tools could potentially be consolidated (e.g., readScreen and renderScreen).

    Completeness5/5

    The tool set provides complete coverage for C64 emulator debugging, including connection management, execution control (continue, step, runTo), breakpoint and watchpoint handling, memory and register access, screen and sprite inspection, state saving/loading, and reset functionality. There are no obvious gaps; all core debugging workflows are supported with logical tool relationships.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources