MCP connectors for the systems your vendor will not build one for

Because their vendors mostly will not. Of the 50 regional ERP, MES, quality and utility systems in this catalogue, one ships a generally available MCP server on live data as of 21 September 2026. Most have a documented API or web services, often behind a partner login, and a small engineering team with other priorities. That is the gap a custom connector fills.

It is a small service that publishes a fixed list of named operations against one system, such as get_bom, where_used or read_tag_history, so an assistant like Claude can call them instead of receiving database access. The Model Context Protocol standardises the shape, so the same server works with any client that speaks it. The engineering is in which operations exist, whose identity they run under, and what is logged.

Wait if the announcement names your product, your version and a date, and if you only need that one system. Build if the agent has to combine systems, for example a BOM from Windchill against the material master in SAP, because no vendor server crosses its own product boundary. Several vendor servers we checked also ship write and configuration tools, some enabled by default, so even the vendor's server usually needs a restricted deployment.

No. The table is a map of where each vendor stands and which interface a server is built against, not a product list. We build per engagement, against your instance, with your permission model. The systems that have their own page are the ones where we have written up the integration surface, the hard parts and a realistic first tool list.

We design for read-only on anything that controls a process, and for proposal-only on validated systems such as pharma MES and LIMS, where a human signs. Writes go into systems of record like ERP or maintenance only through the application's own logic, one named operation at a time, with the person's identity attached. That rule costs some convenience and removes the question a safety review would otherwise stop the project on.

The two-week Readiness Blueprint is fixed at €4,900: one system, an agreed tool list, a test of whether the identity model carries through, and a costed build plan. A first production connector is usually a use-case pilot from €15,000. All prices are net and exclude VAT.