For aerospace, energy and service companies running IFS Cloud
An IFS Cloud MCP server gives Claude or another agent named operations on work orders, fault reports, equipment and parts, built on the IFS Cloud OData projections with OAuth2 per person. As of 19 September 2026, IFS mentions MCP servers in a blog but documents no product. Pexon builds read and draft-only tools for service and MRO.
Before you wait for IFS
The question that decides it
Does the agent only ever need IFS Cloud, and has IFS named a server for your release with a date?
Checked 19 September 2026
| Option | What it is | What it is not |
|---|---|---|
| IFS, the vendor | A blog post of 24 November 2025 refers to "our Model Context Protocol (MCP) servers" | No product documentation, version or availability date that we could find |
| The IFS Cloud API | OData REST projections with OpenAPI v2/v3 export in the API Explorer; OAuth2 and OpenID Connect through IFS IAM | Not shaped for an agent: hundreds of projections, each with its own entity model |
| knakit/ifs-mcp-server-local | MIT-licensed personal project that builds tools from projection OpenAPI specs, with OAuth2 | In its own words "NOT tested in a production environment" |
| Other community servers | One reads work orders, fault reports and equipment over OData with client credentials; one analyses IFS source code | Maturity unknown; the second reads no runtime data at all |
| Makini | Hosted MCP server for IFS Ultimo, the separate mid-market EAM product | The page we read covers Ultimo, not IFS Cloud |
Vendors are shipping MCP servers month by month. This row set is a dated observation; the catalogue on the MCP connectors hub is where it is kept current.
Why IFS Cloud is hard for an agent
01 · Surface
IFS Cloud exposes its data through hundreds of projections, each with its own entities and actions. Pointing an agent at OData discovery hands it the whole surface and asks the model to pick. The server has to publish a curated handful of operations instead, each mapped to the projection a planner would actually use.
02 · Identity
IFS grants projections through permission sets per user. A server running on client credentials sees what its technical user sees, and that is rarely what a given planner may see. The agent has to call IFS with the person's OAuth2 token so that IFS, not the server, decides what comes back.
03 · Releases
IFS Cloud ships named releases such as 25R1, 25R2 and 26R1, and projection versions and customisations differ between them. A tool that worked on one release can return a different shape on the next, so each tool needs a contract test that runs against your instance before an upgrade goes live.
04 · Sign-off
In MRO the release to service is signed by certifying staff, and in A&D some data is segregated for export control. An agent may read history and draft; it may not sign, close or release. That has to be a property of the tool list, not a sentence in a prompt.
A realistic first tool list
What we build, and how to start
The server runs next to your IFS Cloud instance, in your cloud tenant or your data centre, and is your code in your repository. It authenticates each person through IFS IAM, publishes only the operations agreed with your planners and the owners of the permission sets, and logs every call with the person and the projection it touched. The identity exchange and the audit trail are built once; the next system, SAP or a PLM, reuses them. IFS's own public service reference is Rolls-Royce Power Systems, which chose IFS Cloud in October 2024 for global service operations: 1,000 users, 1,200 locations, 175 countries. At that scale no dispatcher sees everything, and named operations matter more than a clever prompt.
We have not built an IFS connector for a named customer, so the first step is finding out whether yours can be built the way this page describes. The Readiness Blueprint does exactly that in two weeks at a fixed €4,900: one use case, the agreed tool list, a test of per-person OAuth2 against your permission sets, and a costed build plan you keep whoever builds it. All prices are net and exclude VAT.
Not as a documented product, as of 19 September 2026. An IFS blog post from 24 November 2025 refers to "our Model Context Protocol (MCP) servers", but we found no product documentation, version or availability date a customer could deploy. If IFS publishes one for your release, use it for questions that stay inside IFS. It will not reach your PLM, your historian or SAP, and an agent in service or MRO usually needs at least one of them.
No, and we will not build a tool that does. In aviation maintenance, the release is signed by certifying staff, and the tool list reflects that: the agent reads fault history, maintenance records and parts availability, and drafts. A person confirms every change in IFS itself, under their own name. The same rule holds outside aviation: no tool on the server writes to IFS without a person completing the step in the application.
Usually not, and it should not have one. IFS Cloud exposes its projections through OAuth2 via IFS Identity and Access Manager, so the server can act on the signed-in person's token and IFS applies that person's permission sets. A client-credentials user is quicker to set up and is exactly what a security review should reject for an agent that reads across departments. Whether API access carries its own licence terms is a question for IFS; check with them.
The two-week Readiness Blueprint is fixed at €4,900: one IFS Cloud use case, an agreed tool list, a test of whether per-person OAuth2 carries through your permission sets, and a costed build plan. A first production server is typically a use-case pilot from €15,000. Model usage is billed by Anthropic or your cloud provider at their rates. All prices are net and exclude VAT.
Partly. Ultimo is a separate IFS product with its own REST API, authenticated by an API key that is bound to one system user, so per-person permissions need an extra layer in the server. Makini already offers a hosted Ultimo MCP server with generic search, get, create and update tools and a self-hosted option. If generic tools are enough for your use case, compare that first; we build when the tool list has to follow your maintenance process.
Next step
Thirty minutes with the engineer who would build the server: your IFS Cloud release, the question your planners ask most, and whether per-person OAuth2 is realistic in your tenant.