Print Hive

What Print Hive MCP server does

Print Hive MCP server gives an AI agent access to an authenticated Print Hive organization and its connected print-farm data. The available areas include printers and fleet information, models, files, materials, inventory, Makes, print jobs, and telemetry. The service is intended for organization-scoped operations, including Bambu print farms, AMS, and queue workflows.

Access is divided by domain. OAuth grants can be separated across printers, models, jobs, inventory, Makes, fleet, and telemetry. This lets an organization control which parts of its Print Hive data and operations an agent may use. Printer credentials are not entered into the client; they are entered in the Print Hive web application.

How it works

The Print Hive MCP server uses the remote endpoint https://api.printhiv3d.com/v1/mcp. The documented plugin configuration is URL-only HTTP, with no API key or secret environment variables. When a client starts the connection, the user completes Print Hive OAuth authorization. Requests are then bound to the authenticated Print Hive organization.

Read and operational workflows are available through the MCP connection. Production-changing actions require exact targets and may ask for explicit confirmation. The documented safety model also prevents dangerous printer operations from being implicitly granted to public OAuth clients.

A separate print-hive-farm-crew marketplace plugin adds role-based agents named Foreman, Trendy, Spool, Nest, Wrench, and Counter. It can be installed alongside the main plugin for MCP and role-agent workflows. The farm-safe behavior is to queue or slice when asked, while confirming buys, parts, start or stop actions, and g-code operations.

Setup and configuration

For Cursor, the plugin is intended to be installed from the Cursor Marketplace after publication. Until then, the repository can be cloned and the plugins/print-hive directory copied into ~/.cursor/plugins/local/print-hive; Grok Bot cannot load that local Cursor path. The repository marketplace can also be imported through team settings.

Claude Code users can add the PrintHive/print-hive-plugins marketplace and install print-hive@print-hive with user scope. Codex users can add the same marketplace and install print-hive@print-hive. After installation, start the client and complete Print Hive authorization when prompted; Claude Code exposes its MCP controls through /mcp.

The reviewed public ChatGPT/Codex listing uses the same endpoint. ChatGPT can be configured with a custom MCP connector using OAuth discovery while the directory listing is pending.

Tools and capabilities

Print Hive MCP server supports workflows covering:

• Fleet status and operations
• Library, models, files, and inventory
• Materials and filament operations
• Print jobs, queueing, slicing, and dispatch
• Smart assignment and production commitments
• Risk readiness and reliability diagnostics
• Performance reporting and operator context
• Makes and telemetry access
• Guarded printer controls

The plugin also includes skills for setup, fleet operations, library and inventory work, Grok claims, shift and dispatch, material runway, briefing settings, and related operator workflows. The README does not provide a complete list of individual MCP tool names, so capabilities are described by their documented workflow areas rather than by assumed tool identifiers.