minecraft-mcp-server and minestom-mcp
These are ecosystem siblings serving different Minecraft server architectures: one controls a Mineflayer-based client to interact with existing servers, while the other provides an MCP interface for the Minestom server framework itself, allowing complementary but distinct integration points.
About minecraft-mcp-server
yuniko-software/minecraft-mcp-server
A Minecraft MCP Server powered by Mineflayer API. It allows to control a Minecraft character in real-time, allowing AI assistants to build structures, explore the world, and interact with the game environment through natural language instruction
Implements the Model Context Protocol (MCP) standard to integrate with Claude Desktop and other MCP-compatible clients via stdio transport. Exposes a comprehensive command set covering movement, block interaction, inventory management, and entity detection, enabling LLMs to perform complex multi-step tasks like structure building from image references. Targets Minecraft Java Edition 1.21.x and abstracts the Mineflayer bot API into discrete, composable MCP tools that Claude can invoke and chain together.
About minestom-mcp
Azoraqua/minestom-mcp
A stdio MCP server for Minestom, implemented with the Model Context Protocol SDK and TanStack AI tool definitions.
Exposes curated Minestom API lookups, environment inspection, and build-aware tools that understand Gradle/Maven modules, JVM source layouts, and workspace patterns—enabling AI agents to navigate Java server projects intelligently. Grounded in official Minestom documentation and the ecosystem library directory, it provides context-aware suggestions for libraries, design reviews against threading/event patterns, and feature planning scaffolds. Distributed as an npm package with stdio transport, designed for seamless integration into `.mcp.json` agent configurations.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work