For wholesalers and manufacturers running Comarch ERP Enterprise
A Comarch ERP Enterprise MCP server gives Claude, ChatGPT or Copilot named tools for item availability, sales orders, delivery status and open items. Comarch documents programmable REST and SOAP web services and REST cockpit exports in public. Comarch ships no MCP server as of 21 September 2026; ChatERP works inside the ERP.
What we build
Built on what Comarch Software und Beratung AG (Comarch SA) documents: cockpit query results, items and item availability, sales orders and order confirmations, delivery status, partners, open items, inventory postings. 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.
# comarch-erp-enterprise-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_cockpit: # cockpit service and filters -> rows as XML or CSV
backend: REST cockpit export /services/rest/<service>/search.<ext>
mode: read
get_item_availability: # item number, quantity -> available quantity and date
backend: confirmed in blueprint
mode: read
get_sales_order_status: # order number -> positions and delivery status
backend: confirmed in blueprint
mode: read
list_open_items: # partner -> open receivables
backend: confirmed in blueprint
mode: read
draft_sales_order: # customer, items -> order draft a person confirms
backend: programmable REST service, confirmed in blueprint
mode: propose
audit: every call logged with user, tool, arguments and the Comarch ERP Enterprise 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 | Programmable web services (REST (JAX-RS) and SOAP 1.2 (Apache CXF), docs public): services are Java applications built in the Comarch development environment, called under /services/rest/ or /services/soap/ per OLTP database; Swagger UI and OpenAPI spec from version 6.5 · REST-conform cockpit exports (REST (XML, CSV, XLS, HTML), docs public): exposes any customisable cockpit query as a read-only search service with filter, sort and column parameters · ODBC data sources (database, docs public): read-only over HTTPS with ERP metadata; business entity permissions are evaluated |
| Authentication | Clients authenticate to the web server by digest authentication or client certificate over HTTPS. Each web service is an application with its own authorisation in the ERP. The Swagger service also needs an active ERP UI session on the OLTP database. |
| Vendor MCP server | No vendor server. No Comarch MCP server for Comarch ERP Enterprise; the knowledge base has no MCP entry and nothing appears in GitHub or the MCP directories. |
| Vendor AI assistant | ChatERP, a chat assistant inside Comarch ERP Enterprise, answers how-to questions, queries item, availability, order and delivery data and performs selected actions such as creating orders; version 6.5 adds AI demand forecasting. |
| Other connectors | None found. |
Comarch Software und Beratung AG (Comarch SA) (DE). Mid-sized wholesale, trading and manufacturing companies, mainly in Germany and Poland, on a Java-based ERP with its own development environment.
Why Comarch ERP Enterprise is hard for agents
01 · Services
REST and SOAP services are Java applications built in the Comarch development environment, not an out-of-the-box object API. Each tool needs a service developed for it, or a cockpit exposed as a REST export. The blueprint decides which per tool.
02 · Identity
Calls authenticate by digest or client certificate, and each web service carries its own ERP authorisation. The Swagger service even needs a live ERP UI session. A headless agent setup that still runs as each person needs careful design.
03 · Scope
Each call is scoped to an OLTP database with the oltp parameter. In a multi-company installation the connector has to route each question to the right database and context explicitly.
Comarch ERP Enterprise 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 work inside Comarch ERP Enterprise, ChatERP already answers item, order and delivery questions there and Comarch maintains it. A connector is right when the assistant lives in Claude, ChatGPT or Copilot, or has to combine the ERP with another system.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your Comarch ERP Enterprise owners and checks every backend against your release and licence. Week two tests whether a person's own Comarch ERP Enterprise 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 Comarch ERP Enterprise 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. Comarch ships ChatERP, an assistant inside Comarch ERP Enterprise, but no MCP server, and the knowledge base has no MCP entry. An assistant outside the ERP has to be connected through the documented web services.
It needs the programmable web services on your installation over HTTPS, with digest or client certificate login. Each web service is an ERP application with its own authorisation, so the tools are granted one by one. Licence terms are not public; check with Comarch.
No. Each call runs as the asking person, and the ERP authorisation of each web service plus the user's rights decide the answer. The ODBC path also evaluates business entity permissions, so no read path bypasses them.
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 Comarch ERP Enterprise administrator in the room if you like.