01
Print Hive supplies page context
When you open Eve inside the app, the product can hint at the printer, job, batch, queue, or action feed you are already viewing.
Eve Agent + Model Context Protocol
AI that understands your print farm.
Print Hive MCP is the authorized connection between your farm data and Eve Agent, the Print Hive Smart Assistant. Eve can read live printer, queue, material, and operator context, then turn it into clear recommendations that stay under operator control.
Org scopedApproval gated actionsWorks with MCP clients
Eve 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
Eve 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 Eve uses MCP
MCP is the working memory behind the assistant.
Eve 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.
02
Eve refreshes through MCP
Page context is treated as a starting point. Eve re-reads the current records through org-scoped MCP tools before answering.
03
Recommendations become tracked work
Eve can produce recommendation receipts so suggested actions stay visible until an operator completes, dismisses, or revisits them.
04
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. Eve and compatible clients can ask focused questions about utilization, queues, printer health, material runway, network state, sessions, and operator follow-through.
Fleet and printer state
Read printer inventory, live state, AMS/extruder state, local files, and temperature telemetry.
printers_listprinters_queryprinter_live_statusprinter_amsprinter_filament_stateprinter_filesprinter_file_task_statustelemetry_temperaturesJobs, 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_advisorFarm intelligence
Higher-level operating summaries for utilization, downtime, throughput, material runway, network health, and session review.
farm_utilizationfarm_playbookprinter_downtimematerial_runwaythroughput_reportsession_summarynetwork_healthAssistant and operator context
Read Eve-related settings, recommendation follow-through, and human-authored shop-floor annotations.
assistant_settings_statusassistant_recommendation_receiptsoperator_annotationsEve approval-gated actions
Narrow production actions that Eve may request only behind explicit operator approval.
filament_loadfilament_unloadfilament_acknowledgejob_duplicate_last_on_printerprinters_set_readySecurity 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 Eve 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.
Eve gets a curated connection
The Eve 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.
Eve is the native Print Hive experience, but the same protocol also gives technical teams a documented path into compatible assistants and automation workflows.
Eve Agent
The Print Hive Smart Assistant uses MCP as its live data and action layer inside the app.
Open Print HiveClaude Code
Connect a developer workflow to printer, queue, material, and job context from the command line.
Setup guideCursor
Use Print Hive MCP in your editor when building automations or diagnosing farm operations.
Setup guideChatGPT
Connect ChatGPT to the same authorized MCP surface for structured print farm questions.
Setup guideEve Agent ready
Give your assistant current farm context.
Use MCP to connect AI workflows to Print Hive data, then let Eve turn that context into prioritized, reviewable operator work.
https://api.printhiv3d.com/v1/mcp