regenerator2000

Regenerator 2000 exposes an MCP server that lets you programmatically interact with the 6502 disassembly environment over HTTP or via stdio. Start the server to access features like disassembly manipulation, memory search, block operations, and data/view resources through the MCP protocol. When running in MCP mode, clients can request views of memory, perform edits to labels or comments, import/export data, and control navigation or analysis tasks within the disassembly project. The server is designed to work with the Regenerator 2000 UI as well as external tooling that speaks MCP, enabling automation and integration into larger tooling pipelines.

Prerequisites:

• Rust toolchain (stable) to compile or install the binary from crates.io

Install and run the MCP-enabled server:

1. Install the crate (pre-built binary will be installed to your Cargo bin directory):

cargo install regenerator2000

2. Run the MCP server (HTTP on port 3000 by default):

regenerator2000 --mcp-server

3. Optional: run via stdio instead of HTTP:

regenerator2000 --mcp-server-stdio

Validation:

• Visit http://localhost:3000 to confirm the MCP server is serving HTTP requests (if using the default HTTP mode).
• Use MCP clients or curl to exercise endpoints defined by the MCP protocol.

Notes:

• You can also build from source if you prefer:

git clone https://github.com/ricardoquesada/regenerator2000.git
cd regenerator2000
cargo install --path .

• Ensure your environment allows network access on port 3000 if using HTTP mode.

Tips and considerations:

• Default MCP HTTP port is 3000 unless overridden by flags or config; ensure no firewall rules block this port if you plan to connect from another machine.
• If you need batch processing, explore the --headless option for non-TUI operation when performing exports or analyses via MCP commands.
• For integration, MCP endpoints provide access to disassembly views, memory operations, and data views; refer to the MCP protocol documentation and the server’s available resources in the implementation for exact endpoints and payload formats.
• If you encounter issues starting the server, verify Rust toolchain installation and that the binary is in your PATH; also check for port conflicts on 3000.
• The README mentions support for loading various file formats (.prg, .crt, .d64, etc.) and exporting to multiple assemblers; MCP operations will operate on the loaded project context.