For semiconductor and electronics fabs running camLine LineWorks
A camLine LineWorks MCP server gives Claude, ChatGPT or Copilot read tools for lot status, SPC violations, yield and equipment alarms. LineWorks names an OpenAPI interface in ECoFrame, but the specification is not public. camLine ships no MCP server as of 21 September 2026, so Pexon builds one inside your fab network.
Why camLine LineWorks is hard for agents
01 · Modules
LineWorks is a suite of more than 30 separately licensed modules, from WIP and SPACE to RM and ECoFrame. Each customer runs a different subset. The tool list follows the modules you have installed, not a generic catalogue.
02 · Docs
camLine names an OpenAPI interface but does not publish the specification. Access runs through a camLine project or support, so each backend is confirmed against your release before a tool is built.
03 · Equipment
Equipment data arrives through SECS/GEM and HSMS via ECoFrame. The connector reads the aggregated MES data in LineWorks and never addresses process equipment directly.
04 · Network
Semiconductor fabs run air-gapped or tightly segmented networks. The MCP server has to live inside the fab network, and an assistant outside it reaches it only through a path your IT and security teams approve.
Checked 21 September 2026
| What we found | |
|---|---|
| Interfaces | LineWorks ECoFrame OpenAPI interface (REST/JSON, docs behind customer or partner login): integrates customer applications and routes process data, alarms and events; ECoFrame 5.0 adds optional mTLS · LineWorks SPISE++ RESTful API (REST/JSON, docs behind customer or partner login): integrates SPISE++ data-collection projects, which feed validated data into LineWorks SPACE for SPC · LineWorks ECoFrame equipment layer (SECS/GEM, HSMS, OPC UA, docs behind customer or partner login): equipment side, not the business API; the connector does not use it |
| Authentication | Not documented publicly. ECoFrame 5.0 offers mTLS for HTTP communication between its components; the login method for an external application is confirmed in the blueprint. |
| Vendor MCP server | No vendor server. No camLine or Elisa Industriq MCP server found on the vendor pages or in the MCP directories. |
| Vendor AI assistant | LineWorks Chatbot, an assistant that executes MES commands by voice or text, is part of LineWorks UA 5; Elisa Industriq also markets AI-assisted SPC. |
| Other connectors | None found. |
camLine, part of Elisa Industriq (DE). High-tech manufacturers in semiconductor frontend and backend, electronics, battery, medical devices, solar and automotive; camLine states 350+ customers in 40+ countries.
What we build
Built on what camLine, part of Elisa Industriq documents: lots, serial numbers and carriers, routes and operations, including split, merge and rework loops, bills of materials and assembled parts, yield, failures and loss categories, equipment process data, alarms and events, SPC samples and control charts, recipes. 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.
# camline-lineworks-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_lot_status: # lot id -> current step, carrier, quantity, hold state, history
backend: LineWorks WIP, resource confirmed in blueprint
mode: read
list_spc_violations: # area or chart, time range -> out-of-control points with rule and value
backend: LineWorks SPACE, resource confirmed in blueprint
mode: read
get_yield_summary: # product, date range -> yield and failure categories
backend: LineWorks WIP, resource confirmed in blueprint
mode: read
list_equipment_alarms: # equipment id, time range -> alarms and events routed by ECoFrame
backend: ECoFrame OpenAPI interface, resource confirmed in blueprint
mode: read
draft_lot_hold: # lot id, reason -> hold proposal for an engineer to confirm
backend: confirmed in blueprint
mode: propose
audit: every call logged with user, tool, arguments and the camLine LineWorks 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.
camLine LineWorks 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 operators want to run MES commands by voice or text on the line, LineWorks Chatbot in UA 5 is the shorter path and camLine maintains it. A connector is right when engineers ask from Claude, ChatGPT or Copilot, or need LineWorks data next to ERP or quality data.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your camLine LineWorks owners and checks every backend against your release and licence. Week two tests whether a person's own camLine LineWorks 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 camLine LineWorks 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. camLine offers LineWorks Chatbot inside LineWorks UA 5 for MES commands by voice or text, but no MCP server for outside assistants. An MCP server for Claude, ChatGPT or Copilot has to be built against the LineWorks interfaces.
camLine does not publish its API terms or the OpenAPI specification; access runs through a camLine project or support. LineWorks modules are licensed separately, so the tool list can only cover modules you run. Check the interface licence with camLine before the build.
No. Each call runs under the asking person's LineWorks identity, so LineWorks' own permission check decides every answer. Two users asking the same question can get two different answers, and that is tested before go-live.
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 camLine LineWorks administrator in the room if you like.