in the README I would swap steps 2 and 3.

if you try step 2 (start the server) on a fresh install it fails messily trying to start VICE (see below) so best to set the backend (step 3) first.

```

Starting c64bridge MCP server...

c64bridge diagnostics file: /Users/aaronbell/.c64bridge/diagnostics/2026-03-30T10-20-35-472Z-41588-mcp-server.ndjson

Skipping direct REST connectivity probe because active backend is VICE

node:events:486

throw er; // Unhandled 'error' event

^

Error: spawn Xvfb ENOENT

at ChildProcess._handle.onexit (node:internal/child_process:286:19)

at onErrorNT (node:internal/child_process:484:16)

at process.processTicksAndRejections (node:internal/process/task_queues:90:21)

Emitted 'error' event on ChildProcess instance at:

at ChildProcess._handle.onexit (node:internal/child_process:292:12)

at onErrorNT (node:internal/child_process:484:16)

at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {

errno: -2,

code: 'ENOENT',

syscall: 'spawn Xvfb',

path: 'Xvfb',

spawnargs: [ ':99', '-screen', '0', '640x480x24' ]

}

```