Commodore 64 Ultimate Computer MCP Server
Related Servers
Alternatives to Commodore 64 Ultimate Computer MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to control Commodore 64 Ultimate hardware via REST API, supporting program execution, memory operations, disk management, audio playback, and device configuration through natural language commands.22MIT
- AlicenseNot gradedqualityAmaintenanceLets 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.518 npm37GPL 2.0
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseAqualityDmaintenanceEnables AI-powered control and debugging of Commodore 64 programs via the VICE emulator, supporting memory operations, breakpoints, register access, and program loading.186 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables controlling and interacting with a Commodore 64 emulator running in the browser via MCP.-
- FlicenseAqualityDmaintenanceEnables autonomous debugging of Commodore 64 programs through the VICE emulator with semantic interpretation of C64-specific data structures, memory layouts, VIC-II states, and PETSCII encoding for AI-assisted 6502 assembly debugging.261-
TDQS
Scored across 49 tools
Most tools have distinct purposes, but there is notable overlap in file handling (e.g., load_prg_file vs. run_prg_file) and disk image creation (create_d64, create_d71, etc.), which could cause confusion. The descriptions help clarify, but the high tool count increases ambiguity.
Tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., capture_screen, list_drives). Minor deviations exist, such as modplay_file vs. sidplay_file (inconsistent prefix usage), but overall naming is predictable and readable.
With 49 tools, the count is excessive for a single server, making it feel heavy and overwhelming. While the domain (Commodore 64 emulation/control) is broad, many tools could be consolidated (e.g., multiple create_d* for disk images) to improve usability.
The tool set provides comprehensive coverage for the domain, including configuration management, disk operations, file loading/execution, machine control, and debugging. There are no obvious gaps; it supports full CRUD/lifecycle operations for emulating and controlling a Commodore 64 system.