Vice MCP Server

Vice MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Vice MCP directly instead of describing what you should do. Every tool follows MCP conventions with full JSON Schema validation, meaningful errors, and consistent parameter naming.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once Vice MCP is connected, these are the calls the assistant has available:

• Category — Tools
• Execution — vice.execution.run vice.execution.pause vice.execution.step vice.run_until
• Registers — vice.registers.get vice.registers.set
• Memory — vice.memory.read vice.memory.write vice.memory.banks vice.memory.search vice.memory.fill vice.memory.compare
• Checkpoints — vice.checkpoint.add vice.checkpoint.delete vice.checkpoint.list vice.checkpoint.toggle vice.checkpoint.set_condition vice.checkpoint.set_ignore_count
• Sprites — vice.sprite.get vice.sprite.set vice.sprite.inspect
• VIC-II — vice.vicii.get_state vice.vicii.set_state
• SID — vice.sid.get_state vice.sid.set_state
• CIA — vice.cia.get_state vice.cia.set_state
• Disk — vice.disk.attach vice.disk.detach vice.disk.list vice.disk.read_sector
• Machine — vice.machine.reset vice.machine.config.get vice.machine.config.set vice.autostart
• Display — vice.display.screenshot vice.display.get_dimensions

Configuration and credentials

| Platform | Install | |---|---| | Debian/Ubuntu | apt install build-essential autoconf automake pkg-config libmicrohttpd-dev libgtk-3-dev xa65 flex byacc | | macOS | brew install autoconf automake pkg-config libmicrohttpd gtk+3 xa lame | | Windows (MSYS2) | pacman -S mingw-w64-x86_64-gcc mingw-w64-x86_64-libmicrohttpd mingw-w64-x86_64-gtk3 autoconf automake pkg-config |

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Vice MCP.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the vice mcp mcp server does with a few real requests.

Choosing this one

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Vice MCP's toolset — Category, Execution, Registers and 11 more — is a fair guide to whether it matches your workflow. It is maintained by barryw; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Vice MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.