Minecraft Agent

A LAN-capable Minecraft MCP server built with Dedalus MCP and a Mineflayer bridge.

What it is

Minecraft Agent connects agent tooling to a Minecraft environment through MCP and a Mineflayer bridge. The repo topics identify the operating domain: ai-agent, automation, game-ai, mcp, minecraft, mineflayer, and python. Source: raw/github/kevin-repos-2026-06-25.json

Why it matters

This is a compact demonstration of Kevin's recurring agent pattern: take an interactive environment with state and tools, expose it through MCP, and let an agent operate in it. In portfolio routing, it belongs with Agent Machines, Agent-Ping, and X-Agent as practical agent infrastructure rather than with the campus games. Source: raw/github/kevin-repos-2026-06-25.json

Demo Role

The March 2026 X demo frames the project as an Imagination Chasm bridge for agents: take a legacy game environment people already understand, replace a passive NPC assumption with an agent that can mine, craft, and fight, and make the workflow visible in a demo rather than a definition. The reviewed local thumbnail shows a stage demo with a Minecraft player view and code visible; it is evidence for the demo framing, not a full source for the command surface. Source: X/@kevskgs and local video thumbnail review, 2026-07-03

The GDC artifact adds event proof: Kevin described Dedalus as the only non-game company presenting at GDC and showed the agent live on stage. The reviewed images show Kevin/Advika on a Dedalus Labs stage and a Minecraft screen where chat commands include destroy this pig, DedalusBot Stopped: follow me around, and DedalusBot Working on: destroy this pig. This turns the project from a repo/demo into an event-tested agent-in-world showcase. Source: X/@kevskgs and local image review, 2026-07-04

Open facts to enrich later

The GitHub metadata establishes the project and pinned status, but the wiki still lacks a deeper README or transcript source for the exact command surface, Minecraft actions, and Dedalus MCP integration details. A future project sync should read the repo source and add the MCP tool list. Source: raw/github/kevin-repos-2026-06-25.json


Timeline