Minecraft MCP
Related Servers
Alternatives to Minecraft MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to inspect and control a real Minecraft Java client through the Model Context Protocol, exposing world data, screenshots, inventories, chat, and normal player actions under the player's permissions.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to control and observe a Minecraft client through tools for state, entities, commands, chat, recording, waiting, and event replay, bridging any agent runtime to the game.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to remotely control a Minecraft player, including navigation, mining, building, and interaction with the world and other players.MIT
- AlicenseNot gradedqualityBmaintenanceGives AI agents eyes and hands inside Minecraft, letting them capture screenshots from any camera angle, read and click GUIs and menus, chat, press keys and read the HUD on a Fabric client. On a Paper server it also runs console commands and JavaScript against the Bukkit API, reads and edits the world, spawns player-like bots, profiles lag, and builds, deploys and tests plugins.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to control Minecraft via MCP with configurable versions, creative building commands, survival helpers, and an autonomous agent loop.Apache 2.0
- AlicenseBqualityCmaintenanceEnables AI agents to operate a Minecraft Java Edition player through MCP, supporting movement, mining, crafting, combat, inventory, and chat with structured observations and action results.18MIT
TDQS
Scored across 5 tools
Each tool has a largely distinct purpose: execute runs code, stop halts tasks, read_output retrieves buffered output, chat posts a local message, and screenshot captures the framebuffer. The only mild overlap is that chat could be achieved through execute, but the dedicated tool is clearly scoped to player-visible notifications.
All names are lowercase and snake_case where needed, but the verb convention is mixed: execute and stop are bare verbs, read_output follows verb_noun, while chat and screenshot are noun-like labels. Readable, but not a predictable pattern.
Five tools is well-scoped for a JS execution/control server. Each tool covers a distinct part of the execution lifecycle or a useful side operation, and none feels redundant.
The core lifecycle is covered: execute with wait/keep_alive, read_output for output and state, stop for cleanup. Minor gaps include no explicit task listing or status-enumeration tool, but read_output and stop mitigate this enough for agent use.