For engineer-to-order manufacturers running Isah
An Isah MCP server gives Claude, ChatGPT or Copilot named tools for production orders, parts, project BOMs and purchase proposals in Isah Business Software. Isah names an API for real-time integration but publishes no reference, so each interface is confirmed with Isah first. Isah ships no MCP server as of 21 September 2026.
Why Isah is hard for agents
01 · Documentation
Isah names an API for real-time integration but publishes no reference, protocol or authentication description. Scope and licensing have to come from Isah before any design, which is why the blueprint starts there.
02 · Installation
Isah's technical consultants typically build the CAD, PDM, warehouse and machine integrations per customer. Two Isah installations can expose different interfaces, so the tool list is checked against yours, not a generic reference.
03 · Database
Community practice relies on direct T-SQL against the Isah database. That bypasses Isah's business logic and permissions, so it is not a basis for an assistant that answers under each person's own rights.
04 · Data depth
Project BOMs, routings and revisions are deep and configured per customer. A question such as 'what is the material status of project P' needs a mapping to your structure, agreed with your Isah owners.
Checked 21 September 2026
| What we found | |
|---|---|
| Interfaces | Isah API (real-time integration) (not published, docs not published): named by Isah for machine and shop-floor connections; no public reference · XML exchange (periodic synchronisation) (file/EDI, docs not published): named by Isah for shop floor control integrations · SQL Server database (database, docs not published): community T-SQL scripts indicate SQL Server; the schema is not publicly documented |
| Authentication | Not documented publicly. |
| Vendor MCP server | No vendor server. No Isah MCP server on isah.com or GitHub, where a search returns only community scripts and an Excel macro. |
| Vendor AI assistant | Isah describes AI for natural-language information requests with proactive deviation alerts, decision support, and automation of invoice processing and purchase proposals, without a named assistant or availability date. |
| Other connectors | ISAH_ERP_Community on GitHub shares T-SQL and AutoIt scripts that work on the database directly; it is not an API or agent connector. |
Isah (NL). Engineer- and make-to-order manufacturers in machine building, metal, maritime, steel, mechatronics, plastics, concrete, furniture and electronics; Isah cites more than 750 customers in over 25 countries.
What we build
Isah does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.
# isah-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_production_orders: # project or date range -> production orders with status
backend: confirmed in blueprint
mode: read
get_part_info: # part code -> revision, stock and open orders
backend: confirmed in blueprint
mode: read
get_project_bom: # project -> BOM lines and material status
backend: confirmed in blueprint
mode: read
list_purchase_proposals: # item or supplier -> open purchase proposals
backend: confirmed in blueprint
mode: read
draft_purchase_order: # proposal -> purchase order draft for a person to confirm
backend: confirmed in blueprint
mode: propose
audit: every call logged with user, tool, arguments and the Isah 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.
Isah 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 want answers inside Isah, check with Isah whether the natural-language requests it describes are available for your release; Isah would maintain them. A connector is right when people ask questions in Claude, ChatGPT or Copilot, or need Isah combined with another system.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your Isah owners and checks every backend against your release and licence. Week two tests whether a person's own Isah 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 Isah 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. Isah describes AI for natural-language information requests and purchase proposals, without a named assistant or availability date, and no MCP server appears on isah.com or GitHub. An MCP server for Claude, ChatGPT or Copilot has to be built on the interfaces Isah supports.
Isah does not publish its API reference, authentication or licensing. We need that material through you or your Isah consultant, and the licence question is one to check with Isah. The blueprint answers both before any build starts.
No. The connector does not query the SQL Server database directly, because that bypasses Isah's permissions. How each person's Isah rights carry through the supported interface is tested in the blueprint, and no tool goes live before that test passes.
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 Isah administrator in the room if you like.