For machine builders and suppliers running PSIpenta/ERP
A PSIpenta MCP server gives Claude, ChatGPT or Copilot read-first tools for purchase orders, order confirmations, incoming invoices and sales orders. PSIpenta/ERP offers the BOB-API and a REST API, neither with a public reference. PSI ships no MCP server as of 21 September 2026, so Pexon builds one against your installation.
Why PSIpenta is hard for agents
01 · Docs
Neither the BOB-API nor the REST API has a public reference. Documentation comes from PSI or implementation partners. Whether the two names describe the same interface is a question for PSI, answered in the blueprint.
02 · Data model
Incoming invoices live in PREK and PREP, order confirmations in PEKK and PEKP. These are PSIpenta's own abbreviations. Mapping tools to them needs someone who knows the PSIpenta data model on your side or at PSI.
03 · Versions
PSIpenta 10, released in November 2024, is Java-based with a PostgreSQL option, while older releases remain in use. API availability differs per installation, so the tool list is pinned to the release you run.
04 · MES
ERP and MES are tightly coupled at many PSIpenta customers. The current state of a production order may live in PSIpenta/MES rather than the ERP. The blueprint decides which system answers which question.
Checked 21 September 2026
| What we found | |
|---|---|
| Interfaces | BOB-API (universal interface) (not documented publicly, docs not published) · PSIpenta REST API (REST/JSON, docs not published) · Web services, files and EDI (myOpenFactory) (file/EDI, docs public) |
| Authentication | Not documented publicly. How the REST API authenticates is confirmed with PSI in the blueprint. |
| Vendor MCP server | No vendor server. No PSI-published MCP server for PSIpenta, and none in GitHub or the MCP directories; the partner PentaFlow builds custom agents on the REST API, not MCP. |
| Vendor AI assistant | None found. |
| Other connectors | PentaFlow AI builds custom agents that read and write incoming invoices and order confirmations through the PSIpenta REST API, with a person in the loop; it is not an MCP server. |
PSI Software SE (Discrete Manufacturing) (DE). Mid-sized discrete manufacturers in machine and plant building, automotive supply and series, variant and project manufacturing in the DACH region, often together with PSIpenta/MES.
What we build
PSI Software SE (Discrete Manufacturing) does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.
# psipenta-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_purchase_order: # purchase order number -> positions, prices, promised dates
backend: confirmed in blueprint
mode: read
list_order_confirmations: # supplier, period -> confirmations with deviations
backend: PSIpenta REST API, PEKK/PEKP, resource confirmed in blueprint
mode: read
list_unmatched_invoices: # period -> incoming invoices without purchase order match
backend: PSIpenta REST API, PREK/PREP, resource confirmed in blueprint
mode: read
get_sales_order_status: # sales order -> delivery date, availability, progress
backend: confirmed in blueprint
mode: read
draft_invoice_booking: # invoice PDF and purchase order -> booking proposal a person confirms
backend: PSIpenta REST API, PREK, resource confirmed in blueprint
mode: propose
audit: every call logged with user, tool, arguments and the PSIpenta 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.
One interface per row
01
not documented publicly. Documentation is not published. named in the PSIpenta/ERP 10 trade report as the interface for connecting external applications
02
REST/JSON. Documentation is not published. used by the partner PentaFlow to read and book incoming invoices and order confirmations; its relation to BOB-API is not public
03
file/EDI. Documentation is public. PSI names interfaces to all EDI formats, with myOpenFactory as universal EDI translator
PSIpenta 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 only goal is invoice and order confirmation processing, a dedicated product such as PentaFlow already covers it on the PSIpenta REST API. A connector is right when an assistant in Claude, ChatGPT or Copilot needs to answer across purchasing, sales and production.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your PSIpenta owners and checks every backend against your release and licence. Week two tests whether a person's own PSIpenta 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 PSIpenta 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. PSI has published no MCP server for PSIpenta, and none appears in GitHub or the MCP directories. The partner PentaFlow builds invoice and order confirmation agents on the REST API, but not as an MCP server.
It needs the PSIpenta REST API or BOB-API on your installation and, for a cloud assistant, a VPN or reverse proxy into your network. Licence terms for API access are not public, so check with PSI; we confirm them in the blueprint.
No. The connector is designed so each call runs as the asking person and PSIpenta's own rights decide the answer. How the API carries that identity is not documented publicly, so the blueprint tests it with two users before any build.
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 PSIpenta administrator in the room if you like.