BlockBenchMCP

Minecraft-oriented Model Context Protocol as a pure Blockbench desktop plugin (≥ 5.1.0).

Install the plugin → it hosts loopback HTTP MCP → point Cursor at the URL. No separate Node adapter. Closing Blockbench stops MCP.

Intent-level tools (scaffold_biped, check_model, …) — not a thin UI mirror.

Install

Artifact (recommended): download blockbench_mcp.js from GitHub Releases.

From source:

git clone https://github.com/SwagRee/BlockBenchMCP.git
cd BlockBenchMCP
npm install && npm run build

Output: packages/plugin/dist/blockbench_mcp.js.

1. Blockbench: File → Plugins → Load Plugin from File

2. Allow network / net when prompted

3. Listens on http://127.0.0.1:39741/mcp (or Tools → Start / Stop MCP Server)

4. Settings: port + Bearer (default dev-local-secret)

Related MCP server: Blockbench MCP

Cursor

{
  "url": "http://127.0.0.1:39741/mcp",
  "headers": { "Authorization": "Bearer dev-local-secret" }
}

Open Blockbench first, enable MCP, call health.

Architecture

AI client  --HTTP MCP-->  packages/plugin (inside Blockbench)

Security: loopback only; Bearer required; file export needs propose_scoped_directory confirmation.

Scope (v1)

Non-goals: trigger_action / emulate_clicks / risky_eval, full paint UI, Hytale, etc.

Main tools

Mutations return explicit success/failure; unknown params hard-error. Prefer check_model over vision spam.

Workflow

1. get_guide(modeling)

2. create_project

3. Entities: scaffold_biped / blocks: apply_geometry_batch

4. Fix errors, then texture

5. pack_box_uv → shade_model_base → paint_face_features (pack_box_uv / geometry follow project uv_mode: box vs per-face)

6. capture_views only if needed

Check uv_mode on health / get_project_summary: java_block → face; Bedrock-style → box.

Agent skill

Pixel-art modeling playbook: skills/blockbench-pixel-art/openai.

License

MIT