Minecraft MCP Server

Created By
yuniko-softwarea year ago
A Minecraft MCP Server powered by Mineflayer API. It allows to control a Minecraft character in real-time, allowing AI assistants to build structures, explore the world, and interact with the game environment through natural language instruction
Overview

what is Minecraft MCP Server?

Minecraft MCP Server is a bot that utilizes large language models and the Mineflayer API to control a Minecraft character in real-time, allowing users to interact with the game through natural language instructions.

how to use Minecraft MCP Server?

To use the Minecraft MCP Server, you need to have Node.js installed, a running Minecraft game, and Claude Desktop. After setting up the MCP configuration, you can start the bot and give it commands through the Claude Desktop chat.

key features of Minecraft MCP Server?

  • Real-time control of Minecraft characters using natural language.
  • Ability to build structures and explore the game world.
  • Commands for movement, inventory management, block interaction, and communication.

use cases of Minecraft MCP Server?

  1. Automating building tasks in Minecraft.
  2. Exploring Minecraft worlds using AI assistance.
  3. Interacting with game elements through voice or text commands.

FAQ from Minecraft MCP Server?

  • What do I need to run the Minecraft MCP Server?

You need Node.js, a running Minecraft game, and Claude Desktop.

  • Can I give the bot commands in any language?

Currently, the bot is optimized for English commands.

  • Is there a limit to what the bot can do in Minecraft?

The bot can perform a variety of tasks, but its capabilities depend on the commands you provide.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yuniko-software
Star
99
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago