For quality teams running iqs CAQ, now PeakAvenue Quality Center
An iqs CAQ MCP server gives Claude, ChatGPT or Copilot read-only tools for complaints, overdue actions, supplier ratings and gauges in Quality Center, now sold by PeakAvenue. PeakAvenue publishes no API reference, so every backend is confirmed against your installation. No MCP server exists as of 21 September 2026.
Why iqs CAQ is hard for agents
01 · Docs
PeakAvenue publishes no API documentation for Quality Center, and interfaces are configured by the vendor per customer. Every backend is confirmed against your installation, with PeakAvenue, before a tool is written.
02 · Transition
iqs is now a brand inside PeakAvenue, which is moving towards an AWS-hosted eQMS. The on-premises Quality Center and the cloud eQMS may expose different interfaces, so the blueprint pins which one your connector uses.
03 · Database
All modules share one central database, which makes direct database reads tempting. They bypass Quality Center's permissions and break on upgrades, so the connector does not use them as the route for user questions.
04 · Measurement
Measuring-device and Q-DAS data flows work at file and device level, not as business objects. Questions on raw measurements need a different route than questions on complaints or supplier ratings.
Checked 21 September 2026
| What we found | |
|---|---|
| Interfaces | Quality Center interfaces (not published, docs not published): vendor lists interfaces to PPS/ERP, BDE, SAP, CAD, Q-DAS and measuring devices; all modules share one central database, and the interface specifications are not public · PeakAvenue eQMS open APIs (not published, docs not published): PeakAvenue names open APIs for ERP, PLM, MES and BI systems for its AWS-hosted cloud eQMS; no public reference |
| Authentication | Not documented publicly. |
| Vendor MCP server | No vendor server. No MCP server or external AI connector from PeakAvenue or iqs found. |
| Vendor AI assistant | PeakAvenue markets AI for language, search and analytics in its cloud eQMS, such as requirements management and a DMS with integrated AI; no named AI feature for Quality Center was found. |
| Other connectors | None found. |
PeakAvenue GmbH, formerly iqs Software GmbH (DE). Quality departments at automotive suppliers, electronics, medical technology and aerospace manufacturers working to ISO 9001, VDA 6, IATF 16949 and AIAG; the product is now sold as Quality Center by PeakAvenue, alongside APIS, PLATO, Isograph and OSSENO.
What we build
PeakAvenue GmbH, formerly iqs Software GmbH does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.
# iqs-caq-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
list_open_complaints: # supplier or customer, age -> complaints with 8D stage
backend: confirmed in blueprint
mode: read
list_overdue_actions: # owner or department -> overdue measures
backend: confirmed in blueprint
mode: read
get_supplier_evaluation: # supplier -> evaluation scores over time
backend: confirmed in blueprint
mode: read
get_inspection_results: # part, supplier, period -> incoming inspection lots and decisions
backend: confirmed in blueprint
mode: read
list_due_gauges: # plant, date -> gauges due for calibration
backend: confirmed in blueprint
mode: read
audit: every call logged with user, tool, arguments and the iqs CAQ 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.
iqs CAQ 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 are moving to PeakAvenue's cloud eQMS anyway, ask PeakAvenue about its APIs and AI features first; a connector to a system you are leaving is money spent twice. For quality KPIs over years, a data warehouse is the better home than per-question calls.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your iqs CAQ owners and checks every backend against your release and licence. Week two tests whether a person's own iqs CAQ 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 iqs CAQ 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. Neither PeakAvenue nor the former iqs Software has published an MCP server or an external AI connector. PeakAvenue's AI features sit in its cloud eQMS, not in Quality Center.
PeakAvenue publishes no API for Quality Center and no licence terms for one; interfaces are configured per customer. Ask PeakAvenue which interface your installation can offer, and whether your roadmap moves to the cloud eQMS.
No. Each call runs as the asking person, so Quality Center's own permissions decide every answer, and the connector never reads the shared database behind them. 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 iqs CAQ administrator in the room if you like.