For steel and aluminium producers running PSImetals

A read-only PSImetals MCP server for coil genealogy, orders and yard, until PSI's own interface ships

A PSImetals MCP server gives Claude, ChatGPT or Copilot read tools for material genealogy, order status, yard location and quality holds. PSI publishes no API reference. As of 21 September 2026 PSI has announced an MCP interface to its Factory Model, without documentation or a release date; Pexon builds a read-only connector meanwhile.

Checked 21 September 2026

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

	What we found
Interfaces	MCP interface to the PSI Factory Model (MCP, docs not published): presented at Hannover Messe 2026; availability and licensing not published · PSImetals Service Platform (Java platform services, docs not published): release 5.30 adds Kubernetes deployment and Keycloak-based authentication; no public API reference · L2 Standard Interface and ERP interfaces (not published, docs not published): standardised link to Level 2 process control and certified SAP integration; technical formats not public
Authentication	No public API authentication documentation. Release 5.30 introduces Keycloak-based authentication for the platform, which is the natural anchor for per-user identity; confirmed in the blueprint.
Vendor MCP server	Announced only. PSI presented a Model Context Protocol interface to the PSI Factory Model for PSImetals at Hannover Messe 2026 (press release of 25 February 2026); no public documentation or general availability date found.
Vendor AI assistant	Chatbot Factory Model & Documentation, which combines database access to production data with system documentation; PSI also names AI and machine learning in the Line Scheduler.
Other connectors	None found.

PSI Metals, part of PSI Software SE (DE). Steel, aluminium and copper producers running integrated plants and rolling mills; named customers include ArcelorMittal, AMAG Austria Metall, SSAB and Tata Steel.

Why PSImetals is hard for agents

Where a PSImetals connection needs engineering, not configuration

01 · Docs

Everything runs through PSI projects

PSI publishes no API reference for PSImetals. Every backend is agreed with PSI and your PSImetals team, and confirmed against your release in the blueprint.

02 · Vendor MCP

PSI's MCP interface is a showcase so far

PSI has shown an MCP interface to its Factory Model, but scope, licensing and which releases get it are not published. A connector has to be aligned with PSI's roadmap so you do not build what PSI is about to ship.

03 · Material model

Genealogy breaks naive queries

Coils split, merge and change identity across hot and cold rolling. A query that ignores the genealogy gives answers that look right and are wrong, so tools follow parent and child material explicitly.

04 · 24/7

Mills never stop for a test

Mills run around the clock with Level 2 automation behind PSImetals. The connector is read-only towards production and scheduling, and it is tested without touching the running plant.

What we build

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

Built on what PSI Metals, part of PSI Software SE documents: material and material genealogy (coils, slabs and other types), production orders, yard inventory, work instructions and collected production data, quality data, production schedules. 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.

# psimetals-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_genealogy:      # material id -> parent and child materials and processing steps
    backend: Factory Model, resource confirmed in blueprint
    mode: read
  get_production_order_status: # order number -> status, assigned material, due date
    backend: confirmed in blueprint
    mode: read
  find_material_in_yard:       # material or order -> yard location
    backend: confirmed in blueprint
    mode: read
  list_quality_holds:          # line, date range -> materials on quality hold with reason
    backend: confirmed in blueprint
    mode: read
audit: every call logged with user, tool, arguments and the PSImetals 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.

PSImetals 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

What is the genealogy of coil C123: which slab, heat and processing steps?
Which production orders for customer X are at risk of missing their due date?
Where in the yard are the coils for order 4711 stored?

What it will not do

Write to PSImetals: the connector is read-only and never changes orders, schedules or material.
Read more than the asking user may read in PSImetals; permissions come from PSImetals, not from the connector.
Talk to Level 2 or process control: the connector reads the MES layer only.

When this is the wrong page

If PSI's MCP interface to the Factory Model is available for your release and licence, it is the better choice, because PSI maintains it; ask PSI for a date first. A connector is right when that answer is no or not yet, or when the assistant has to combine PSImetals with ERP or quality data.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your PSImetals owners and checks every backend against your release and licence. Week two tests whether a person's own PSImetals 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 PSImetals 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: PSImetals · PSImetals Production · PSI at Hannover Messe 2026 · PSImetals Release 5.30. 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 PSImetals teams ask before the first tool call

Does PSImetals have its own MCP server?

Announced, not available. As of 21 September 2026, PSI has presented an MCP interface to the PSI Factory Model at Hannover Messe 2026, but has published no documentation or general availability date. Ask PSI whether and when it reaches your release before you commission a build.

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

PSI does not publish licence terms for API access or for its MCP interface. Every interface to PSImetals runs through a PSI project, so check access and licensing with PSI first. The blueprint settles it before any tool is built.

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

No. Each call runs under the asking person's PSImetals identity, from release 5.30 through Keycloak, so PSImetals decides every answer. Two users asking the same question can get two different answers, and that is tested before go-live.

What does a PSImetals 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 PSImetals administrator in the room if you like.