Craftwire

io.github.UXPLIMAv0.7.2Updated Oct 7, 2026

See and drive Minecraft: Fabric client, Paper server, bots, plugin tests, profiling.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Lets an AI assistant see and drive Minecraft: control a Fabric client, run commands on a Paper server, and profile lag.

What it does
Craftwire is the MCP hub for a Minecraft toolchain. On a Fabric client it exposes screenshots, a free camera, GUI reading and clicking, chat, input and HUD state. On a Paper server it offers console commands, JavaScript against the Bukkit API, world reads, edits and images, event capture, exception grouping, logs and plugin control. It also covers a plugin dev loop, pathfinding server-side bots, JSON-scenario plugin tests, and profiling of which plugin, mod, listener or method causes lag. Plugins and mods can add their own tools.
When to use it
Use it when an assistant should inspect or operate a live Minecraft game or server rather than only read code: reproducing and debugging plugin or mod behavior, driving a client through GUIs and chat, running scripted plugin tests, or finding what makes a server or game lag.
Requirements
A local Node.js runtime to run the npm package via npx, plus the matching game-side jars: the Fabric agent mod (with Fabric API) in a client mods folder or the Paper plugin in a server plugins folder. The hub listens on 127.0.0.1 and writes a token to ~/.craftwire/hub.json. The client_process tool downloads Minecraft and Fabric from official servers and needs online-mode=false on the dev server. No accounts or API keys are declared.
Before you install
The server can act inside a running game and server: console commands, Bukkit API JavaScript, world edits, GUI clicks, chat and input, and plugin control, so changes are real and may be destructive. The hub token in ~/.craftwire/hub.json is a credential; the hub is local-only unless shared over HTTP with npx craftwire serve. The setup command edits MCP client config files, though it backs them up as .bak and supports --dry-run. The client_process tool downloads game files from third-party…

Installation

In SourceWeft

  1. Open Craftwire in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Craftwire: let AI agents see and drive Minecraft]

craftwire

This package is the MCP server (hub) of Craftwire. It lets AI agents see and drive Minecraft:

  • On a Fabric client: screenshots, a free camera, reading and clicking GUIs, chat, input and the HUD.
  • On a Paper server: console commands, JavaScript against the Bukkit API, world reads, edits and images, every event that fires, exceptions grouped into bugs, logs and plugin control.
  • A plugin dev loop, server-side bots that find their own path, and plugin tests written as JSON scenarios (npx craftwire test).
  • Profiling: which plugin or mod, listener and method makes the server or the game lag, and exact call times for one method.
  • Plugins and mods can add their own tools.

Minecraft 26.2 & 26.3 · Fabric client · Paper server · MIT · by UXPLIMA

Set up your AI client

npx craftwire setup            # lists the clients found on this computernpx craftwire setup codex      # or: gemini, antigravity, cursor, windsurf, vscode, claude-desktop

setup adds the craftwire entry to the client's MCP config. It leaves the other entries alone and backs the file up as .bak first. For Codex and Gemini CLI it also installs Craftwire's skills. --dry-run shows the change without writing it.

Claude Code uses the plugin instead:

/plugin marketplace add uxplima/craftwire/plugin install craftwire@uxplima

Any other MCP client runs it over stdio:

json
{ "mcpServers": { "craftwire": { "command": "npx", "args": ["-y", "craftwire"] } } }

On Windows, use "command": "cmd", "args": ["/c", "npx", "-y", "craftwire"].

Add the game side

Get both jars from Releases:

  • craftwire-agent-fabric-<version>.jar: put it in your Fabric profile's mods/ folder, with Fabric API.
  • craftwire-paper-<version>.jar: put it in a Paper server's plugins/ folder.

Both connect to the hub on their own. The hub listens on 127.0.0.1 only and writes a token to ~/.craftwire/hub.json. Use one AI client with Craftwire at a time, or run npx craftwire serve (MCP over HTTP with a token) to share one hub between several clients.

No game open? The client_process tool starts a hidden client the hub runs itself. It downloads Minecraft and Fabric from their official servers on first use, then joins your dev server, which needs online-mode=false, or opens a singleplayer world.

Troubleshooting: npx craftwire doctor. Add --server <folder> to check a server folder too.

Docs, tools and the protocol: https://github.com/uxplima/craftwire

Source: hub/README.md at commit d28dd73

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.7.2LatestOct 7, 2026