How nice2mu/muumc works
muu-mc is an MCP server that exposes Minecraft control and world-information tools to an AI host. The main workflow is a host task request through the MCP tool handler into cached skills or generated, sandboxed code, which acts on the game through a safety DSL and normalized bot driver. The README also documents autonomous planning, construction, persistent world memory, and voice-chat integration. Some subsystems are represented from documented capabilities and the file tree; their internal wiring is omitted where excerpts do not establish it.
Main entry points: tools.js Tool handler · client.js Bot client · index.js MCP server · autonomous_engine.js Autonomous engine
Components 24
MCP Interface
- MCP server
src/index.js - Tool handler
src/mcp/tools.js - Resource handler
src/mcp/resources.js
Gameplay Runtime
- Bot client
src/bot/client.js - Chat companion
src/bot/chat_companion.js - Safe game DSL
src/coder/dsl.js - Game watchdog
src/bot/watchdog.js - Driver adapter
src/driver/adapter.js
Planning and Skills
- Autonomous engine
src/bot/autonomous_engine.js - Goal planner
src/bot/planner/goal_plan.js - Situation evaluator
src/bot/planner/situation_evaluator.js - Skill cache
src/memory/skill_manager.js - Skill library
data/skills - AI coder
src/coder/agent.js - Code sandbox
src/coder/sandbox.js - Self-healing debugger
src/coder/debugger.js
World Services
- World memory
src/memory/world_memory.js - Construction subsystem
src/builder
External Integrations
- Voice bridge client
src/voice/voice_client.js - Voice event manager
src/voice/voice_manager.js
Other components
- AI host
- Minecraft server
- Voice bridge service
- Ollama model
Connections 31
- AI host → MCP server: MCP requests
- MCP server → Tool handler: dispatches tools
- MCP server → Resource handler: dispatches resources
- MCP server → Bot client: starts connection
- Tool handler → Skill cache: matches skills
- Skill cache → Skill library: loads skills
- Tool handler → AI coder: requests code
- AI coder → Ollama model: generates code
- Tool handler → Code sandbox: executes code
- Code sandbox → Safe game DSL: invokes helpers
- Tool handler → Self-healing debugger: repairs failures
- Self-healing debugger → Code sandbox: re-executes code
- Autonomous engine → Tool handler: dispatches tasks
- Autonomous engine → Goal planner: manages goals
- Autonomous engine → Situation evaluator: checks progress
- Bot client → Driver adapter: creates adapter
- Bot client → Game watchdog: wires watchdog
- Bot client → Safe game DSL: wires DSL
- Safe game DSL → Driver adapter: uses game API
- Game watchdog → Driver adapter: monitors actions
- Driver adapter → Minecraft server: controls bot
- Tool handler → Construction subsystem: dispatches builds
- Tool handler → World memory: manages memory
- Resource handler → World memory: reads world data
- Bot client → World memory: records landmarks
- MCP server → Voice bridge client: starts bridge
- Voice bridge client → Voice bridge service: connects outbound
- Voice bridge client → Voice event manager: forwards utterances
- Voice event manager → MCP server: sends notifications
- Voice event manager → Autonomous engine: pauses on command
- Bot client → Chat companion: processes chat