For manufacturers and wholesalers running Proalpha ERP
A Proalpha MCP server gives Claude, ChatGPT or Copilot named tools for customers, sales orders, invoices, stock and work orders. Proalpha publishes OpenAPI specs for its REST APIs from release 9.4, with every endpoint blocked until authorised. Proalpha ships no MCP server as of 21 September 2026, so Pexon builds one against your installation.
What we build
Built on what Proalpha Group GmbH documents: customers, customer sales orders, customer invoices and quotes, contact persons and prospects, suppliers, inventory overview, projects, production work orders and operations. 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.
# proalpha-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
find_customer: # name or customer number -> customer GUID and master data
backend: GET /api/web/v2/crm/customer/list
mode: read
get_customer_sales_orders: # customer GUID -> sales orders with document number, date, net total
backend: GET /api/web/v1/crm/customer/{customerGuid}/salesOrders
mode: read
get_customer_invoices: # customer GUID -> invoices of the customer
backend: GET /api/web/v1/crm/customer/{customerGuid}/invoices
mode: read
get_inventory_overview: # article filter -> stock overview
backend: GET /api/web/v1/mawi/lager/InventoryOverview/
mode: read
list_projects: # filter -> projects
backend: GET /api/web/v1/proj/project/list
mode: read
propose_operation_dates: # work order operation, new start and end -> draft change a person confirms before it is posted
backend: POST /api/web/v1/pps/prod/setWorkOrderOperationDates/
mode: propose
audit: every call logged with user, tool, arguments and the Proalpha 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 | Proalpha ERP REST APIs (V9.4.x / V9.5.x) (REST/JSON, docs public): OpenAPI specs on the Proalpha API portal, served by the Progress PASOE AppServer; privileges as of 9.4.0; endpoints are configured per customer by a Proalpha consultant · Integration Workbench (INWB) (file/EDI, docs public): message-based replication and integration layer; the ERP message API on the portal is tagged inwb |
| Authentication | Incoming requests authenticate against the Progress PASOE agent with Basic Auth or OAuth tokens, which need a third-party token builder. The user also needs the Proalpha service REST SERVICES and an explicit WebRequest authorisation per endpoint and HTTP method; every endpoint is blocked by default. |
| Vendor MCP server | No vendor server. No Proalpha-published MCP server; Proalpha markets its own AI Platform with a data context layer and an agent layer, with no mention of MCP. |
| Vendor AI assistant | The Proalpha AI Platform names use cases such as an Intelligent Sales Assistant and 8D-Assist; inside the ERP, Connected AI (as of 9.4.0) uses the Nemo analysis system for master data quality checks. |
| Other connectors | A community server, mcp-proalpha, runs read-only SQL against the Proalpha MSSQL database and bypasses ERP logic and permissions; LIT Beratung sells a REST add-on (ICR) for older releases. |
Proalpha Group GmbH (DE). Small and mid-sized manufacturing and wholesale companies, mainly in Germany, Austria and Switzerland; the Proalpha Group reports more than 17,500 customers across all its products, not the ERP alone.
Why Proalpha is hard for agents
01 · Endpoints
Endpoints are defined in configuration files and implemented as PASOE handler classes that only Proalpha developers provide. A Proalpha consultant customises them per customer, so the API set differs by installation and release. The tool list is checked against what your system actually serves.
02 · Access
A call passes PASOE authentication, needs the REST SERVICES service on the user, and needs a WebRequest authorisation for that endpoint and HTTP method. Every endpoint starts blocked. Missing the service returns 401, a missing endpoint grant returns 403.
03 · Identity
The published OpenAPI specs declare Basic Auth only. Token-based login to PASOE needs a third-party token builder. Carrying each person's own identity through without shared passwords is a design decision for the blueprint.
04 · Coverage
The published 9.4.x and 9.5.x catalogue is weighted towards CRM (built for Gedys) and production work orders. There is no published endpoint for purchase orders or the general ledger, so those need custom endpoints or INWB. Releases before 9.4 lack the documented privilege model.
Proalpha 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 the use case is one Proalpha already names for its own AI Platform, such as the sales assistant or 8D-Assist, ask Proalpha first. A connector is right when the assistant lives in Claude, ChatGPT or Copilot, or has to combine Proalpha with another system; reporting across years of data belongs in a warehouse.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your Proalpha owners and checks every backend against your release and licence. Week two tests whether a person's own Proalpha 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 Proalpha 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. Proalpha markets its own AI Platform with a data context layer and an agent layer, without mentioning MCP. A community server exists, but it reads the SQL database directly and skips Proalpha's permissions.
The REST API framework runs on the Progress PASOE AppServer and needs the REST SERVICES service on each user. Each endpoint and HTTP method must be authorised explicitly, because all start blocked. Which endpoints your installation serves, and under which licence, is checked with Proalpha in the blueprint.
No. Each call runs as the asking person, so Proalpha's own WebRequest authorisations decide what comes back. A user without the grant for an endpoint gets a 403, and the assistant reports that rather than working around it.
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 Proalpha administrator in the room if you like.