Blockbench MCP

Community

Adds an MCP server to Blockbench so AI clients can reach a local modeling session

★ 438 Stars Category · Dev Tools Very popular

56FMRS · C

Blockbench MCP delivers a local MCP server to Blockbench as a plugin, with README config examples for VS Code, Claude Desktop, Claude Code, Cline, Ollama, OpenCode, and Antigravity, under GPL-3.0. It suits users who want AI clients connected to a local modeling environment, but the README does not enumerate specific tools and it is not an official product.

Reliability

9/20

Security and permissions

10/20

Maintenance

11/20

Documentation

12/20

Setup experience

14/20

Read the FMRS scoring method →

Blockbench MCP is a Blockbench plugin that runs an MCP server inside Blockbench, letting MCP-capable AI clients connect over HTTP to the local Blockbench instance. The plugin is installed by loading it from a URL, and the server port and endpoint are configured in Blockbench under Settings > General, with a default of :3000/bb-mcp. The README also mentions using Agent Skills to orchestrate tool usage and links to a sample project.

Setup

Open the desktop version of Blockbench, go to File > Plugins, click "Load Plugin from URL" and paste https://jasonjgardner.github.io/blockbench-mcp-plugin/mcp.js.
In Blockbench, open Settings > General and configure MCP Server Port and MCP Server Endpoint (default :3000/bb-mcp).
Configure the MCP server in your AI client, for example: npx mcp-add --type http --url "http://localhost:3000/bb-mcp" --scope project.
For Claude Desktop, bridge with mcp-remote: npx -y mcp-remote http://localhost:3000/bb-mcp (on Windows, invoke through cmd /c).
For VS Code use .vscode/mcp.json, and for Cline use cline_mcp_settings.json.

claude_desktop_config.json

{
  "mcpServers": {
    "blockbench": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "http://localhost:3000/bb-mcp"]
    }
  }
}

Generate and validate client config

Fit and risk

Best for

3D modelers using the desktop version of Blockbench
Developers who want MCP clients wired into their local modeling environment
Users adding AI assistance to a Blockbench workflow

Not for

Users who cannot run desktop Blockbench or load plugins
Clients without access to local HTTP endpoints
Users who need official support or a hosted service

Required permissions

Loading and running a third-party plugin inside Blockbench
Exposing a local MCP server port (default 3000)
AI client access to http://localhost:3000/bb-mcp

Risks and side effects

The plugin is third-party and not maintained by Blockbench itself
A local MCP endpoint without restrictions could be reached by other local programs
Incorrect port or endpoint configuration causes connection failures
Loading the plugin from a URL relies on remote script distribution

Troubleshooting

Confirm you are on desktop Blockbench and the plugin loaded successfully
Check that MCP Server Port/Endpoint under Settings > General match the default :3000/bb-mcp
Verify the client points at http://localhost:3000/bb-mcp
On Windows, wrap npx with cmd /c for Claude Desktop
Check that port 3000 is not in use by another program

Use cases

Connect an AI client to a local Blockbench session over MCP

Use an AI assistant while modeling in Blockbench

Orchestrate tool usage through Agent Skills

Supported clients

VS CodeFull support

Claude DesktopFull support

Claude CodeFull support

ClineFull support

OllamaPartial support

OpenCodePartial support

AntigravityFull support

Related MCP servers

Compare with other MCP servers