Hex Agent + Model Context Protocol

AI that understands your print farm.

Print Hive MCP is the authorized connection between your farm data and Hex Agent, the Print Hive Smart Assistant. Hex can read live printer, queue, material, and operator context, then turn it into clear recommendations that stay under operator control.

Cursor, Claude, Codex, ChatGPT, and Grok connect to the same org-scoped MCP server as Hex — through OAuth or the official plugin — so you can drive your farm from any agent workflow.

Start free Read MCP docs

Org scopedApproval gated actionsWorks with MCP clients

Print Hive dashboard with live print farm status

Hex reads

live farm context

MCP scopes

org and tool access

Operators approve

production actions

Ask operational questions

Which jobs are at risk, what can run next, and where is material becoming a bottleneck?

Keep context current

Hex re-reads printers, jobs, queues, materials, and receipts instead of relying on stale chat memory.

Protect production work

Sensitive actions stay narrow, visible, and approval-gated before they affect a real machine.

How Hex uses MCP

MCP is the working memory behind the assistant.

Hex is not a generic chat window taped to your dashboard. It uses MCP to fetch scoped, current Print Hive context, cite the tools it used, and translate that context into operator work.

Print Hive supplies page context

When you open Hex inside the app, the product can hint at the printer, job, batch, queue, or action feed you are already viewing.

Hex refreshes through MCP

Page context is treated as a starting point. Hex re-reads the current records through org-scoped MCP tools before answering.

Recommendations become tracked work

Hex can produce recommendation receipts so suggested actions stay visible until an operator completes, dismisses, or revisits them.

Production changes require approval

Actions such as filament changes, ready-state updates, or duplicate-job operations pause for confirmation before execution.

Available tools

A practical tool surface for real farm work.

The MCP server exposes high-signal tools instead of raw tables. Hex and compatible clients can ask focused questions about utilization, queues, printer health, material runway, network state, sessions, and operator follow-through. Listed in the official MCP registry as com.printhiv3d/print-hive.

Fleet and printer state

Read printer inventory, live state, AMS/extruder state, local files, and temperature telemetry.

printers_listprinters_queryprinter_live_statusprinter_amsprinter_filament_statenarrated_filament_load_previewprinter_filesprinter_file_task_statustelemetry_temperatures

Jobs, queue, compatibility, and risk

Read print job records, history, schedulability, risk, and model-file printer compatibility.

jobs_listjobs_getjobs_historyqueue_healthjobs_at_riskmodel_file_compatible_printersproduction_promise_advisorsmart_queue_intervention_planfailure_patternsprint_job_resource_search

Farm intelligence

Higher-level operating summaries for utilization, downtime, throughput, maintenance, material runway, network health, and session review.

farm_utilizationfarm_playbookprinter_downtimematerial_runwaythroughput_reportsession_summarynetwork_healthmaintenance_debtmaintenance_service_plan

Assistant and operator context

Read Hex-related settings, recommendation follow-through, and human-authored shop-floor annotations.

assistant_settings_statusassistant_capabilities_statusassistant_recommendation_receiptsoperator_annotationsoperator_annotation_previewaction_items_listoperator_dispatch_queue

Hex approval-gated actions

Narrow production actions that Hex may request only behind explicit operator approval.

eve_operation_proposeoperator_annotation_applynarrated_filament_load_confirmfilament_loadfilament_unloadfilament_acknowledgefilament_assign_slotsjob_createjob_duplicate_last_on_printerprinters_set_ready

Security model

Scoped by user, organization, and tool intent.

MCP is not a shortcut around Print Hive authorization. The same API boundary validates credentials, binds organization access, and separates read privileges from production-affecting actions.

Authenticated access

The MCP server accepts user Bearer tokens and scoped API credentials. Models do not receive raw database credentials.

Organization scoping

Every request is bound to an active Print Hive organization, then revalidated by the API before a tool handler runs.

Curated tool exposure

Read tools are separated from write tools, and Hex receives an allow-list tuned for safe print farm assistance.

Architecture

How the pieces fit.

Print Hive API owns MCP

The MCP endpoint is mounted by the API at /v1/mcp. Tool handlers read through the same org-scoped backend services used by the product.

Pulse and HiveLink stay in the control path

Printer commands still flow through API, Pulse, HiveLink, and then the local printer. MCP does not move local-network trust into the assistant.

Hex gets a curated connection

The Hex Agent connection allow-lists read tools and a small set of approval-gated actions, keeping broad hardware controls invisible.

Connectors

Use MCP inside Print Hive or from your AI tools.

Hex is the native Print Hive experience, but the same protocol also gives technical teams a documented path into compatible assistants and automation workflows.

Hex Agent ready

Give your assistant current farm context.

Use MCP to connect AI workflows to Print Hive data, then let Hex turn that context into prioritized, reviewable operator work.

https://api.printhiv3d.com/v1/mcp

Start free Read docs