For distributors and manufacturers running Divalto infinity
A Divalto MCP server gives Claude, ChatGPT or Copilot named tools for customers, sales orders, stock and intervention requests in Divalto infinity. Divalto documents a REST API that runs DIVA actions and SQL definitions, plus a read-only OData service. Divalto ships no MCP server as of 21 September 2026, so Pexon builds one against your installation.
What we build
Built on what Divalto documents: ERP tables and views in the visible SQL dictionary (read-only via OData), record sets defined as DHOQ SQL definitions, business actions implemented as DIVA programs, CRM customers, deals, opportunities and prospects (weavy), intervention requests (weavy). 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.
# divalto-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
query_customer: # name or code -> customer master record
backend: OData table or view, physical name confirmed in blueprint
mode: read
get_open_sales_orders: # customer, date range -> open order lines
backend: RecordSql/Execute with a DHOQ definition
mode: read
get_stock_levels: # article -> stock per warehouse
backend: OData or RecordSql/Execute
mode: read
list_intervention_requests: # customer -> open intervention requests
backend: confirmed in blueprint
mode: read
draft_sales_quote: # customer, articles -> quote draft for a person to confirm
backend: WebService/Execute calling a DIVA action
mode: propose
audit: every call logged with user, tool, arguments and the Divalto 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 | Divalto REST web services (api.divaltocloud.com) (REST/JSON, docs public): Authent/Auth, WebService/Execute to run DIVA actions and RecordSql/Execute for SQL record definitions set up in Cloud Administration, up to 1,000 records per call; SOAP is no longer supported since September 2024 · Divalto OData service (OData, docs public): read-only access to tables and views of the ERP and weavy CRM databases hosted in Divalto Cloud, with physical table and field names · Harmony / DIVA development layer (REST/JSON, docs public): custom services written in Divalto's DIVA language and exposed through WebService/Execute |
| Authentication | Credentials are posted as JSON to Authent/Auth, which returns an access token valid for 45 minutes, sent on every following call. |
| Vendor MCP server | No vendor server. No Divalto MCP server for infinity; Divalto writes about MCP without a product, and its public divalto-ia-devkit is a Claude Code plugin for DIVA developers, not a data connector. |
| Vendor AI assistant | Divalto has announced industry AI agents inside its ERP and CRM from autumn 2026, for sales and field intervention, procurement, planning and routing, and fault diagnosis. |
| Other connectors | Zapier offers MCP access to Divalto weavy, the CRM only, with six triggers and three actions and no ERP coverage. |
Divalto (FR). French-speaking SMEs and mid-sized companies in B2B distribution, field service and manufacturing, in France and Quebec; Divalto cites 85,000 users across its solutions.
Why Divalto is hard for agents
01 · Configuration
REST calls do not expose business objects directly. They run a DIVA action or a DHOQ SQL definition configured in Cloud Administration. Each agent tool therefore starts as a definition inside Divalto, which your Divalto partner or developer owns.
02 · Semantics
The OData service is read-only and uses physical table and field names, without business aliases, and only fields in the visible SQL dictionary. An agent cannot guess what a column means, so the connector carries a mapping from business terms to tables, reviewed with your Divalto owners.
03 · Hosting
The REST API is documented at api.divaltocloud.com, per site and environment. Customers running Divalto on-premise need their own exposure path for the same services, which is a network decision your IT team has to own.
04 · Sessions
Tokens expire after 45 minutes, so the connector renews them without dropping a running question. Integrations built on SOAP before September 2024 no longer work and have to be moved to REST before they can be reused.
Divalto 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 you only need weavy CRM data, Zapier's MCP access for weavy already exists. If your users will work inside Divalto, check with Divalto whether its announced industry AI agents cover your questions; a connector is right when the assistant lives in Claude, ChatGPT or Copilot, or has to reach ERP data.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your Divalto owners and checks every backend against your release and licence. Week two tests whether a person's own Divalto 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 Divalto 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. Divalto has announced industry AI agents inside its ERP and CRM from autumn 2026 and writes about MCP, but ships no MCP server for infinity. Zapier offers MCP access to the weavy CRM only, without ERP data.
Every REST tool runs a DIVA action or a DHOQ SQL definition that has to be configured in Cloud Administration first, so your Divalto partner is part of the project. Whether that work or the API access carries a licence cost is a question to check with Divalto. The blueprint answers both before any build starts.
No. How each person's Divalto rights carry through the API token is tested in the blueprint, and no tool goes live until two users asking the same question get the answers their own rights allow. Writes only happen as drafts a person confirms in Divalto.
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 Divalto administrator in the room if you like.