Repository navigation
Installation
Pavel Erokhin edited this page Oct 25, 2026
·
3 revisions
minecraft-mcp runs on your computer, next to your AI client. It needs a server to talk to and a way for the client to start it.
- WorldAPI 4.2.0 or newer on a Paper, Fabric, or NeoForge server, or as a mod in your game for Singleplayer. With an older WorldAPI, minecraft-mcp warns at start and some tools fail.
-
WorldAPI's address. It ends in
/api/v1:http://localhost:8110/api/v1on the same machine, or the public URL your proxy gives it. -
A WorldAPI token, optional. Run
/worldapi token create agentin game, click the groups you want, and copy the token from the chat. Without a token, the agent sees only what WorldAPI lets visitors read. Tokens and permissions says which group fits which job. -
Node.js 22 or newer, for clients that start the server with
npx. Claude Desktop runs the bundle with its own Node.js, so it doesn't need one.
- Claude Desktop: one-click bundle, no Node.js needed.
- Claude Code: one command.
- Cursor: a JSON file.
- Other clients: VS Code, any client that starts a server over stdio, and HTTP for remote agents.
Moonlands, my hard survival server with friends, runs WorldAPI and lets anyone read it. Point the agent at https://minecraft.mairwunnx.com/worldapi/api/v1 without a token to try it on a real world.
Next: Claude Desktop, Claude Code, Cursor, or Other clients.
Players and server owners
- Installation
- Claude Desktop
- Claude Code
- Cursor
- Other clients
- Singleplayer
- Configuration
- Tokens and permissions
- Tools
- Example prompts
- Security
- Troubleshooting
Developers