For manufacturers running Monitor G5
A Monitor ERP MCP server gives Claude, ChatGPT or Copilot named tools for manufacturing orders, stock, customer and purchase orders. Monitor documents its REST API in public; reading is included, writing needs paid API licences. Monitor ships no MCP server as of 21 September 2026, so Pexon builds one against your installation.
What we build
Built on what Monitor ERP System AB documents: customer orders, quotes, parts and stock, manufacturing orders and operations, work centres, purchase orders and deliveries, suppliers, vouchers and ledgers. 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.
# monitor-erp-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_manufacturing_orders: # status, part, date range -> manufacturing orders with status and reported quantity
backend: GET api/v1/Manufacturing/ManufacturingOrders
mode: read
get_part_stock: # part number -> stock balance by location
backend: Inventory module, Parts and PartLocations
mode: read
get_customer_orders: # customer, delivery date range -> open customer orders and rows
backend: Sales module, CustomerOrders
mode: read
get_purchase_orders: # supplier or part -> open purchase orders and expected deliveries
backend: Purchase module, PurchaseOrders
mode: read
draft_customer_order: # customer, parts, quantities -> validated order draft, rolled back, for a person to confirm
backend: Sales command with /Simulate
mode: propose
audit: every call logged with user, tool, arguments and the Monitor ERP 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.
Checked 21 September 2026
| What we found | |
|---|---|
| Interfaces | Monitor ERP API v1 (REST/JSON, docs public): runs on the customer's Monitor server; reads are queries with filter and expand options, writes are commands with /Validate and /Simulate · Full Access API (REST/JSON, docs public): reading is included for every customer; writing needs paid API licences per user |
| Authentication | Login with a normal Monitor user returns a session ID sent on every request (X-Monitor-SessionId), optionally with Monitor MFA. From release 25.8, OIDC login with Authorization Code and PKCE via Microsoft Entra ID. Actions are change-tracked as that user. |
| Vendor MCP server | No vendor server. No Monitor ERP MCP server on monitorerp.com or api.monitor.se, and no community server found in the MCP directories. |
| Vendor AI assistant | MAiA, Monitor's AI assistant, answers questions on orders, customers and deliveries inside the Monitor web client; it requires the web client and the PostgreSQL migration. |
| Other connectors | Lerry.ai is listed as a Monitor integration for finance teams; it is an assistant product, not a general agent connector. |
Monitor ERP System AB (SE). Small and mid-sized discrete manufacturers in metal, machinery, electronics and plastics, mostly in the Nordics; Monitor states more than 6,500 manufacturing companies in 16 countries.
Why Monitor ERP is hard for agents
01 · Network
The API is served from the customer's own Monitor server on port 8001 with a self-signed certificate. An assistant in the cloud needs a tunnel or gateway into that network and a pinned certificate, which is a firewall change your IT team has to own.
02 · Identity
Every request carries a Monitor session, and a forced re-login closes the user's other sessions. Before release 25.8 there is no single sign-on, so carrying each person's own identity through means managing Monitor sessions on their behalf. From 25.8, Entra ID login makes that clean.
03 · Licensing
Every Monitor system ships with a read-only API user. Any tool that creates or changes a record needs paid API licences per user, so the write tools in the manifest are a licensing decision before they are an engineering one.
04 · Versions
Monitor documents the version in which each entity and property was introduced. A tool built against 25.8 can find a field missing on an older release, so the connector checks the server version and the tool list is pinned to your release.
Monitor ERP 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 everyone who needs answers already works in the Monitor web client, MAiA is the shorter path and Monitor maintains it. A connector is right when the assistant lives outside Monitor, in Claude, ChatGPT or Copilot, or has to combine Monitor with another system such as a PLM or a quality database.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your Monitor ERP owners and checks every backend against your release and licence. Week two tests whether a person's own Monitor ERP 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 Monitor ERP 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. Monitor has an AI assistant, MAiA, inside its web client, and a fully public REST API at api.monitor.se. An MCP server for assistants outside Monitor has to be built against that API, which is what this page describes.
For reading, no: every Monitor system includes a read-only API user. Any tool that creates or changes a record needs paid Monitor API licences per user. We start read-only and add a write tool only after that licence question is answered with Monitor.
No. Each call runs under the asking person's Monitor login, or from release 25.8 their Entra ID sign-in, so Monitor's own permission check decides every answer. Two users asking the same question can get two different answers, and that is tested before go-live.
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 Monitor ERP administrator in the room if you like.