This MCP server provides a lightweight wrapper around the MCP 2.0 tooling to help you manage, inspect, and apply mappings for Minecraft development and modding workflows. The server exposes endpoints and a local CLI that can fetch MCP mappings, reveal deobfuscated names, and apply patch sets to provided artifacts. Use it to quickly spin up a local MCP 2.0 environment, view mapping data in a readable format, and generate patches for deobfuscated code. The included tooling supports viewing mappings, diffing mappings, and exporting mapping sets for downstream tooling.

To interact with the server, start it with the configured command, then access its API or CLI to list available mappings, fetch a specific version, and apply patches. Typical use cases include preparing mapping data for a Minecraft mod development project or for educational exploration of MCP 2.0 mappings. If your setup includes a frontend, point it at the server host/port to present a user-friendly UI for mapping operations.

Prerequisites:

• Node.js (LTS version) installed on your system
• npm (comes with Node.js) or pnpm
• Basic knowledge of the command line

1. Clone this repository:

   git clone https://github.com/your-org/frankraitv-mcp2.0-server.git cd frankraitv-mcp2.0-server

2. Install dependencies:

   npm install

   or using yarn

   yarn install

3. Configure environment (optional):

• Create a .env file or export variables as needed:

  MCP_PORT=8080 MCP_HOST=localhost MCP_LOG_LEVEL=info

4. Run the server:

   npm start

   or if a start script is not defined, run the server directly

   node server.js

5. Verify the server is running by visiting:

   http://localhost:8080/api/status

6. (Optional) Build or package for deployment according to your environment following the repository's build scripts.

Note: If the project provides alternative run scripts (e.g., npm run dev), prefer those per the package.json.

Tips:

• Ensure Node.js version compatibility with MCP 2.0 tooling you intend to use.
• If you encounter port conflicts, change MCP_PORT or bind to a different MCP_HOST.
• For production deployments, consider running behind a reverse proxy and enabling authentication for API access.
• Review environment variables in .env or the server startup logs to ensure mappings are loaded correctly.
• If you use the CLI, consult the available commands (e.g., list, fetch, diff, export) for mapping data and patch generation.

Common issues:

• Module not found errors: run npm install to pull dependencies.
• Connection refused: ensure the server is started and the port is not blocked by a firewall.
• Permission denied on port <80/443> when running as a non-root user: use a higher port and a proxy for external access.