Minecraft

Created By
yuniko-softwarea year ago
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 through the Model Context Protocol (MCP).

how to use Minecraft MCP Server?

To use the Minecraft MCP Server, you need to have Node.js and a running Minecraft game. Set up the bot with Claude Desktop, configure the MCP settings, and start the Minecraft game with a singleplayer world opened to LAN.

key features of Minecraft MCP Server?

  • Control a Minecraft character using AI through Claude Desktop.
  • Execute various commands for movement, inventory management, and block interaction.
  • Ability to upload images of buildings for the bot to recreate.

use cases of Minecraft MCP Server?

  1. Automating tasks in Minecraft such as building structures.
  2. Interacting with the game environment using AI commands.
  3. Enhancing gameplay experience with AI assistance.

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 installed.

  • Can I use this bot for multiplayer games?

The bot is designed for singleplayer worlds opened to LAN.

  • What commands can the bot execute?

The bot can execute commands for movement, inventory management, block interaction, and communication.

Server Config

{
  "mcpServers": {
    "minecraft": {
      "command": "npx",
      "args": [
        "-y",
        "github:yuniko-software/minecraft-mcp-server",
        "--host",
        "localhost",
        "--port",
        "25565",
        "--username",
        "ClaudeBot"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yuniko-software
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago