For Mittelstand manufacturers running FASTEC 4 PRO

A read-only FASTEC 4 PRO MCP server for OEE, downtimes and order progress, scoped to each user's role

A FASTEC 4 PRO MCP server gives Claude, ChatGPT or Copilot read tools for OEE, downtimes, order progress and open maintenance. FASTEC publishes no API reference; the BI-Connector database views are the read source. FASTEC ships no MCP server as of 21 September 2026, so Pexon builds one on your local network.

Why FASTEC 4 PRO is hard for agents

Where a FASTEC 4 PRO connection needs engineering, not configuration

01 · Docs

No public API reference

FASTEC does not publish a REST API reference. The interface scope is agreed per project with FASTEC, so every tool backend is confirmed against your installation before it is built.

02 · Interfaces

Built for files, not questions

Most FASTEC integrations exchange files, XML or database tables with an ERP. An agent needs request and response, so the connector reads from the BI-Connector views instead of the ERP interface.

03 · OPC UA

The OPC UA server holds KPIs only

The integrated OPC UA server exists from version 3.4.4 and exposes calculated data points such as OEE and MTBF. Orders and bookings are not on it, so it cannot be the only source.

04 · Network

The server runs in your plant

FASTEC 4 PRO typically runs on premises. The MCP server has to run on the local network, and an assistant in the cloud reaches it only through a gateway your IT team approves.

Checked 21 September 2026

FASTEC 4 PRO at a glance: interfaces, access and what exists for AI

	What we found
Interfaces	FASTEC 4 PRO BI-Connector (database views, docs not published): star and snowflake evaluation model with sample DAX and SQL for OEE and downtime, built for Power BI, QlikView and Databricks · Integrated OPC UA server (OPC UA, docs not published): from version 3.4.4; exposes calculated data points such as OEE and MTBF, not orders or bookings · ERP interfaces (file, XML, CSV, database tables, REST, docs not published): FASTEC standard interface or agreed per project; no public API reference
Authentication	Not documented publicly. The read access for the BI-Connector views is set up in the blueprint with your database team.
Vendor MCP server	No vendor server. No FASTEC MCP server, AI assistant or LLM integration found on fastec.de or in the MCP directories.
Vendor AI assistant	None found.
Other connectors	None found.

FASTEC GmbH (DE). German Mittelstand manufacturers, from automotive suppliers to food, pharma and plastics, using it for shop-floor and machine data collection, OEE, planning, quality and traceability; FASTEC states over 400 customers.

What we build

A first FASTEC 4 PRO tool list, written as the manifest your IT team signs

Built on what FASTEC GmbH documents: production orders, machine states and downtimes, OEE, MTBF and other KPIs, operating data bookings, quality inspections, traceability records, maintenance orders, personnel planning. 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.

# fastec-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_oee:               # machine or group, date range -> OEE with availability, performance, quality
    backend: BI-Connector views, confirmed in blueprint
    mode: read
  list_downtimes:        # machine, date range -> downtime periods with reason
    backend: BI-Connector views, confirmed in blueprint
    mode: read
  get_order_progress:    # order number -> status, quantities, remaining time
    backend: confirmed in blueprint
    mode: read
  list_open_maintenance: # machine -> open maintenance orders
    backend: confirmed in blueprint
    mode: read
audit: every call logged with user, tool, arguments and the FASTEC 4 PRO response

The manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.

FASTEC 4 PRO 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

What was OEE for the injection moulding machine group last week, and which downtime reasons dominated?
Which production orders are behind schedule today?
Which maintenance orders are open for machine 12?

What it will not do

Write to FASTEC 4 PRO: the connector is read-only, and bookings stay with the terminals and people on the shop floor.
Read more than the asking user may read; access is scoped per role and tested with two users before go-live.
Touch machine control: the connector reads evaluated data and never writes to PLCs or the OPC UA server.

When this is the wrong page

If the question is a fixed OEE dashboard across all plants, the BI-Connector into Power BI or Databricks answers it without an agent. A connector is right when people ask ad hoc questions from Claude, ChatGPT or Copilot, or need FASTEC data next to ERP data.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your FASTEC 4 PRO owners and checks every backend against your release and licence. Week two tests whether a person's own FASTEC 4 PRO 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 FASTEC 4 PRO 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.

Sources: FASTEC 4 PRO · FASTEC data connections · FASTEC OPC UA interface · FASTEC BI-Connector. Read 21 September 2026. Vendor documentation changes; verify against the current release.

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 FASTEC 4 PRO teams ask before the first tool call

Does FASTEC 4 PRO have its own MCP server?

Not as of 21 September 2026. FASTEC offers no MCP server, AI assistant or LLM integration on fastec.de. An MCP server for Claude, ChatGPT or Copilot has to be built against the interfaces your installation has, usually the BI-Connector views.

Do we need extra FASTEC licences or access for an AI connector?

FASTEC does not publish its licence terms for the BI-Connector or the OPC UA server, and the OPC UA server needs version 3.4.4 or later. Check with FASTEC which of the two your licence includes. The blueprint settles it before any tool is built.

Can the assistant see data a user is not allowed to see in FASTEC?

No. The BI-Connector views are read under a role-scoped account, and each person is mapped to the scope their role allows. Two users asking the same question can get two different answers, and that is tested before go-live.

What does a FASTEC 4 PRO 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 FASTEC 4 PRO administrator in the room if you like.