A
licenseNot graded
qualityB
maintenanceProvides external AI agents with reliable, observable tools to inspect, navigate, and act in a Minecraft world, enabling autonomous playthroughs such as beating the game.
11
MIT
OmniMod MCP
by Mcamento8
Related Servers
Alternatives to OmniMod MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn AI-native game engine MCP server that enables AI agents to create, modify, and run games using 53 tools for scene creation, physics, audio, 3D rendering, and AI-generated images and music.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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 gradedqualityFmaintenanceEnables AI-driven interactions with Minecraft through a WebSocket-based server and MCP protocol, allowing external MCP clients and in-game chat to trigger AI tools.4MIT
- AlicenseBqualityCmaintenanceEnables an AI agent to fully drive Blockbench through 69 tools covering 3D modeling, seeded procedural textures, UV mapping, animation, export codecs, files, and plugin management, plus arbitrary JavaScript inside the app when the built-in tools fall short. It bridges agent and editor over a token-gated localhost connection so models can be built, rendered, reviewed, and exported end to end with zero dependencies.72MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients such as AstrBot, Claude, Cursor, or custom scripts to control a Minecraft bot over SSE through 49 tools covering perception, movement, building, gathering, crafting, combat, farming, memory, social interaction, and autonomous skills. It supports multi-client body control, emotion and event context, and survival/companion behaviors.1MIT
TDQS
B3.2/5.0
Scored across 51 tools
Disambiguation4/5
Most tools have distinct resource/action pairs, and the high-level prefixes (world_, shape_, map_, mod_, batch_) make the primary purpose clear. However, a few clusters blur together—omni_errors/omni_logs/omni_notifications all address log inspection, and omni_map_guide/omni_map_onboard/omni_map_docs/omni_knowledge are all informational—so an agent may occasionally pick the wrong one. Detailed descriptions save it from a lower score.
Naming Consistency4/5
The set consistently uses the omni_ prefix and lowercase snake_case, and the omni_<domain>_<detail> pattern is recognizable across world_, map_, mapdev_, shape_, mod_, and batch_ tools. The pattern is not strictly verb_noun: one-word tools like omni_state, omni_inventory, and omni_chat mix with action-style names like omni_world_create and omni_recipe_validate. This is a minor inconsistency but not chaotic.
Tool Count1/5
51 tools is far beyond the 25+ threshold and lands in the 50+ extreme-mismatch range for this rubric. The server covers a broad Minecraft bridge surface, but the sheer number of entries will overwhelm tool-selection and make coherent orchestration harder. Clusters like logs/notifications/errors and the many map_* document tools could be consolidated.
Completeness4/5
The tool surface covers the full map-development workflow: world lifecycle, batch validate/apply, shape generation, dev/play mode, mod staging, recipe linting, verification reports, and the map agent context pack. Minor gaps exist—no world delete, no mod list/remove, and no explicit undo/rollback for batches—but those are workaroundable via omni_command or the existing ledger/report machinery. Overall, the core domain is well covered.
Maintenance
ActivitySlowing
ResponsivenessNo issues