mcbaratone
Related Servers
Alternatives to mcbaratone
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control Minecraft via MCP with configurable versions, creative building commands, survival helpers, and an autonomous agent loop.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to control Minecraft bots through a standardized JSON-RPC interface.7 npm40MIT
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to control a Minecraft bot and interact with the game through MCP tools, including observing state, moving, mining, crafting, building, farming, managing inventory, enchanting, and chatting in-game.1-
- AlicenseNot gradedqualityCmaintenanceGoverns and audits AI coding agents via command gating, cryptographic logging, and multi-agent orchestration, exposed as an MCP server.22 npm4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to control Minecraft bots via natural language commands by bridging a Python MCP server with a Node.js Mineflayer bridge. It supports a wide range of in-game actions including complex pathfinding, resource gathering, crafting, and combat.10MIT
- AlicenseBqualityCmaintenanceA local MCP server that gives AI agents structured task planning, execution tracking, and guided research workflows.166 npmMIT
TDQS
Scored across 69 tools
Many tools overlap in purpose: run_command/batch_command/mission_macro/mission_queue for execution, and numerous pathing/exploration variants (path, goal_coordinates, goto_block_type, come, thisway, axis, surface, explore). Several legacy commands (proc, eta, find, gc, damn) have vague descriptions, making it hard for an agent to choose reliably.
Names mix single-word Baritone commands (find, path, explore, invert, damn) with snake_case verb_noun tools (set_goal_block, subscribe_events, wp_save). No consistent pattern is applied across the set; prefixes like wp_, mission_, and get_ are not used systematically.
69 tools is extreme for this surface; many are niche legacy commands or redundant wrappers, far exceeding a well-scoped 3-15 tool set. The count creates a high cognitive load and increases misselection risk.
The set broadly covers pathing, mining, building schematics, waypoints, settings, cache, events, uploads, and command execution, suggesting fairly complete coverage for Baritone automation. Minor gaps and oddities remain, such as the non-functional 'damn' tool and some lifecycle operations being implicit via run_command.