For maintenance teams running HxGN EAM on their own server

An HxGN EAM API and MCP server that reads work order grids and comments on the customer's own server

Pexon builds an HxGN EAM API connector so Claude, ChatGPT or Copilot can read grids and comments on the customer's own server. The November 2025 guide names the grid path, the CSV grid path and Work Order Comments. No MCP server is named there. The product page read on 22 November 2026 calls it Octave Attune EAM, formerly HxGN EAM.

HxGN EAMquery_alert_gridread_grid_csvlist_work_order_commentsAgentruns as theperson asking

What we build

A first HxGN EAM tool list, written as the manifest your IT team signs

Built on what Hexagon documents: alert grid rows, grid rows as CSV, with column labels, work order comments, part comments, asset comments, purchase order comments. 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.

# hxgn-eam-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
  query_alert_grid:             # alert grid BSALRT, filter -> alert rows
    backend: POST /axis/restservices/grids
    mode: read
  read_grid_csv:                # grid request -> CSV rows, column labels and the next cursor
    backend: POST /axis/restservices/csvgrids
    mode: read
  list_work_order_comments:     # work order -> comment records
    backend: Work Order Comments GET Collection
    mode: read
  list_part_comments:           # part -> comment records
    backend: Part Comments GET Collection
    mode: read
  list_asset_comments:          # asset -> comment records
    backend: Asset Comments GET Collection
    mode: read
  list_purchase_order_comments: # purchase order -> comment records
    backend: Purchase Order Comment GET Collection
    mode: read
audit: every call logged with user, tool, arguments and the HxGN EAM 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.

Checked 22 November 2026

HxGN EAM at a glance: interfaces, access and what exists for AI

What we found
InterfacesHxGN EAM Rest Web Services (REST/JSON, docs public)
AuthenticationThe 12.3 guide says the swagger Authorize step takes the person's username and password, an API key, or a bearer token for OIDC. Every call sends tenant, Role and Organization. The user record needs the Connector checkbox, and the user group needs Query on that web service. The connector calls the customer's own server as the person who asked.
Vendor MCP serverNo vendor server. The version 12.3 Rest Web Services guide, read on 22 November 2026, does not name an MCP server. A GitHub search that day for a repository named hxgn eam mcp returned none. Makini publishes its own page. That is not Hexagon's.
Vendor AI assistantThe Octave Attune page opened on 22 November 2026 describes an AI assistant that guides users with prescriptive actions. It does not name an MCP server. The same page says Octave Attune EAM was formerly HxGN EAM.
Other connectorsMakini publishes a hosted MCP server page for HxGN EAM, read on 22 November 2026, and that page lists create and update actions. It is not a Hexagon server, and those writes are not this connector.

Hexagon (SE). Maintenance teams that keep work, equipment and materials in HxGN EAM on their own application server. The Rest Web Services guide, version 12.3, November 2025, is written for that administrator and gives no installed-base count. The product page opened on 22 November 2026 calls the product Octave Attune EAM and says it was formerly HxGN EAM. Hexagon AB's imprint, read the same day, is in Stockholm, organisation number 556190-4771. The guide prints a Hexagon PPM address in Madison, Alabama.

Why HxGN EAM is hard for agents

Where a HxGN EAM connection needs engineering, not configuration

01 · Identity

The call runs as the person who asked

The 12.3 guide requires the Connector checkbox on the EAM user, Query on that user group's Interface Permissions, and the headers tenant, Role and Organization. LGNCON is STD, LDAP or EXTERN and must line up with the other login parameters. EXTERN also uses the SSO Configuration screen. The connector does not keep a shared service login.

02 · Grid

The grid read is a POST, and the sample ids are a sample

The guide says POST /axis/restservices/grids is a get, used because the request has a body. Its sample is the alert grid, GRID_NAME BSALRT, GRID_ID 2489 and DATASPY_ID 2462. Those ids are that sample. CSV is POST /axis/restservices/csvgrids with the same body. An empty NEXTCURSORPOSITION means the rows are finished.

03 · Shape

Comments and other screens do not come back the same way

Comment GET collections return a COMMENT array and ignore RSCLROWS. The guide names Work Order Comments, Part Comments, Asset Comments and Purchase Order Comment among them. A screen such as Lot returns DATARECORD and is capped by RSCLROWS. The guide names RSCLROWS and does not print its number.

04 · Year

The year field changed shape in 12.3, and writes stay off

From EAM 12.3, RSYRYYYY sets the DATETIME year. NO, which is also the empty value, means epoch milliseconds. The guide's example is 1735669800000. YES means a 4-digit year. The guide's example is 2025. POST add, PUT, PATCH and DELETE are in the same guide and stay off the manifest.

HxGN EAM 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 alerts on the alert grid begin with this code?
  • What does this grid return, including the column labels?
  • What do the work order comments say?

What it will not do

  • Add a record, update a record, patch selected fields, or delete a record. Those actions are in the 12.3 guide and stay off the manifest.
  • Treat GRID_ID 2489 or DATASPY_ID 2462 as the id on every server. They are the alert-grid sample in that guide.
  • Read the customer's records from a public Hexagon host. The swagger host is the customer's own EAM application server.

When this is the wrong page

If the work orders are in IBM Maximo or IFS Ultimo, use that connector. HxGN EAM reads grids and comments on the customer's own REST web services. Adding or updating a record stays with the person in EAM. Makini publishes its own MCP server, and that is not this connector.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your HxGN EAM owners and checks every backend against your release and licence. Week two tests whether a person's own HxGN EAM 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 HxGN EAM 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: HxGN EAM Rest Web Services 12.3 · Hexagon AB imprint · Octave Attune EAM, formerly HxGN EAM · Makini HxGN EAM MCP server. Read 22 November 2026. Vendor documentation changes; verify against the current release.

Questions HxGN EAM teams ask before the first tool call

Does Hexagon ship an MCP server for HxGN EAM?

Not one named in the version 12.3 Rest Web Services guide, read on 22 November 2026. A GitHub search that day for a repository named hxgn eam mcp returned none. Makini publishes its own page and lists create and update actions. That page is not Hexagon's.

What can an assistant read from HxGN EAM?

Alert-grid rows through POST /axis/restservices/grids, the same grid as CSV through POST /axis/restservices/csvgrids, and the comment collections the guide names for work orders, parts, assets and purchase orders. Adding, updating and deleting records stay off the manifest.

Whose permission does the HxGN EAM connector use?

The customer's. The 12.3 guide says the Authorize step takes that person's username and password, an API key, or a bearer token for OIDC, and that every call sends tenant, Role and Organization. The user needs the Connector checkbox and Query on the web service.

What does an HxGN EAM connector cost?

The two-week Readiness Blueprint is fixed at €4,900: the tool list, the customer's swagger, identity tested end to end, and a costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.

Not a sales call. An architecture call.

Thirty minutes with the engineer who would build the connector, with your HxGN EAM administrator in the room if you like.

The connector catalogue lists this system next to Maximo and IFS Ultimo. Maximo is the other large EAM. Ultimo is the maintenance system when the jobs and spare parts live there instead.