Finds a location by its external ID, returns full map metadata, and lists every map the connected account can reach.
3actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro retrieves all maps accessible to your account with details about each. You quickly locate a map or check which locations are mapped.
Ayro fetches detailed information about a specific map including points and layers. You verify location data or troubleshoot map display issues.
Ayro finds locations in Mapulus using their external system identifier. You sync location data across systems or look up specific stores or branches.
Each card is one request a support team gets, and the Mapulus actions Ayro runs to close it.
Ayro looks the place up by the external identifier stored against it, so a record in your CRM or database resolves to its mapped location without anyone hunting for it by name.
Ayro lists the maps available to the connected account, filtered by name or tag, so a request for the right territory map ends with a specific map instead of a forwarded question.
Before anyone promises a visit or a delivery, Ayro checks whether a location exists for that external ID and says plainly when nothing matches.
In one exchange Ayro resolves the external ID to a location and pulls the metadata of the map holding it, joining the record and the geography without an export in between.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Mapulus actions it has and picks the ones a request needs.
Authorize the Mapulus account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Mapulus actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeMapulus · Ayro
What can you do in Mapulus without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Mapulus.
It is the identifier your other systems use for the same place - typically the record ID from a CRM or database that was stored against the Mapulus location. Find Location by External ID matches on that value and returns every location carrying it, which is what makes a customer record and a map point line up without a manual search.
All 3 actions your agent can call on Mapulus, straight from the live MCP connection.
Find locations by their external identifier.
Retrieve detailed information about a map.
Retrieves a paginated list of all maps accessible to the authenticated user.
Same connection, same setup. Pick the next one your team already uses.
Pulls the latest reading from every registered Ambient Weather station into the conversation.
Verifies phone numbers, emails, and postal addresses at capture, scores signup fraud risk, and honours do-not-call requests on the spot.
Finds the nearest open location, geocodes an address, calculates travel time, and returns a photo or embeddable map with the answer.
Pulls survey responses for a form or report, resolves the fields behind them, and reports where and when a feedback form is shown.
Reads and updates trip status, starts and completes trips, maintains geofences and beacons, and turns partial addresses into verified coordinates.
Reads a receipt the moment it arrives, extracts merchant, totals, tax, and line items, and keeps the registries it matches against current.

Authorize the account and your agent has all 3 actions from the first conversation.
