For French manufacturers running Sylob 9
A Sylob MCP server gives Claude, ChatGPT or Copilot named tools for manufacturing orders, stock and purchasing in Sylob 9. Sylob documents two REST APIs: one returns predefined system-information queries, one runs catalogue actions. Neither Sylob nor Forterro ships an MCP server as of 21 September 2026, so Pexon builds one against your installation.
Why Sylob is hard for agents
01 · Configuration
Every read needs a query built in Sylob's own query builder, and every write an action in the action catalogue. The connector therefore starts with configuration inside Sylob, agreed with your Sylob administrator, before a single tool is written.
02 · Deployment
The knowledge base describes separate access procedures for on-premise, Cloud AWS and MyForterro Cloud. The same tool list can need three different network and authentication set-ups, so the blueprint pins down yours first.
03 · Licensing
The REST APIs need the separately licensed Webservice module with at least one licence. How many licences an assistant used by many people needs is a question for Forterro before it is an engineering one.
04 · Versions
Sylob runs as two product lines, Sylob 5 and Sylob 9, which share a base but not necessarily configurations. The documented REST APIs are in the Sylob 9 knowledge base, so the release you run decides what can be built.
Checked 21 September 2026
| What we found | |
|---|---|
| Interfaces | API REST Système d'Information (REST/JSON, docs public): read API that returns the result of a query defined in the ERP activity 'Interroger le système d'information'; separate access procedures for on-premise, Cloud AWS and MyForterro Cloud · API REST Action (REST/JSON, docs public): read and write actions defined in the action catalogue, with an operation that returns the data schema of an action; needs the Webservice module with at least one licence · EDI (AirSupply, Galia, Chorus) (file/EDI, docs public): sector EDI standards for aerospace and automotive, and public-sector e-invoicing through Chorus |
| Authentication | The REST APIs need the Webservice module licence. The Sylob 9 knowledge base describes separate access procedures for on-premise, Cloud AWS and MyForterro Cloud; token and scope details were not readable in public, so check them with Forterro. |
| Vendor MCP server | No vendor server. No Sylob or Forterro product MCP server; the MCP repositories on Forterro's GitHub are generic tooling, such as a gateway and servers for GitLab, Freshservice and Kubernetes. |
| Vendor AI assistant | Sylob markets machine-learning forecasting, anomaly detection and a conversational assistant for querying the ERP, plus Prodaso for machine monitoring, without a named product or date. |
| Other connectors | None found. |
Forterro (Sylob brand) (FR). French industrial SMEs and mid-sized manufacturers in aerospace, automotive, defence, medical devices, mechanics and plastics; LeMagIT reports about 500 customers in France, 45% on SaaS and 55% on-premise.
What we build
Built on what Forterro (Sylob brand) documents: record sets defined as system-information queries, read and write actions from the action catalogue, orders, invoices and price offers via EDI. 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.
# sylob-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
run_si_query: # query code, parameters -> rows from a predefined system-information query
backend: API REST Système d'Information
mode: read
get_late_manufacturing_orders: # customer or date -> manufacturing orders behind schedule
backend: system-information query, confirmed in blueprint
mode: read
get_stock_position: # article -> stock, reserved and on-order quantities
backend: system-information query, confirmed in blueprint
mode: read
describe_action: # action code -> input schema of a catalogue action
backend: API REST Action (schema operation)
mode: read
draft_purchase_order: # supplier, article, quantity -> purchase order proposal for a person to confirm
backend: API REST Action (catalogue write action)
mode: propose
audit: every call logged with user, tool, arguments and the Sylob 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.
Sylob 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 your users want answers inside Sylob, check with Forterro whether the conversational assistant Sylob markets is available for your release; Forterro would maintain it. A connector is right when the assistant lives in Claude, ChatGPT or Copilot, or has to combine Sylob with another system.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your Sylob owners and checks every backend against your release and licence. Week two tests whether a person's own Sylob 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 Sylob 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. Forterro's GitHub holds generic MCP tooling but nothing for Sylob, and Sylob markets a conversational assistant without a named product or date. An MCP server for Claude, ChatGPT or Copilot has to be built on the Sylob REST APIs.
Yes, at least one: the REST APIs need the Webservice module with at least one licence. How many licences an assistant used by many people needs is a question to check with Forterro. The blueprint answers it before any build starts.
No. How each person's Sylob rights carry through the API is tested in the blueprint, and every read is a reviewed system-information query rather than free SQL. 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 Sylob administrator in the room if you like.