For manufacturers running cronetwork MES

A read-only cronetwork MCP server for operations, disruptions and schedules from the cronetwork Gateway

A cronetwork MCP server gives Claude, ChatGPT or Copilot read tools for operations, disruptions, schedules and production feedback. cronetwork exposes REST services through its Gateway and PIDO, plus MQTT signals, without a public API reference. Industrie Informatik ships no MCP server as of 21 September 2026, so Pexon builds one against your installation.

Why cronetwork MES is hard for agents

Where a cronetwork MES connection needs engineering, not configuration

01 · PIDO

Endpoints exist only once you publish them

REST services are configured per installation through PIDO. Which endpoints exist depends on what your team has published, so the blueprint starts by listing yours and publishing the missing ones.

02 · Docs

No public API reference

Industrie Informatik does not publish an API reference. Access runs through its customer care or Solution Store, and every backend is confirmed against your installation before a tool is built.

03 · Events

Disruptions arrive as a stream

Disruptions and releases are pushed as MQTT signals, not stored for a later query. To answer what happened in the last shift, the connector needs a small buffer that keeps those events.

04 · Personal data

Attendance needs its own scope

Time and attendance data is personal data. It stays out of the tool list unless it gets a separate scope your works council has agreed to.

Checked 21 September 2026

cronetwork MES at a glance: interfaces, access and what exists for AI

	What we found
Interfaces	cronetwork Gateway REST web services (REST/JSON, docs behind customer or partner login): cronetwork data and MES logic are published as REST services per installation through cronetwork PIDO; no public API reference · cronetwork Gateway MQTT signals (MQTT, docs behind customer or partner login): push of business events such as disruptions, operation releases, workplace changes and feedback
Authentication	Not documented publicly. The login for published Gateway services is confirmed with Industrie Informatik in the blueprint.
Vendor MCP server	No vendor server. No Industrie Informatik MCP server or LLM assistant found; Hannover Messe 2026 showed the AI Optimizer and predictive analytics only.
Vendor AI assistant	Optimizer, a reinforcement-learning algorithm for detailed scheduling, plus MES-supported predictive analytics for downtime and quality risks; neither is a conversational assistant.
Other connectors	None found.

Industrie Informatik GmbH (AT). Discrete manufacturers in Central Europe, from machinery and automotive supply to metal processing, with references such as Liebherr, Stihl and voestalpine; Industrie Informatik states about 500 installations worldwide.

What we build

A first cronetwork MES tool list, written as the manifest your IT team signs

Built on what Industrie Informatik GmbH documents: operations and operation releases, workplaces, disruptions and downtimes, production feedback, detailed scheduling information, machine and process data, time and attendance, traceability data. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.

# cronetwork-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
  list_operations:    # workplace or order, status -> operations with planned dates
    backend: Gateway REST service published via PIDO, confirmed in blueprint
    mode: read
  list_disruptions:   # workplace, time range -> disruption events with reason
    backend: Gateway MQTT signals, buffered, confirmed in blueprint
    mode: read
  get_schedule:       # workplace, date -> planned operation sequence
    backend: confirmed in blueprint
    mode: read
  get_order_feedback: # order -> confirmed quantities and times
    backend: confirmed in blueprint
    mode: read
audit: every call logged with user, tool, arguments and the cronetwork MES response

The manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.

cronetwork MES 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.

What the connector answers, and what it will not do

Questions it answers

Which operations were released today on the milling workplace group, and which are delayed?
What disruptions occurred on machine 17 during the night shift?
What is the planned sequence for workplace 12 tomorrow?

What it will not do

Write to cronetwork: the connector is read-only and never books feedback or changes the schedule.
Read more than the asking user may read; each person is mapped to the scope their role allows, tested with two users before go-live.
Read time and attendance data without a separate scope your works council has agreed to.

When this is the wrong page

If the goal is a better detailed schedule, the vendor's Optimizer inside cronetwork is the right tool, not an agent. A connector is right when people ask from Claude, ChatGPT or Copilot, or need cronetwork data next to ERP data.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your cronetwork MES owners and checks every backend against your release and licence. Week two tests whether a person's own cronetwork MES 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 cronetwork MES 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.

Sources: cronetwork Gateway · cronetwork MES overview · 35 years Industrie Informatik · Hannover Messe 2026. Read 21 September 2026. Vendor documentation changes; verify against the current release.

Connectors for 100 source systems — the dated catalogue this page belongs to
Claude MCP server development — how we build an MCP server for any internal system

Questions cronetwork MES teams ask before the first tool call

Does cronetwork have its own MCP server?

Not as of 21 September 2026. Industrie Informatik showed its AI Optimizer and predictive analytics at Hannover Messe 2026, but no MCP server or LLM assistant. An MCP server for Claude, ChatGPT or Copilot has to be built against the cronetwork Gateway.

Do we need extra Industrie Informatik licences or access for an AI connector?

Industrie Informatik does not publish licence terms for the Gateway or PIDO. Check with the vendor whether your licence includes the Gateway REST services and MQTT signals. The blueprint settles it before any tool is built.

Can the assistant see data a user is not allowed to see in cronetwork?

No. Each person is mapped to the scope their role allows, and time and attendance data stays out unless separately agreed. Two users asking the same question can get two different answers, and that is tested before go-live.

What does a cronetwork connector cost?

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

Not a sales call. An architecture call.

Thirty minutes with the engineer who would build the connector, with your cronetwork MES administrator in the room if you like.