Is there an MCP server for EROAD?

Is there an MCP server for EROAD?

Yes. Atso has an EROAD connector, so Claude can read your EROAD fleet data directly. You connect EROAD once, and then you ask questions in plain language.

Atso is one MCP connection that lets the AI chats your team already uses read your business software, across every account and organisation you own, with control over who can see what. MCP is the Model Context Protocol, an open standard for connecting AI assistants to outside tools and data. Atso is a remote MCP server, so there is nothing to install. The same connection that reads EROAD also reads your other connected software, such as Xero, Shopify, Unleashed or Google Search Console.

The EROAD connector is read-only. It can look at your fleet. It cannot change anything in EROAD.

What is EROAD?

EROAD is a fleet telematics platform used in New Zealand, Australia and North America. A device in each vehicle reports its position, speed, distance and engine data to EROAD. Fleet managers then use MyEROAD, the web application, to see their vehicles, drivers and sites.

EROAD also has a REST API. EROAD’s own developer pages say the API lets a business connect EROAD data to transport management, payroll or other business software. That API is what Atso reads. EROAD publishes separate API base paths for New Zealand (api.apac.eroad.com), Australia (api.au.eroad.com) and North America (api.na.eroad.com).

What can an AI assistant tell you about your fleet?

It can answer questions about where your vehicles are now, who is driving them, how many hours each driver has left, and which vehicles entered or left a site. Here are questions the connector can answer:

• “Give me a snapshot of the fleet right now. Which vehicles are moving, and which are parked with the ignition off?”
• “Which drivers are close to their hours of service limit today?”
• “Were there any hours of service violations yesterday?”
• “Which vehicles entered or left the Penrose depot geofence yesterday, and at what time?”
• “Where was truck KTR419 on Tuesday afternoon?”
• “List every vehicle with its odometer reading, so I can plan the next service.”
• “Who is driving the vehicles in the Auckland fleet right now?”

The connector reads the current state of each vehicle: position, speed, heading, odometer, engine hours, ignition status and the current driver. It also reads the vehicle list, drivers, fleets, driver groups, geofences, geofence entry and exit events, hours of service (current state, daily summary and violations), duty status changes and home terminals.

The assistant does the work of combining these. You ask one question, and Claude reads the records it needs, then answers from them. You do not need a report that someone built in advance.

Why does Atso keep its own location history?

Because EROAD’s API only reports where a vehicle is now. There is no endpoint that returns where a vehicle was on Tuesday afternoon. Without a history, an assistant could answer “where is the truck?” but never “where was the truck?”.

So Atso builds the history itself. When an organisation connects EROAD, Atso starts to record the position of each vehicle every 5 minutes. It keeps those positions for 90 days. Older positions are deleted.

This has one clear limit. The history starts from the moment you connect. Atso cannot show where a vehicle was before the connection existed, because nobody recorded it. If you connect on a Monday, a question about the previous Friday has no answer. After 90 days, the history always covers the most recent 90 days.

Five minutes is a deliberate choice. EROAD asks integrators not to poll its API faster than once a minute. A position every 5 minutes is enough to answer “where was the truck that afternoon?” and stays well inside that request. It is not a turn-by-turn trace, so it will not show every corner a vehicle took.

How do you connect EROAD to Atso?

You create an API key in MyEROAD, then paste it into Atso. The whole process takes a few minutes.

1. Check your plan. EROAD’s developer pages say its APIs are available for customers on the Premium plan. If your plan does not include API access, the API key option will not appear.
2. Create the key as an administrator. A user with the Client Administrator role creates an API key in MyEROAD. EROAD is moving API setup into a part of MyEROAD called Integrations, so the exact menu differs between older and newer accounts. Copy the key and keep it somewhere safe.
3. Paste the key into Atso. Open the connectors page in Atso, choose EROAD and paste the key. Atso works out which EROAD region the key belongs to, so you do not need to choose one.

The key belongs to your organisation. Atso stores it on your behalf and uses it only to read. If you remove the key in MyEROAD, the connection stops.

What does it mean that Atso is read-only for EROAD?

It means every EROAD tool in Atso reads data and none of them writes. Claude cannot create a geofence, change a driver record or send a message to a vehicle through Atso.

EROAD’s API can do some of those things. The connector does not use those parts. A fleet system controls real vehicles and real drivers’ working records, so the useful part for an AI assistant is the answer, not the change.

If you need to change something, do it in MyEROAD as you do today. Then ask the assistant again, and it will read the new state.

What happened to eroadmcp.co.nz?

The standalone EROAD MCP product at eroadmcp.co.nz is being retired. Its job now sits inside Atso, next to the other connectors. If an old eroadmcp.co.nz link brought you to this page, that is the reason.

The old product connected one system, EROAD, to an AI chat. Atso connects EROAD and the rest of a business’s software through the same connection. That means one question can use fleet data and accounting data together, for example vehicle odometer readings next to the fuel and maintenance bills in Xero.

You can open Atso to connect EROAD and ask your first question.