01 · Payload
HAL responses are deep and chatty
FORCE Bridge nests data in _embedded and _links. A tool that passes that through burns tokens and round trips, so each tool flattens the response and follows only the links the question needs.
For manufacturers running FORCAM FORCE MES
A FORCAM MCP server that reads operations, OEE and tickets from the FORCE Bridge API, scoped per role
A FORCAM MCP server gives Claude, ChatGPT or Copilot named tools for operations, downtime hit lists, OEE and tickets. FORCAM documents the FORCE Bridge REST API in public on SwaggerHub, with OAuth 2.0 client credentials. FORCAM ENISCO ships no MCP server as of 21 September 2026, so Pexon builds one against your release.
What we build
A first FORCAM FORCE tool list, written as the manifest your IT team signs
Built on what FORCAM ENISCO documents: production orders, operations with quantity summary and scheduled dates, workplaces and workplace groups, operating states and downtime hit lists, OEE and OPE reports, quality details, tickets with activities, tools, materials and documents. 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.
# forcam-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
search_operations: # workplace or order, phase -> operations with scheduled dates and quantity summary
backend: POST /operations/search, GET /operations/{operationId}/quantitySummary
mode: read
get_downtime_hitlist: # workplace or group, date range -> operating states ranked by duration
backend: GET /reports/hitListOperatingStatesWorkplace
mode: read
get_oee: # workplace, date range -> OEE with availability, performance, quality
backend: GET /reports/overallEquipmentEfficiency
mode: read
get_production_order: # order id -> operation sequence, scheduled dates, specification
backend: GET /productionOrders/{productionOrderId}/operationSequence
mode: read
list_tickets: # workplace, state -> tickets with activities
backend: GET /tickets, GET /tickets/{ticketId}/activities
mode: read
draft_ticket: # workplace, description, class -> ticket draft, created only after a person confirms
backend: POST /tickets
mode: propose
audit: every call logged with user, tool, arguments and the FORCAM FORCE 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 21 September 2026
FORCAM FORCE at a glance: interfaces, access and what exists for AI
| What we found | |
|---|---|
| Interfaces | FORCE Bridge API v4 (REST/JSON, docs public): OpenAPI on SwaggerHub, base path /ffwebservices/api/v4, HAL hypermedia responses; v2 to v4 published, full PDF in the customer portal · FORCE Bridge callbacks and events (REST/JSON, docs public): /callbacks and /events resources for push notifications · FORCAM FORCE Bridge connector for Microsoft Power Platform (REST/JSON, docs public): preview, published by FORCAM; API key per instance, 100 calls per 60 seconds per connection |
| Authentication | OAuth 2.0 client credentials flow; the access token is sent as a Bearer header and refreshed before it expires. The Power Platform connector uses an API key per FORCE Bridge instance. |
| Vendor MCP server | No vendor server. No FORCAM ENISCO MCP server found; the vendor's AI agent ENI.one targets SAP Digital Manufacturing, not FORCE Bridge. |
| Vendor AI assistant | ENI.one, a voice-controlled AI agent embedded in SAP Digital Manufacturing, starts and stops orders and reports quantities by voice. |
| Other connectors | FORCAM publishes a FORCE Bridge connector for Microsoft Power Platform (preview) with about 30 actions, usable from Copilot Studio; it is a low-code connector, not an MCP server. |
FORCAM ENISCO (DE). Large and mid-sized discrete manufacturers in automotive, aerospace and machinery; named references include Audi, BMW, Schaeffler, Airbus and voestalpine.
Why FORCAM FORCE is hard for agents
Where a FORCAM FORCE connection needs engineering, not configuration
02 · Versions
Three API versions coexist
FORCAM publishes v2, v3 and v4 of the API. Your installed FORCE release decides which paths exist, so the tool list is pinned to your release and checked against it in the blueprint.
03 · Custom fields
Every plant extends the objects
Orders, operations, workplaces and staff carry customer-specific custom fields. Those fields need a mapping per plant, or the assistant sees names that mean nothing outside your MES team.
04 · Identity
The token belongs to a client, not a person
FORCE Bridge authenticates an OAuth client, not the user asking. Staff attendance and login periods are personal data under works-council rules, so OAuth clients are scoped per role and the connector decides which client a person may use.
FORCAM FORCE 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
- Which operations are in progress on workplace group Pressing, and what is their quantity status?
- What were the top downtime reasons on machine 4711 last week?
- What was OEE for line 2 yesterday, and which tickets are open for that line?
What it will not do
- Start, stop or book anything by itself: the only write tool drafts a ticket and a person confirms it before it is created.
- Read more than the asking user may read; each person is mapped to a scoped OAuth client, and staff attendance data stays out unless that scope is agreed.
- Replace reporting: long OEE trends across all plants belong in a data warehouse, not in per-question API calls.
When this is the wrong page
If your people already work in Copilot Studio and a handful of actions are enough, FORCAM's own Power Platform connector is the shorter path. If you run SAP Digital Manufacturing and want voice control on the line, look at ENI.one; a connector is right for Claude, ChatGPT or Copilot across FORCE and other systems.
Start with the Readiness Blueprint.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your FORCAM FORCE owners and checks every backend against your release and licence. Week two tests whether a person's own FORCAM FORCE 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 FORCAM FORCE 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.
Related
- 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 FORCAM FORCE teams ask before the first tool call
Does FORCAM have its own MCP server?
Not as of 21 September 2026. FORCAM publishes a Power Platform connector for FORCE Bridge in preview, and its AI agent ENI.one runs inside SAP Digital Manufacturing. An MCP server for Claude, ChatGPT or Copilot has to be built against the FORCE Bridge API.
Do we need extra FORCAM licences or access for an AI connector?
The connector needs an OAuth client on your FORCE Bridge instance; the API reference itself is public on SwaggerHub. FORCAM does not publish whether extra API clients are licensed separately, so check that with FORCAM ENISCO before the build.
Can the assistant see data a user is not allowed to see in FORCAM?
No. FORCE Bridge authenticates an OAuth client rather than a person, so each user is mapped to a client scoped to their role before any call is made. Staff attendance and login data stay out unless that scope is agreed, and the mapping is tested before go-live.
What does a FORCAM 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 FORCAM FORCE administrator in the room if you like.