For manufacturers running Asseco APplus

An APplus MCP server that answers from your ERP under each user's own APplus rights

An APplus MCP server gives Claude, ChatGPT or Copilot named tools for purchase orders, stock, articles and customers. It is built on the APplus web service interfaces, which Asseco documents only for customers and partners. Asseco ships no APplus MCP server as of 21 September 2026; Elly Help answers documentation questions inside APplus 9.

Why APplus is hard for agents

Where a APplus connection needs engineering, not configuration

01 · Docs

No public API reference

The web service documentation is only available through Asseco and its partners. Nothing on this page names an endpoint for that reason. Every backend is confirmed against your installation in the blueprint before a tool is built.

02 · Interfaces

Three integration paths, one per object

APplus exposes web services, the Business Integration Framework and an EDI subsystem. Which path a given object uses depends on the release and the licensed modules. The blueprint picks one path per tool and records why.

03 · Customising

Every installation is its own system

APplus installations are customised per customer. A tool contract that works for one company can miss a field or a rule at the next. Tool contracts are written against your system, not a generic APplus.

04 · Versions

APplus 9 changed the platform

APplus 9 moved the platform from Java 8 to Java 17. Integrations built against older releases may need rework, so the connector is built against the release you run and retested on upgrade.

Checked 21 September 2026

APplus at a glance: interfaces, access and what exists for AI

What we found
InterfacesAPplus web service interfaces (web services (protocol mix not public), docs not published): described by Asseco and partners for MES, CAD, DMS, e-commerce and Office 365; integration partners require APplus 5.2 or higher · Business Integration Framework (BIF) (file/EDI, docs not published): since APplus 6.3; a communicator converts source data into an adaptive structure for the target system · APplus EDI subsystem (file/EDI, docs not published): orders, dispatch advice and invoices, mapped by EDI partners to EDIFACT or VDA
AuthenticationNot documented publicly. How the web services authenticate is confirmed with Asseco in the blueprint.
Vendor MCP serverNo vendor server. No Asseco MCP server or MCP announcement for APplus 9; Asseco's AI messaging centres on the in-product assistant Elly Help and process automation.
Vendor AI assistantAPplus 9, available since 28 April 2025, ships Elly Help, a generative AI assistant that answers from the APplus documentation, plus Flow Mode with more than 60 process templates.
Other connectorsSEEBURGER and Wiberg W6 sell web-service-based APplus connectors for APplus 5.2 or higher; both are integration platforms, not AI connectors.

Asseco Solutions AG (DE). Mid-sized manufacturers and project and service businesses in the DACH region, in machine building, automotive, aerospace and defence and medical technology; Asseco states over 2,000 customers.

What we build

A first APplus tool list, written as the manifest your IT team signs

Asseco Solutions AG does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.

# applus-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
  get_open_purchase_orders:   # supplier, date range -> open purchase orders
    backend: confirmed in blueprint
    mode: read
  get_stock_level:            # article number -> stock per warehouse
    backend: confirmed in blueprint
    mode: read
  get_customer:               # customer number or name -> customer master data
    backend: confirmed in blueprint
    mode: read
  search_articles:            # text -> matching articles
    backend: confirmed in blueprint
    mode: read
  draft_purchase_requisition: # article, quantity -> requisition draft a person confirms
    backend: confirmed in blueprint
    mode: propose
audit: every call logged with user, tool, arguments and the APplus response

The manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.

APplus 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.

What the connector answers, and what it will not do

Questions it answers

  • Which purchase orders for supplier X are still open?
  • What is the current stock for article Y?
  • Which customer master data do we hold for company Z: address, contact and terms?

What it will not do

  • Order anything by itself: the only write tool drafts a purchase requisition and a person confirms it in APplus.
  • Read more than the asking user may read in APplus; the user's own APplus rights decide every call.
  • Replace Elly Help for questions about how APplus works; that assistant answers from the APplus documentation already.

When this is the wrong page

If the question is how to use APplus, Elly Help inside APplus 9 answers from the documentation and Asseco maintains it. A connector is right when an assistant in Claude, ChatGPT or Copilot needs live order, stock or customer data; reporting across years belongs in a warehouse.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your APplus owners and checks every backend against your release and licence. Week two tests whether a person's own APplus 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 APplus 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.

Sources: APplus · APplus 9 release news · APplus 6.3 new functions (BIF) · SEEBURGER APplus connector · Wiberg W6 APplus connector. Read 21 September 2026. Vendor documentation changes; verify against the current release.

Related

Questions APplus teams ask before the first tool call

Does APplus have its own MCP server?

Not as of 21 September 2026. Asseco has shipped Elly Help, an assistant inside APplus 9 that answers from the APplus documentation, but no MCP server and no announcement of one. An assistant outside APplus has to be connected through the web service interfaces.

What licences or access does an APplus connector need?

Integration partners require APplus 5.2 or higher for the web service interfaces. Which modules and licences your release needs for API access is not public, so check with Asseco or your APplus partner; we confirm it in the blueprint.

Can the assistant see data a user is not allowed to see in APplus?

No. The connector is designed so each call runs as the asking person and APplus's own rights decide the answer. How that identity is carried through the web services is not documented publicly, so it is the first thing the blueprint tests.

What does an APplus connector cost?

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

Not a sales call. An architecture call.

Thirty minutes with the engineer who would build the connector, with your APplus administrator in the room if you like.