Print Hive MCP server
{
"mcpServers": {
"printhiv3d-print-hive": {
"type": "http",
"url": "https://api.printhiv3d.com/v1/mcp"
}
}
}{
"mcpServers": {
"printhiv3d-print-hive": {
"type": "http",
"url": "https://api.printhiv3d.com/v1/mcp"
}
}
}{
"mcpServers": {
"printhiv3d-print-hive": {
"type": "http",
"url": "https://api.printhiv3d.com/v1/mcp"
}
}
}{
"servers": {
"printhiv3d-print-hive": {
"type": "http",
"url": "https://api.printhiv3d.com/v1/mcp"
}
}
}{
"mcpServers": {
"printhiv3d-print-hive": {
"type": "http",
"url": "https://api.printhiv3d.com/v1/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.1.4
What it does
This server connects AI agents to Print Hive, a management platform for Bambu Lab print farms. It provides access to fleet status, print jobs, materials, inventory, and printer controls through OAuth-secured organization-scoped permissions.
- Monitor fleet status and retrieve current print job information across multiple printers.
- Manage materials inventory and check filament availability for production scheduling.
- Dispatch print jobs to appropriate printers based on fleet capacity and material availability.
Tools this server exposes
| Tool | Does |
|---|---|
| fleet-status | Retrieve current status of all printers in the fleet. |
| shift-and-dispatch | Assign and dispatch print jobs to printers. |
| material-runway | Check material inventory and availability across the fleet. |
| production-commitments | Track and manage production commitments and deadlines. |
| smart-assign | Intelligently assign print jobs based on printer capabilities and availability. |
| risk-readiness | Assess fleet readiness and identify potential production risks. |
| performance-reporting | Generate reports on printer and fleet performance metrics. |
| reliability-diagnostics | Run diagnostics on printer reliability and identify issues. |
| filament-operations | Manage filament inventory, loading, and AMS operations. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.