For UK manufacturers running EFACS E/8
An EFACS MCP server gives Claude, ChatGPT or Copilot named tools for works orders, engineering changes, contracts and field service jobs in EFACS E/8. Exel publishes no API documentation; the interface is clarified with Exel through the customer portal first. Exel ships no MCP server as of 21 September 2026, so Pexon builds one against your installation.
Why EFACS is hard for agents
01 · Documentation
Exel publishes no API reference, protocol or authentication description. Scope has to be clarified with Exel or through the customer portal before any estimate, which is why the blueprint starts there.
02 · Network
EFACS runs mostly on-premise or Exel-hosted for a single customer. Network access to your EFACS server has to be arranged for your installation, and that is a firewall decision your IT team owns.
03 · Configuration
Configurator, contract control and workflows are set up per customer. Mapping questions such as 'which works orders are late on contract C' to records is installation-specific work, done with your EFACS owners.
04 · Ecosystem
Exel is a small independent vendor based in Nottingham since 1985. No community libraries or connectors were found, so there is no existing code to start from; everything is built and tested against your system.
Checked 21 September 2026
| What we found | |
|---|---|
| Interfaces | EFACS E/8 integration interfaces (not published, docs behind customer or partner login) · Power BI and BIRT dashboards (Version 6) (database (reporting), docs not published) |
| Authentication | Not documented publicly. |
| Vendor MCP server | No vendor server. No EFACS MCP server, agent API or LLM assistant on exel.co.uk. |
| Vendor AI assistant | Exel markets EFACS as AI-enabled for purchase invoice capture, using Google Document AI Invoice Parser with OCR, and for workflow automation; there is no assistant. |
| Other connectors | None found. |
Exel Computer Systems plc (UK). UK discrete manufacturers in aerospace, automotive, electronics, engineering and food and beverage, and field service providers, running make-to-order and engineer-to-order work.
What we build
Exel Computer Systems plc does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.
# efacs-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_works_orders: # status, due date, contract -> works orders with progress
backend: confirmed in blueprint
mode: read
get_part_changes: # part number -> open change control records
backend: confirmed in blueprint
mode: read
get_contract_status: # contract -> cost, progress and open orders
backend: confirmed in blueprint
mode: read
list_field_service_jobs: # customer, date range -> open jobs and engineers
backend: confirmed in blueprint
mode: read
draft_sales_order: # customer, items -> sales order proposal for a person to confirm
backend: confirmed in blueprint
mode: propose
audit: every call logged with user, tool, arguments and the EFACS 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.
One interface per row
01
not published. Documentation is behind customer or partner login. Exel only says EFACS communicates with other systems via 'industry standard protocols'; technical material sits in the Exel customer and partner portals
02
database (reporting). Documentation is not published. Version 6 ships Power BI and BIRT dashboards; how they access EFACS data is not documented publicly
EFACS 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 need is dashboards and KPIs, the Power BI and BIRT dashboards in EFACS Version 6 are the shorter path, and cross-year analysis belongs in a data warehouse. A connector is right when people ask questions in Claude, ChatGPT or Copilot, or need EFACS combined with another system.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your EFACS owners and checks every backend against your release and licence. Week two tests whether a person's own EFACS 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 EFACS 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. Exel markets EFACS as AI-enabled for purchase invoice capture and workflow automation, but offers no MCP server, agent API or assistant. An MCP server for Claude, ChatGPT or Copilot has to be built on the interfaces Exel supports for your installation.
Exel does not publish its integration interfaces, their authentication or their licensing. We need that material through you, from the Exel customer portal or from Exel directly, and the licence question is one to check with Exel. The blueprint answers both before any build starts.
No. How each person's EFACS rights carry through the interface is tested in the blueprint, and no tool goes live until two users asking the same question get the answers their own rights allow. Writes only happen as drafts a person confirms in EFACS.
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 EFACS administrator in the room if you like.