For machine builders running Abas ERP
An Abas ERP MCP server gives Claude, ChatGPT or Copilot named tools for products, customers, opportunities and infosystems. It runs on the Abas REST API, whose reference sits behind the partner extranet. Forterro ships no Abas MCP server as of 21 September 2026 and only describes MCP for a future MyForterro API.
Why Abas ERP is hard for agents
01 · Docs
The REST API and SDK documentation moved to the Abas partner extranet, and the old public pages redirect to a login. Only Abas's own demo clients on GitHub remain public. Every backend is confirmed against your release in the blueprint.
02 · Data model
Objects are addressed by internal database and group numbers, such as 2:1 for products and 3:30 for opportunities, with German field names like nummer and such. Every installation adds its own fields and infosystems, so the tool mapping is per customer.
03 · Writes
A change is not a single PUT. It opens an editor, sets fields, commits and closes. A write tool has to handle locking and roll back cleanly when a person rejects the draft.
04 · Network
An on-premises Abas server is not reachable by a cloud-hosted assistant by default. abas Cloud Connect or your own reverse proxy exposes the REST API with outbound traffic only, which your IT team has to approve.
Checked 21 September 2026
| What we found | |
|---|---|
| Interfaces | abas REST API (middleware) (REST/JSON, docs behind customer or partner login): hypermedia API that reads and writes in real time through ERP core logic and customer customisations; reference moved to the partner extranet · abas Cloud Connect (REST/JSON, docs public): reverse proxy for on-premises installations, outbound HTTPS 443 only, so cloud clients reach the REST API without a VPN · MS SQL Connector (database, docs public): exports Abas ERP data to SQL Server tables with incremental synchronisation, a read-side option for reporting |
| Authentication | The REST API supports OAuth 2.0 through abas Cloud Connect, with AD, LDAP, SAML or OpenID Connect as identity providers, and Basic Auth without OAuth. Requests run under an Abas ERP user and client, so ERP permissions apply. |
| Vendor MCP server | No vendor server. No Abas or Forterro MCP server; the Abas AI page says future AI access will run through the MyForterro API 'based on modern standards such as MCP'. Only a community skeleton exists. |
| Vendor AI assistant | Abas lists machine learning in customer support and production analytics via Forterro's Prodaso unit; customer-facing AI functions are announced for the MyForterro API, most described as planned. |
| Other connectors | A community MCP skeleton (abasapi-mcp) on the REST API, and innfactory's CompanyGPT integration with MCP-style tools tied to that product. |
Forterro (Abas Software GmbH) (DE). Mid-market discrete manufacturers in machine building, make-to-order and variant production, mainly in DACH; Forterro states 4,000 customers and 120,000 users.
What we build
Built on what Forterro (Abas Software GmbH) documents: products and articles, customers, opportunities, any Abas database object addressed by database and group, infosystems. 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.
# abas-erp-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_products: # search word or number range -> products with number and search word
backend: REST API obj/data/2:1 query
mode: read
get_object: # database:group and ID -> full Abas object with head and table fields
backend: REST API obj/data/<db>:<group>/<id>
mode: read
get_customer: # customer number -> customer master data
backend: REST API customer object, database number confirmed in blueprint
mode: read
list_opportunities: # customer -> opportunities
backend: REST API obj/data/3:30
mode: read
run_infosystem: # infosystem search word and parameters -> result table
backend: REST API infosystem call, confirmed in blueprint
mode: read
draft_opportunity: # customer and fields -> opportunity draft a person confirms before commit
backend: REST API obj/data/3:30 editor command NEW, then commit
mode: propose
audit: every call logged with user, tool, arguments and the Abas ERP 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.
Abas ERP 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 can wait for Forterro's MyForterro API and the MCP access it describes, ask Forterro for a date first. For reporting, the MS SQL Connector and a warehouse are the better path; a connector is right when an assistant in Claude, ChatGPT or Copilot needs live answers now.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your Abas ERP owners and checks every backend against your release and licence. Week two tests whether a person's own Abas ERP 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 Abas ERP 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. The Abas AI page says future AI access will run through the MyForterro API based on standards such as MCP, without a date. Today there is a community skeleton on GitHub and nothing a customer can deploy from Forterro.
It needs the Abas REST API on your installation and, for an on-premises server, abas Cloud Connect or your own reverse proxy. Which modules and licences your release requires is not public, so check with Forterro or your Abas partner; we confirm it in the blueprint.
No. Requests run under the asking person's Abas user and client, so Abas's own permissions decide every answer. With Cloud Connect, sign-in goes through your identity provider, such as Active Directory or an OpenID Connect service.
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 Abas ERP administrator in the room if you like.