For maintenance teams running IFS Ultimo
An IFS Ultimo MCP server gives Claude, ChatGPT or Copilot named tools for jobs, assets, failure history and spare parts, built on the public Ultimo REST API with API keys scoped per role. IFS ships no Ultimo MCP server as of 21 September 2026, so Pexon builds one against your installation.
What we build
Built on what Ultimo Software Solutions, an IFS company documents: jobs (work orders), incl. technical service and IT incidents, equipment and assets, articles (spare parts) and article suppliers, departments, cost centres, employees, suppliers, service contracts, reservations, IoT measurements. 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.
# ultimo-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_jobs: # equipment, status, target date range -> jobs with priority and progress status
backend: GET /api/v1/object/Job with filter and expand=Equipment
mode: read
get_equipment: # equipment id or ExternalId -> asset with spare parts and vendor
backend: GET /api/v1/object/Equipment('id') with expand=SpareParts,Vendor
mode: read
get_failure_history: # equipment id, period -> finished jobs with fail type and feedback text
backend: GET /api/v1/object/Job with filter on Equipment/Id
mode: read
search_articles: # description or id -> spare parts with purchase price and suppliers
backend: GET /api/v1/object/Article with filter on Description
mode: read
propose_job_status_change: # job, new progress status, remark -> draft for a technician to confirm
backend: POST change-job-status workflow, after confirmation
mode: propose
audit: every call logged with user, tool, arguments and the IFS Ultimo 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
| What we found | |
|---|---|
| Interfaces | Ultimo REST API v1 (REST/JSON, docs public): OData-style filter, orderby, expand and select on /api/v1/object/<Entity>; reads since 18.04 in all editions, inserts and updates only for cloud customers on Azure · REST workflow actions (REST/JSON, docs public): configured workflows triggered by POST, such as changing a job status; customer-specific workflows need Premium or Enterprise · BI Platform (database, docs public): read access to the Ultimo cloud database through a customer-created database user and BI views; Premium and Enterprise |
| Authentication | An API key secret in the ApiKey HTTP header; keys are created in the Ultimo Configuration Tool and expose only the entities and properties configured on them. On Azure cloud, a key can be bound to an IP allow-list and a client certificate. |
| Vendor MCP server | No vendor server. No Ultimo MCP server from IFS; IFS writes about its MCP servers for IFS Cloud without mentioning Ultimo, and the commercial Makini service lists Ultimo in its hosted MCP catalogue. |
| Vendor AI assistant | Ultimo has embedded AI for failure-report suggestions, assisted troubleshooting, work instructions, photo meter readings and HSE measures, plus digital workers for planners, technicians and HSE in Microsoft Teams, announced June 2026. |
| Other connectors | Makini offers a commercial hosted MCP server that lists IFS Ultimo among 2,000+ products; its Ultimo-specific depth is not verified. |
Ultimo Software Solutions, an IFS company (NL). Maintenance, technical service, HSE and facility teams in manufacturing, logistics, healthcare and fleet operations; IFS states more than 2,300 customers in over 40 countries.
Why IFS Ultimo is hard for agents
01 · Quotas
Ultimo allows 10,000 requests per day and 100 requests per 10 seconds across all API keys. An agent running broad searches can starve your production interfaces, so the connector's key gets its own daily quota and the tools filter narrowly.
02 · Identity
Ultimo authenticates API keys, not people. Each key sees only the entities and properties configured on it, so the key design per role is the real permission model and has to be built per use case, then mapped to the signed-in user.
03 · Writes
Inserts and updates through REST work only for cloud customers on Azure; on-premises installations are read-only through REST. Customer-specific workflows need Premium or Enterprise, which decides whether a write tool exists at all.
04 · Codes
Context and status codes are numeric and configured per customer; Job Context 1, for example, means technical service. The connector carries a mapping table from your configuration, or the assistant reads the wrong jobs.
IFS Ultimo 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 technicians and planners work in Ultimo and Microsoft Teams, Ultimo's embedded AI and digital workers are the shorter path, and IFS maintains them. A connector is right when the assistant lives in Claude, ChatGPT or Copilot, or has to combine maintenance data with ERP or OT data.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your IFS Ultimo owners and checks every backend against your release and licence. Week two tests whether a person's own IFS Ultimo 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 IFS Ultimo 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. IFS writes about MCP servers for IFS Cloud without mentioning Ultimo, and Ultimo's own AI runs inside the product and in Microsoft Teams. The commercial Makini service lists Ultimo in a hosted MCP catalogue, with Ultimo-specific depth unverified.
Reading through the REST API is available in all editions. Inserts and updates work only for cloud customers on Azure, and customer-specific workflows need Premium or Enterprise. The blueprint starts read-only and adds a write tool only if your edition allows it.
No. Ultimo API keys expose only the entities and properties configured on them, so each role gets its own key and the connector maps the signed-in person to that role. Two users asking the same question can get two different answers, and that is tested before go-live.
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 IFS Ultimo administrator in the room if you like.