01 · Docs
The IMSApi reference is not public
iTAC ships the function reference with the installation or through partner access. Every tool is therefore mapped to an IMSApi function on your release in the blueprint, not taken from a public spec.
For electronics and automotive manufacturers running iTAC
An iTAC.MOM.Suite MCP server that traces serial numbers and lots under each user's own iTAC login
An iTAC.MOM.Suite MCP server gives Claude, ChatGPT or Copilot read tools for serial-number history, failed units and material lot traces. iTAC's interface is IMSApi, a station-bound .NET and Java API whose reference is not public. iTAC ships no MCP server as of 21 September 2026, so Pexon builds one against your installation.
Why iTAC.MOM.Suite is hard for agents
Where a iTAC.MOM.Suite connection needs engineering, not configuration
02 · Stations
Every session is bound to a station
IMSApi sessions need a registered station number and station password next to the user login. The MCP server needs its own technical station in iTAC, set up and approved by your MES team.
03 · Database
Reading Oracle directly is a trap
ODBC reads against the Oracle schema skip iTAC's business logic and break when the schema changes on upgrade. The connector goes through IMSApi, even where a direct query looks quicker.
04 · Volume
SMT lines produce huge serial counts
Serial-number volumes on SMT lines are large. Every tool is bounded by serial number, order or time window, so a vague question cannot turn into a full-table read.
Checked 21 September 2026
iTAC.MOM.Suite at a glance: interfaces, access and what exists for AI
| What we found | |
|---|---|
| Interfaces | IMSApi (iTAC MES API) (.NET and Java client libraries, docs behind customer or partner login): station-oriented function API; the reference comes with the iTAC installation or partner access · Oracle database via ODBC (database, docs not published): described by a third party as an integration path; schema not public, and reads bypass iTAC's business logic |
| Authentication | IMSApi opens a session with regLogin: station number and station password plus user name, password and client. The call returns a session ID used on later calls. Authentication for other interfaces is not documented publicly. |
| Vendor MCP server | No vendor server. No iTAC MCP server found; iTAC's own AI product iTAC.CATi uses MES data internally and has no public MCP or agent API. |
| Vendor AI assistant | iTAC.CATi, a chatbot that combines documents, SOPs, MES data and tickets with an LLM and a knowledge graph, and can run fully on premises with local AI. |
| Other connectors | A small community Python wrapper (itac-rest-api) handles station and user login and reads serial-number attributes; Leading2Lean documents an integration for its own product. Neither is an AI connector. |
iTAC Software AG, part of the Dürr Group (DE). Discrete manufacturers in automotive, e-mobility, electronics and EMS, medical technology, metal and injection moulding, typically with serial-number traceability on SMT and assembly lines; references include Festo, Alps Alpine and HELLA.
What we build
A first iTAC.MOM.Suite tool list, written as the manifest your IT team signs
Built on what iTAC Software AG, part of the Dürr Group documents: serial numbers and serial number attributes, production orders, components, lots and supplier lots, production events and processing statuses, machine states, quality inspections and measurement results, lock indicators, master data. 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.
# itac-mom-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_serial_history: # serial number -> station bookings, results, timestamps
backend: IMSApi, function confirmed in blueprint
mode: read
get_serial_attributes: # serial number -> stored attributes
backend: IMSApi attribute read, confirmed in blueprint
mode: read
list_failed_units: # station, time range -> serial numbers with fail result and failure code
backend: confirmed in blueprint
mode: read
trace_material_lot: # material lot -> affected serial numbers and orders
backend: confirmed in blueprint
mode: read
draft_serial_lock: # serial list, reason -> lock proposal for a quality engineer to confirm
backend: confirmed in blueprint
mode: propose
audit: every call logged with user, tool, arguments and the iTAC.MOM.Suite 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.
iTAC.MOM.Suite 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
- Show the full traceability for serial number SN123: which stations, results and components?
- Which serial numbers failed at test station X in the last shift?
- Which material lot was used on order 4711, and which serial numbers are affected?
What it will not do
- Lock, release or book a unit by itself: the only write tool drafts a serial lock and a quality engineer confirms it in iTAC.
- Read more than the asking user may read in iTAC; permissions come from the iTAC user behind each session, not from the connector.
- Run unbounded queries: every call is limited by serial number, order or time window.
When this is the wrong page
If the goal is a chatbot over SOPs, documents and MES data inside the plant, iTAC.CATi is the shorter path and runs on premises. A connector is right when people ask from Claude, ChatGPT or Copilot, or need iTAC traceability next to ERP or quality data.
Start with the Readiness Blueprint.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your iTAC.MOM.Suite owners and checks every backend against your release and licence. Week two tests whether a person's own iTAC.MOM.Suite 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 iTAC.MOM.Suite 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.
Related
- Connectors for 100 source systems — the dated catalogue this page belongs to
- Claude MCP server development — how we build an MCP server for any internal system
Questions iTAC.MOM.Suite teams ask before the first tool call
Does iTAC.MOM.Suite have its own MCP server?
Not as of 21 September 2026. iTAC offers iTAC.CATi, a chatbot over documents and MES data, but no public MCP or agent API. An MCP server for Claude, ChatGPT or Copilot has to be built against IMSApi.
Do we need extra iTAC licences or access for an AI connector?
The connector needs IMSApi access and its own technical station registered in iTAC. iTAC does not publish whether that station or API use is licensed separately, so check it with iTAC before the build. The blueprint settles it before any tool is written.
Can the assistant see data a user is not allowed to see in iTAC?
No. IMSApi sessions carry a user login next to the station, and each call runs under the asking person's iTAC user, so iTAC's own permission check decides every answer. That is tested with two different users before go-live.
What does an iTAC.MOM.Suite 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 iTAC.MOM.Suite administrator in the room if you like.