For make-to-order manufacturers running ams.erp
An ams.erp MCP server gives Claude, ChatGPT or Copilot named tools for projects, bills of materials, purchasing and quotations. It is built on the ams.erp REST API, whose Swagger documentation sits on each customer installation. ams.Solution ships no MCP server as of 21 September 2026; its own AI chat runs on-premises from release 16.0.
Why ams.erp is hard for agents
01 · Docs
The Swagger documentation is served by each customer installation and taught in vendor training. There is no public copy. Every backend is read from your own Swagger page in the blueprint before a tool is built.
02 · Coverage
ams states that some ERP areas are not supported by the API. Objects outside it need ams Workflow Studio or a custom extension, which is a question for ams before it is an engineering one.
03 · Data model
ams.erp is built for multi-project work where bills of materials grow during engineering. Order, BOM and schedule data change continuously. Tools read the current state on every call and never answer from a cached copy.
04 · Hosting
ams positions its own AI strictly on-premises. The MCP server is therefore planned to run inside your network next to ams.erp, and where the assistant itself runs is agreed with your IT team first.
Checked 21 September 2026
| What we found | |
|---|---|
| Interfaces | ams.erp API (REST/JSON, docs behind customer or partner login): GET, PATCH, POST and DELETE with Swagger documentation served by the customer's own installation; ams states that some areas are not supported by the API · ams.flex business apps (Central Cloud Manager) (not documented publicly, docs public): no-code mobile apps for CRM, purchasing, warehouse and order processes, configured in a web-based manager |
| Authentication | Not documented publicly. The Swagger documentation on your installation shows it, and the blueprint confirms it. |
| Vendor MCP server | No vendor server. No ams.Solution MCP server; the vendor's AI runs on-premises through its own context layer and an integrated AI chat from release 16.0. |
| Vendor AI assistant | From release 16.0, a context layer gives AI access to ERP data plus company documents and drawings, and an integrated AI chat answers in natural language, all on-premises; AI-assisted quotation creation was shown at AMB in September 2026. |
| Other connectors | None found. |
ams.Solution AG (ams.GROUP) (DE). Mid-sized make-to-order and project manufacturers working in lot size 1+: machine and plant building, steel and metal construction and special vehicle building in Germany, Austria and Switzerland.
What we build
Built on what ams.Solution AG (ams.GROUP) documents: projects and orders, quotations, bills of materials, purchasing and warehouse data, forms and dialogs exposed through the API. 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.
# ams-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:
get_project_status: # project number -> budget, capacity, dates and status
backend: ams.erp API, resource confirmed in blueprint
mode: read
get_project_bom: # project number -> current bill of materials
backend: ams.erp API, resource confirmed in blueprint
mode: read
list_open_purchase_items: # project -> open purchasing positions and expected delivery
backend: ams.erp API, resource confirmed in blueprint
mode: read
search_quotations: # customer, keyword -> past quotations
backend: ams.erp API, resource confirmed in blueprint
mode: read
draft_quotation: # customer request -> quotation draft a person confirms
backend: ams.erp API POST, resource confirmed in blueprint
mode: propose
audit: every call logged with user, tool, arguments and the ams.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.
ams.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 run ams.erp 16.0 or later and the questions stay inside ams.erp, the integrated AI chat is the shorter path and ams maintains it. A connector is right when the assistant lives in Claude, ChatGPT or Copilot, or has to combine ams.erp with another system such as a PLM.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your ams.erp owners and checks every backend against your release and licence. Week two tests whether a person's own ams.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 ams.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. ams.Solution ships an integrated AI chat and a context layer from release 16.0, both on-premises, but no MCP server. An assistant outside ams.erp has to be connected through the ams.erp API.
It needs the ams.erp API on your installation and a user with the rights for the objects the tools read. Licence terms for API access are not public, so check with ams.Solution; we confirm them in the blueprint.
No. The connector is designed so each call runs as the asking person and ams.erp's own rights decide the answer. How the API carries that identity is not documented publicly, so the blueprint tests it with two users before any build.
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 ams.erp administrator in the room if you like.