Minecraft MCP Server

Created By
DennisTrauba year ago
An early prototype of a Model Context Protocol (MCP) server implementation integrating the Mineflayer API to interact with Minecraft
Overview

what is Minecraft MCP Server?

Minecraft MCP Server is an early prototype of a Model Context Protocol (MCP) server that integrates the Mineflayer API to facilitate interaction with Minecraft.

how to use Minecraft MCP Server?

To use the Minecraft MCP Server, clone the repository from GitHub, set up the server environment, and utilize the Mineflayer API to create bots that can interact with the Minecraft world.

key features of Minecraft MCP Server?

  • Prototype implementation of Model Context Protocol (MCP)
  • Integration with Mineflayer API for bot creation
  • Ability to interact with Minecraft in real-time

use cases of Minecraft MCP Server?

  1. Creating AI-driven bots for Minecraft gameplay.
  2. Developing interactive experiences within the Minecraft environment.
  3. Experimenting with generative AI in a gaming context.

FAQ from Minecraft MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol designed to facilitate communication between AI models and applications.

  • Can I use this server for commercial purposes?

This is a prototype and may not be suitable for commercial use without further development.

  • Is there documentation available?

Yes, you can find documentation in the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
DennisTraub
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.

8 hours ago