For pharma, chemicals and food manufacturers running GUS-OS
A GUS-OS MCP server gives Claude, ChatGPT or Copilot read-first tools for batch status, genealogy, weighing records and supplier performance. GUS-OS exposes a Digital Hub REST interface and web services without a public reference. GUS ships no MCP server as of 21 September 2026, and in GMP plants the tool list is validated first.
Why GUS-OS is hard for agents
01 · GMP
Pharma customers run under EU-GMP Annex 11, so any interface that touches quality-relevant data needs validation and an audit trail. Adding an agent is a change to a computerised system. Your QA team signs off the tool list before it is built, not after.
02 · Docs
The Digital Hub REST interface exists mainly for GUS's own mobile UI and partner web apps. There is no public endpoint reference. Every backend is confirmed with GUS against your release in the blueprint.
03 · Batches
Batch and lot genealogy and the integrated LIMS data are the central objects. An agent that misreports a release status creates a compliance risk, so every tool that touches batches stays read-only or proposal-only.
04 · Hosting
The ERP usually runs on-premises while the Digital Hub is a cloud service. Where the MCP server runs, and which of the two it calls, is agreed with your IT and QA teams before the first tool.
Checked 21 September 2026
| What we found | |
|---|---|
| Interfaces | GUS-OS Digital Hub REST interface (REST/JSON, docs not published): carries every request of the GUS-OS mobile UI; the Digital Hub Service opens selected processes to partners and external staff through a web app · Open API architecture (REST and SOAP web services, docs not published): named by GUS for regulatory portals, serialisation platforms and partner portals, plus preconfigured MES and QMS interfaces · EDI and preconfigured connectors (file/EDI, docs not published): includes the GUS-OS scale connector for weighing input components in production |
| Authentication | Not documented publicly. How the Digital Hub and web services authenticate is confirmed with GUS in the blueprint. |
| Vendor MCP server | No vendor server. No GUS ERP MCP server and no MCP announcement; the GUS AI pages describe AI categories and research with Saarland University and DFKI, not a product. |
| Vendor AI assistant | No named AI assistant; GUS positions GUS-OS as the data foundation for AI and cites research with Saarland University and DFKI. |
| Other connectors | None found. |
GUS ERP GmbH (GUS Group) (DE). Mid-market process manufacturers in regulated sectors such as pharma, chemicals, food, cosmetics and dairy, plus logistics companies, mainly in Germany.
What we build
GUS ERP GmbH (GUS Group) does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.
# gus-os-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
get_batch_status: # batch or lot number -> status, release state, quality results
backend: confirmed in blueprint
mode: read
trace_batch: # batch number -> input lots and downstream deliveries
backend: confirmed in blueprint
mode: read
get_weighing_records: # production order -> weighed components and lots
backend: confirmed in blueprint
mode: read
get_supplier_performance: # supplier, period -> delivery performance
backend: confirmed in blueprint
mode: read
draft_workflow_task: # context -> proposed workflow task a person confirms
backend: confirmed in blueprint
mode: propose
audit: every call logged with user, tool, arguments and the GUS-OS responseThe manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.
GUS-OS holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.
When this is the wrong page
If the goal is batch release or quality decisions made by the system, this is the wrong page: the connector answers and proposes, and the validated GUS-OS workflow decides. Reporting across years of batch data belongs in a warehouse, not in per-question calls.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your GUS-OS owners and checks every backend against your release and licence. Week two tests whether a person's own GUS-OS permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.
What we need from you: a named GUS-OS administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.
Not as of 21 September 2026. GUS has published no MCP server and no announcement of one; its AI pages describe research with Saarland University and DFKI. An assistant outside GUS-OS has to be connected through the Digital Hub or the web services.
It needs access to the Digital Hub REST interface or the GUS-OS web services on your installation. Module and licence terms for that access are not public, so check with GUS; we confirm them in the blueprint together with your QA team.
No. The connector is designed so each call runs as the asking person and GUS-OS's own rights decide the answer. How the interface carries that identity is not documented publicly, so it is tested first, and every call is logged for the audit trail.
The two-week Readiness Blueprint is fixed at €4,900: agreed tool list, backends checked against your release, identity tested end to end, costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.
Next step
Thirty minutes with the engineer who would build the connector, with your GUS-OS administrator in the room if you like.