bedrock-map-builder-mcp
Related Servers
Alternatives to bedrock-map-builder-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables local authoring and testing of Minecraft Java adventure maps through validated MCP tools, including structure building, snapshot/restore, and automated QA.MIT
- FlicenseBqualityBmaintenanceThis server enables MCP clients to inspect and edit the currently open map in the Wulfram Forge desktop editor, including moving mirrored structures, shaping terrain, capturing views, validating placements, exporting copies, and undoing changes.10-
- AlicenseNot gradedqualityDmaintenanceMCP server for Minecraft Bedrock Edition providing 7 tools for zone management, building, scanning, and command execution via LLM.5 npm2MIT
- FlicenseNot gradedqualityCmaintenanceEnables Claude or Codex to build directly in a live Minecraft Java world via RCON, render textured previews so the AI can inspect its own work, place whole structures from ASCII layers, and hot-reload datapack minigames. It also moves worlds between the local server, bundled maps, and Realms-ready exports.1-
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to build, validate, test, and play Minecraft Bedrock add-ons, with versioned knowledge, pack validation, Bedrock Dedicated Server checks, live game bridging, and player control.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to set up and use a private local Minecraft test server, build and validate maps block by block, and export creations as schematics for any server.2465 npmMIT
TDQS
Scored across 51 tools
Despite 51 tools, most target distinct resource+action pairs (world_*, server_*, plan_*, project_*, region/block editing, analysis). A few pairs need the descriptions to separate: server_console vs run_commands, ws_listen/ws_status/use_connection vs server_status, and generate vs fill_region/place_blocks. The descriptions do explicitly disambiguate these (e.g. 'In-game commands are better sent with run_commands'), so overlap is manageable but present.
Everything is snake_case, which helps, but the verb/noun ordering is mixed: block_search, world_list, server_start (noun_verb) alongside find_blocks, list_entities, check_map, use_connection (verb_noun), plus bare names like generate, view, markers. Readable but not a predictable pattern.
51 tools is very heavy for a single server; even granting the breadth of Minecraft map building (server, world, project, plan, generation, editing, analysis, rendering), the surface is large enough that an agent must scan many names to find the right one. Some consolidation (e.g. merging plan_* or ws_* helpers) would be reasonable.
Coverage is unusually thorough: server lifecycle, world create/import/export/backup/restore, project memory, plans, generators, block edits, structures, palette, commands, entities, functions, and analysis/rendering. Minor gaps exist (no world_delete or project delete/close, region deletion only via region_mark with name), but nothing that blocks core workflows.