mcpmc

mcpmc provides a Model Context Protocol (MCP) server built on Mineflayer to enable AI agents to control and interact with Minecraft bots via a standardized JSON-RPC interface. The server communicates through stdin and stdout, allowing your agents or tooling to send requests (such as moving, mining, or inventory actions) and receive structured responses. This setup is ideal for experimenting with automated Minecraft play or integrating with AI systems that rely on MCP-style messaging. The project also includes an MCP inspector utility to browse and test the API surface, helping you discover available methods and data structures.

To use it, install the MCPMC package and run the server (via its CLI entry point). Once running, connect your client or agent to the process input/output streams to begin issuing RPC calls. The MCP inspector can be invoked to explore the API, test calls, and verify response formats before integrating into your own automations or experiments.

Prerequisites:

• Node.js v18 or newer (or compatible environment for your platform)
• npm (or yarn/bun if you prefer)

Installation steps:

1. Install the MCP server package from npm: npm install @gerred/mcpmc

2. Verify installation by listing binaries if provided, or rely on the CLI path exposed by npm (often npx or bin script named after the package): npx -y @gerred/mcpmc --help

3. Start the MCP server using the recommended command (as documented in the package README): mcpmc

4. Optional: Install a package manager wrapper (bun, pnpm) if you prefer those workflows and run the inspector to explore the API: bun run inspector

Notes and tips:

• The MCP server uses JSON-RPC over standard input/output; ensure your client is configured to send/receive JSON messages accordingly.
• The included MCP inspector is useful for discovering methods and data structures. Use it to validate calls before integrating into your agent.
• If you encounter network or runtime issues, verify Node.js compatibility and that the CLI entry point is accessible in your environment (some setups require invoking the package via npx or a local bin path).
• Environment variables aren’t required by default for mcpmc, but you can extend the mcp_config with additional environment variables if you need to configure Minecraft connection details, logging, or runtime behavior.
• If you’re using a CI environment, ensure the runner has network access to fetch the npm package when using npx.