This plugin integrates the Blockbench 3D modeling application with the Model Context Protocol (MCP) server ecosystem. It enables users to connect Blockbench to various AI development tools and agents that leverage MCP, streamlining 3D asset creation within AI-assisted workflows.

How It Works

The plugin allows Blockbench to be configured to communicate with an MCP server. Users specify the MCP server's endpoint and port within Blockbench's general settings. This enables Blockbench to send and receive data or commands related to 3D models, facilitating integration with external AI agents or development environments that support the MCP protocol.

Quick Start & Requirements

• Primary install: Open Blockbench desktop, navigate to File > Plugins, and select "Load Plugin from URL", pasting https://jasonjgardner.github.io/blockbench-mcp-plugin/mcp.js.
• Prerequisites: Blockbench desktop application. An MCP server must be running and configured in Blockbench settings (Settings > General > MCP Server Port and MCP Server Endpoint), defaulting to http://localhost:3000/bb-mcp.
• Integration Examples: Configuration examples are provided for clients like VS Code, Claude Desktop/Code, Antigravity, Cline, Ollama, and OpenCode to connect to the MCP endpoint.
• Documentation: Development setup and plugin extension details are available in CONTRIBUTING.md.

Highlighted Details

• Broad client integration supports configuration for multiple AI development tools and environments.
• Enables seamless communication between Blockbench and MCP-compliant AI agents or services.
• Provides clear examples for integrating the MCP endpoint into various development workflows.

Maintenance & Community

• CONTRIBUTING.md is available, indicating a pathway for community contributions and development setup. No specific community channels or contributor details are provided in the README.

Licensing & Compatibility

• No license information is specified in the provided README content. Compatibility for commercial use or closed-source linking is undetermined.

Limitations & Caveats

• The plugin requires a separate, running MCP server to function. Setup complexity may vary depending on the specific client integration and MCP server configuration. Crucially, the absence of explicit licensing information presents a significant adoption blocker.