Short answer
You connect Claude to a print farm through MCP, an open standard for connecting AI apps to outside systems. Add AMENT Hive's MCP server to Claude as a custom connector (https://hive.ament.ai/mcp), review the permissions on Hive's consent screen and allow access. Claude can then read printers, orders, the plan, filament and quality, and draft plate layouts and print proposals. Uploading to a printer, starting a print or commanding a printer always takes a person's approval in the Hive app.
Key takeaways
- MCP is an open standard for connecting AI apps to outside systems; Claude is an MCP client and Hive is an MCP server.
- The connection uses OAuth: Hive's consent screen shows which permissions you grant, and you can disconnect at any time.
- Claude reads and drafts; uploads, starts and printer commands happen only in the Hive app, with a person's approval.
- Customer names are never sent to external AI apps; orders appear by reference.
- Claude's menu names can change; check Anthropic's current help page before you set it up.
What is MCP (Model Context Protocol)?
MCP is an open-source standard for connecting AI applications to external systems. Anthropic announced it in November 2024, and today it is supported by Claude, ChatGPT and many developer tools. The protocol's own site explains it with an analogy: MCP is like a USB-C port for AI applications; just as USB-C connects devices in a standard way, MCP connects AI applications to external systems in a standard way.
The architecture has three roles. The host is the AI app you use, such as Claude. The client is the part inside the host that is opened for each connection and talks to one server. The server is the program that provides data and tools; in our case, Hive. A server can offer tools the AI can call, resources it can read and ready-made prompts.
Servers can be local or remote. A local server runs on your own computer; a remote server runs on the internet and talks over HTTP. For remote servers, MCP recommends OAuth to obtain access tokens. Hive's MCP server is a remote server and uses OAuth.
Why connect your print farm to an external AI app?
Hive has its own AI assistant; you can ask the farm questions in the app, in Telegram and in WhatsApp. So why Claude? Because many farm owners already spend much of the day in an AI app: drafting replies to customers, comparing supplier quotes, writing a weekly report. Once production data is there too, you can bring both worlds together in one conversation.
- Reports: ask "Summarise this week's quality and compare it with last week", and Claude writes it from data it reads in Hive.
- Planning questions: before giving a customer a date, ask "Will this order make it by Friday?"
- Purchasing: have it read the filament forecast and draft the order to your supplier.
- Analysis: work through failure reasons and printer and product breakdowns in a longer conversation, alongside your own notes.
In short, the assistant inside Hive is for daily operations, and the Claude connection brings production data into a wider workspace. The connection is entirely optional; you can use every Hive feature without connecting any external AI app. We discuss where AI genuinely helps in a print farm in AI for 3D print farms.
How AMENT Hive's MCP server works
AMENT Hive runs its MCP server at one address: https://hive.ament.ai/mcp. When Claude connects to it, Hive sends you to its own sign-in and consent screen. The heading reads something like "Claude wants to access your farm", followed by what the app will be able to do, item by item.
| Permission | What it means |
|---|---|
| Farm status | See printers, their live state and the connector status. |
| Diagnostics | Read printer events and error codes. |
| Orders | See orders and their production status; customer names hidden. |
| Plan | See the production plan and print-file coverage. |
| Plan simulation | Try out plans without changing anything. |
| Plate layout drafts | Propose draft layouts; nothing changes until someone saves them. |
| Print proposals | Prepare print proposals; may slice the file, but nothing is uploaded or started until someone confirms it in Hive. |
Quality and maintenance status, the filament forecast and filament use are read with the farm status permission. Hive offers an external AI app the same tool catalogue as its in-app assistant, but some tools are never exposed outside: drafting a change to a printer's filament colour or maintenance mode, for example, exists only in Hive's own assistant.
The connection works with the farm role of the person who approved it, and that role is checked again on every request. Permissions granted by someone who is removed from the team stop working. Access tokens are short-lived and each refresh invalidates the previous one; if a token is ever reused, access is cut off completely.
Steps to connect Claude to Hive
The steps below follow Anthropic's help page for custom connectors (as of October 2026). Claude's menu names can change over time; if a step looks different, check Anthropic's current page.
- 1
Open the connectors page
In Claude, go to Customize → Connectors. On Free, Pro and Max plans you add a custom connector to your own account; the Free plan allows one custom connector.
- 2
Add a custom connector
Click Add custom connector and enter https://hive.ament.ai/mcp as the server URL. Hive's OAuth server supports the ways Claude identifies itself, so you normally do not need to enter a client ID. Save with Add.
- 3
Sign in to Hive and read the permissions
When you connect, Hive's page opens. Sign in to your farm, read the listed permissions and make sure you are in the right farm.
- 4
Allow access
Choose Allow access and you are sent back to Claude. The connection now appears in Hive under Integrations → Connected AI apps.
- 5
Turn it on in a chat
In a conversation, open the + button, then Connectors, and switch the Hive connector on or off for that conversation.
On Team and Enterprise plans, an organisation Owner adds the custom connector (Organization settings → Connectors); members see it in their list with a Custom label and connect with their own account via Connect. Each member goes through Hive's consent screen themselves, so everyone works with their own role.
Claude Code and other MCP clients
For tools such as Claude Code or MCP Inspector, the farm owner can create a personal access token on Hive's Integrations page. That token works with viewer rights: it reads printers, orders and plans, can at most propose a draft plate layout, does not see customer names, cannot prepare print proposals and cannot change anything. It is shown only once and can be revoked at any time.
What can Claude read, what can it draft, and what can it never do?
Hive's AI rule fits in one sentence: the AI prepares, a person approves. It applies to Hive's own assistant and to Claude connected over MCP alike, and it is enforced on the server; no prompt or conversation can stretch it.
| Reads | Drafts | Can never |
|---|---|---|
| Printer state, errors and what they mean | Plate layout proposals | Upload a file to a printer |
| Orders (customer names hidden) | Print proposals (slicing if needed) | Start a print |
| Plan, delivery estimates, plan simulation | Pause, resume or stop | |
| Filament forecast, quality and maintenance | Calibrate or clear an error | |
| Print files and catalogue coverage | Change stock, settings or plan approval |
A draft waits in Hive, where you open and review it. Uploading a print proposal to a printer is a person's request in Hive; starting the print is a separate approval by an owner or production manager, and at that moment the server checks again that the plate is clear, the printer idle, the filament right and the file sliced for that printer. We explain how remote commands are protected in remote printer control.
Security: what to know before you connect
Connecting an AI app to production data means handing it a key. Hive keeps that key narrow, but there are a few things you should know too. Anthropic recommends similar precautions for custom connectors: connect only to servers from organisations you trust, review the permissions requested during authentication carefully, and watch for unexpected changes in tool behaviour.
- Read the permissions: do not click Allow access without reading the list on the consent screen. Check you are signed in to the right farm.
- Customer names stay in Hive: they are never sent to external AI apps; orders appear by reference. Order references, product names and production data do reach Claude, so weigh that against your company's policy.
- Your role applies: Claude cannot go beyond the permissions of the person who approved it. Connect with a viewer account and Claude can only read.
- Prompt injection: text the AI reads, such as a file note, may try to steer it. In Hive the risk is limited because none of the physical steps are in the AI's hands, but always check what Claude tells you against the data in Hive.
- Logging: connecting and disconnecting are written to the audit log, and AI tool calls are recorded too.
- Disconnect: choose Disconnect under Integrations → Connected AI apps and access ends at once. The owner sees, and can cut off, connections made by anyone in the team.
Example questions to ask Claude
Once connected, you ask in plain language and Claude decides which Hive tool to call. Some examples that work well:
- "Is any printer in error or waiting for me? What do the error codes mean?"
- "Which open orders might miss their shipping deadline this week?"
- "Can we have this order ready by 2 pm on Friday? When would it finish in the worst case?"
- "If I add 50 more units to the plan, which orders slip?"
- "When does black PLA run out, and how much should I order given the lead time?"
- "Which product and which printer failed most in the last 30 days, and what was the most common reason?"
- "List printers with overdue maintenance."
- "Which products have no print file?"
- "Draft a plate layout for 8 units of Kapak sol."
Claude writes its answer from the data Hive returns and usually shows which tool it used, which makes the source easy to check. Interpreting the numbers is Claude's part: Hive's forecast gives a most-likely range, so if Claude boils it down to a single figure, ask for the range too. Before important decisions, especially purchasing and delivery dates promised to customers, it is a good habit to see the same figure once on Hive's own screen.
For the last example, Claude prepares a draft that you open in Hive's plate editor; the draft changes nothing until someone saves it. You can ask similar questions from inside Hive or from Telegram; we cover the channels in notifications and floor displays.
You can try Hive free for 14 days. If you want to connect your farm to Claude, see the plans and start a trial, and we can do the first setup with you.
Frequently asked questions
What is MCP?
MCP (Model Context Protocol) is an open-source standard for connecting AI apps such as Claude and ChatGPT to data sources, tools and workflows. Anthropic announced it in November 2024. The AI app acts as the client, and the system it connects to acts as the server.
Can Claude start a print for me?
No. Claude connected to Hive over MCP can read and draft plate layouts or print proposals, but it cannot upload a file, start a print or command a printer. Uploading is a person's request in Hive, and starting is a separate approval by an owner or production manager.
Will Claude see my customers' details?
Customer names are never sent to external AI apps; orders appear by reference. Order references, products, printer state and production data do reach Claude, so weigh the connection against your company's policy.
How do I remove the Claude connection?
In Hive, find the connection under Integrations → Connected AI apps and choose Disconnect; access ends immediately. You can also remove the connector on Claude's side under Customize → Connectors.
Does it work with ChatGPT too?
Hive's MCP server is a standard remote server that connects with OAuth, and Hive's consent screen mentions ChatGPT connectors too. We have verified the steps in this guide for Claude only; for other apps, follow their own custom connector steps.