blockbench -plugin

This MCP server powers the Blockbench MCP plugin, allowing Blockbench to send prompts and tool requests to a centralized Model Context Protocol (MCP) endpoint. The plugin loads from the URL provided in the installation steps and uses the configured MCP server to communicate with the server at http://localhost:3000/bb-mcp by default. Once connected, you can orchestrate prompts and tool usage via Agent Skills and the MCP protocol to perform tasks such as querying model data, running checks, and coordinating external tools. The workflow is designed to let Blockbench act as the client that issues commands to the MCP server, which in turn coordinates with various tools and services described in your MCP project.

To use it with Claude, Antigravity, Cline, Ollama, OpenCode, or other MCP clients, ensure the server URL matches your local setup (default: http://localhost:3000/bb-mcp) and choose the transport that your client supports (http, streamableHttp, etc.). The plugin can be loaded via the Load Plugin from URL option and will connect to the MCP server using the configured endpoint. Agent Skills can be used to orchestrate tool usage across the connected tools, providing a flexible bridge between Blockbench workflows and external reasoning or data-processing steps.

Prerequisites:

• Node.js and npm installed on your system
• Blockbench installed (desktop version) for plugin loading
• Internet access to fetch the MCP client package (mcp-remote) via npx

Step-by-step installation:

1. Verify prerequisites

   • node -v
   • npm -v
   • Ensure Blockbench is installed and accessible

2. Install and run the MCP client via NPX

   • The Blockbench MCP plugin expects an MCP server endpoint at http://localhost:3000/bb-mcp by default. You can connect using npx mcp-remote to generate a compatible request wrapper:

   npm i -g npx npx mcp-remote http://localhost:3000/bb-mcp

3. Load the Blockbench MCP plugin

   • In Blockbench, go to File > Plugins > Load Plugin from URL and enter: https://jasonjgardner.github.io/blockbench-mcp-plugin/mcp.js
   • This will enable the Blockbench plugin to communicate with the MCP server at the configured endpoint.

4. Configure the MCP server endpoint in Blockbench

   • Settings > General > MCP Server Port: 3000
   • Settings > General > MCP Server Endpoint: bb-mcp

5. Optional: for other environments (Claude, Antigravity, Cline, Ollama, OpenCode)

   • Use the corresponding configuration examples provided in the README to connect to the same endpoint, ensuring the serverUrl or transport matches your setup.

Notes and tips:

• The default MCP endpoint used in examples is http://localhost:3000/bb-mcp. Adjust as needed to fit your environment.
• When using npx, you don’t need a global installation of the MCP client; npx will fetch and run the mcp-remote package on demand.
• Supported transports across clients include http, streamableHttp, and others as demonstrated in the README (Claude, Cline, Ollama, OpenCode). Ensure your client configuration matches the transport type.
• If you run into connection issues, verify that the MCP server is running, reachable at the configured URL, and that any firewalls allow HTTP traffic on the required port.
• You can adapt the mcp.json files demonstrated in the README to point to other endpoints if you host the MCP server on a different port or path.
• For production, consider pinning a specific version of the mcp-remote client or using a package manager workflow to ensure consistent behavior across environments.