For trading and manufacturing companies running Opacc OXAS
An Opacc MCP server gives Claude, ChatGPT or Copilot named tools for customers, open orders, stock and DMAS documents in Opacc OXAS. Opacc states every OXAS resource is readable and writable through its Service Bus API, whose reference sits behind the customer portal. Opacc ships no MCP server as of 21 September 2026.
Why Opacc is hard for agents
01 · Documentation
Opacc publishes no API reference, protocol or authentication description; the technical material sits in the customer portal. Nothing can be designed until a customer or partner login gives access, which is why the blueprint starts there.
02 · Paths
Opacc names the Service Bus API, the Custom Programming Interface, Web Application Services and EDI or database access. Opacc describes the Service Bus as the version-safe path and sells an update guarantee, so the connector should sit there rather than on a path that breaks at the next release.
03 · Stack
OXAS runs on SQL Server, Oracle, MySQL, PostgreSQL or IBM DB2, on-premise or in Opacc Smart Cloud. Direct database access would be specific to each installation, which is one more reason to stay on the Service Bus.
04 · Generations
Opacc introduced its fifth-generation Nytron interface in April 2024, so installations differ in which generation they run. The blueprint checks your release before any tool list is agreed.
Checked 21 September 2026
| What we found | |
|---|---|
| Interfaces | OXAS Service Bus API (not published, docs behind customer or partner login) · Custom Programming Interface (CPI) and Web Application Services (WAS) (not published, docs not published) · EDI, XML, JDBC and ODBC (file/EDI, database, docs not published) |
| Authentication | Not documented publicly. |
| Vendor MCP server | No vendor server. No MCP server or agent interface on opacc.ch or in the MCP directories. |
| Vendor AI assistant | Opacc AI Integration Services connect DeepL for translation and the OXAS DataScience Platform, since end of 2023, for customer segmentation, product recommendations and demand forecasting; there is no chat assistant. |
| Other connectors | None found. |
Opacc Software AG (CH). Mid-sized trading and manufacturing companies in Switzerland, Germany and Austria; the topsoft product profile lists over 200 installations.
What we build
Opacc Software AG does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.
# opacc-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
search_customer: # name or number -> customer master data
backend: OXAS Service Bus API, resource confirmed in blueprint
mode: read
get_open_sales_orders: # customer, date range -> open orders with status
backend: OXAS Service Bus API, resource confirmed in blueprint
mode: read
get_article_stock: # article number -> stock and availability
backend: OXAS Service Bus API, resource confirmed in blueprint
mode: read
find_documents: # business object reference -> linked DMAS documents
backend: OXAS Service Bus API, resource confirmed in blueprint
mode: read
draft_quote: # customer, articles, quantities -> quote draft for a person to confirm
backend: OXAS Service Bus API, resource confirmed in blueprint
mode: propose
audit: every call logged with user, tool, arguments and the Opacc 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 published. Documentation is behind customer or partner login. Opacc states all OXAS resources are available to read and write through it; technical material sits in the Opacc customer portal
02
not published. Documentation is not published. named by Opacc for custom integrations and custom web apps on OXAS, without public technical detail
03
file/EDI, database. Documentation is not published. listed on the topsoft profile; OXAS runs on-premise or in Opacc Smart Cloud on several database systems
Opacc 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 what you need is forecasting or product recommendations, the OXAS DataScience Platform is Opacc's own route and Opacc maintains it. A connector is right when people ask questions in Claude, ChatGPT or Copilot, or need Opacc combined with another system.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your Opacc owners and checks every backend against your release and licence. Week two tests whether a person's own Opacc 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 Opacc 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. Opacc's AI Integration Services cover DeepL and the OXAS DataScience Platform, with no chat assistant and no MCP server. An MCP server for Claude, ChatGPT or Copilot has to be built on the OXAS Service Bus API.
Opacc does not publish the API reference, its authentication or its licensing; the technical material sits in the Opacc customer portal. We need access to that material through you or your Opacc partner, and the licence question is one to check with Opacc. The blueprint answers both before any build starts.
No. How each person's OXAS rights carry through the Service Bus API 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 Opacc.
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 Opacc administrator in the room if you like.