A Critical Manufacturing MCP server for live lots, resources and history, not just the documentation

Checked 21 September 2026

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

Critical Manufacturing, part of ASMPT (PT). High-tech discrete manufacturers in semiconductor, electronics, medical devices and industrial equipment, typically running several sites.

Why Critical Manufacturing MES is hard for agents

Where a Critical Manufacturing MES connection needs engineering, not configuration

What we build

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

Built on what Critical Manufacturing, part of ASMPT documents: materials (lots, wafers, units) with track-in and track-out, sub-materials, resources and areas, setup and line clearance, certifications, material substrate maps, system events from the Data Platform. 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.

# critical-manufacturing-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_material:         # material name -> current step, flow, resource, state, hold reasons
    backend: REST /api/<service> material query, exact service confirmed in blueprint
    mode: read
  list_resource_states: # area -> resources with state and state duration
    backend: confirmed in blueprint
    mode: read
  get_material_history: # material name -> track-in and track-out history
    backend: confirmed in blueprint
    mode: read
  draft_material_hold:  # material, reason -> hold proposal for an engineer to confirm
    backend: confirmed in blueprint
    mode: propose
audit: every call logged with user, tool, arguments and the Critical Manufacturing 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.

Critical Manufacturing 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.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your Critical Manufacturing MES owners and checks every backend against your release and licence. Week two tests whether a person's own Critical Manufacturing 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 Critical Manufacturing 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: CM API reference 11.2 · CM REST API reference · CM Documentation Portal · CM agent-plugins (CM GPT) · CM blog: MCP and AI agents · Critical Manufacturing (Wikipedia). Read 21 September 2026. Vendor documentation changes; verify against the current release.

Related

• 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