For quality teams running ZEISS PiWeb on their own server
Pexon builds a ZEISS PiWeb API connector so Claude, ChatGPT or Copilot can read inspection plans, measurements and measured values from the customer's own PiWeb Server. The interface is the public DataService REST API. ZEISS publishes no PiWeb MCP server as of 24 October 2026.
What we build
Built on what ZEISS documents: inspection-plan parts, characteristics, measurements, measured values, attribute configuration, raw data files. 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.
# zeiss-piweb-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_service_information: # -> server name, version and whether security is enabled
backend: GET /dataServiceRest/serviceInformation
mode: read
get_configuration: # -> attribute definitions for this PiWeb Server
backend: GET /dataServiceRest/configuration
mode: read
list_parts: # part path -> parts in the inspection plan
backend: GET /dataServiceRest/parts
mode: read
list_characteristics: # part path -> characteristics under that part
backend: GET /dataServiceRest/characteristics
mode: read
list_measurements: # part uuid -> measurements
backend: GET /dataServiceRest/measurements
mode: read
list_measured_values: # part uuid, characteristic uuid -> measured values
backend: GET /dataServiceRest/values
mode: read
audit: every call logged with user, tool, arguments and the ZEISS PiWeb 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.
Checked 24 October 2026
| What we found | |
|---|---|
| Interfaces | DataService REST (REST/JSON, docs public) · RawDataService REST (REST/JSON, docs public) |
| Authentication | Whatever this PiWeb Server requires: HTTP Basic, Windows authentication, a client certificate, or an OpenID Connect bearer token from GET /oAuthServiceRest/oAuthConfiguration. serviceInformation.securityEnabled says whether authentication is required. A refused permission is HTTP 403. |
| Vendor MCP server | No vendor server. No PiWeb MCP server is named on the ZEISS PiWeb product page, the PiWeb API docs, or the ZEISS-PiWeb/PiWeb-Api repository, read 24 October 2026. A search that day for a PiWeb MCP server did not return one from ZEISS. |
| Vendor AI assistant | None found. |
| Other connectors | None found. |
ZEISS (DE). Quality teams that keep inspection results in ZEISS PiWeb. ZEISS describes it as reporting and quality data management for tactile, optical, manual or CT measurements, and describes PiWeb Server as the module that hosts an open API and controls access. No installed-base figure was on the pages read for this record.
Why ZEISS PiWeb is hard for agents
01 · Network
DataService and RawDataService are served by the customer's PiWeb Server, at /DataServiceRest and /RawDataServiceRest. The instance name and HTTPS depend on that server's settings. The connector runs in the network that can already reach it.
02 · Identity
ZEISS documents Basic, Windows, certificate and OpenID Connect authentication, and says PiWeb Planner is where roles and user privileges are defined. securityEnabled reports whether this server requires a login. A connector that signs in as one shared account answers with that account's rights.
03 · Keys
The public README shows an example configuration where key 1001 is part number and key 1 is the measured value. Those are example labels. The tool list reads GET /dataServiceRest/configuration on the installed server before it treats a key as a meaning.
04 · Writes
The DataService and RawDataService docs include create, update and delete next to the reads. Those operations stay off the manifest. ZEISS describes PiWeb Essential as on-premise with a 10 GB database and PiWeb Enterprise as unlimited storage, so which edition is installed is checked in the blueprint.
One interface per row
01
REST/JSON. Documentation is public. served by the customer's PiWeb Server at /DataServiceRest; the 1.12.0 docs page was the newest that resolved on 24 October 2026, and the server reports its own supported versions from GET /dataServiceRest/
02
REST/JSON. Documentation is public. same server, at /RawDataServiceRest, for raw files attached to a part or other entity; the 1.8.0 docs page was read on 24 October 2026
ZEISS PiWeb 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 the quality system is BabtecQ or iqs CAQ, use that connector. PiWeb holds inspection plans, measurements and measured values on the customer's PiWeb Server, not a complaint or audit workflow. A PiWeb MCP server from ZEISS was not found on 24 October 2026; if one appears, this page is the restriction and identity work, not a second writer.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your ZEISS PiWeb owners and checks every backend against your release and licence. Week two tests whether a person's own ZEISS PiWeb 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 ZEISS PiWeb 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 one that was named on the PiWeb product page, the PiWeb API documentation, or the ZEISS-PiWeb/PiWeb-Api repository on 24 October 2026. A search that day for a PiWeb MCP server did not return one from ZEISS.
Parts and characteristics in the inspection plan, measurements, and measured values, through DataService REST on your PiWeb Server. Create, update and delete exist in the same docs and stay off the tool list.
The call uses that person's login. ZEISS documents Basic, Windows, certificate and OpenID Connect authentication, and a refused permission comes back as HTTP 403. A shared PiWeb account would answer with the shared account's rights, which is why the connector does not use one.
The two-week Readiness Blueprint is fixed at €4,900: the tool list, the installed DataService version checked against your PiWeb Server, identity tested end to end, and a 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 ZEISS PiWeb administrator in the room if you like.