Lists available cities, reads saved property searches and their alert settings, and fires test webhooks at your endpoint.
3actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro looks up available cities to verify if properties exist in a customer's desired area. This cuts down response time and prevents mismatched leads.
Ayro retrieves the customer's saved property searches from Melo to follow up with matching new listings. This keeps the conversation personal and shows the team understands their criteria.
Each card is one request a support team gets, and the Melo actions Ayro runs to close it.
Ayro pulls the city list with the filters applied, so a question about whether a particular area is covered is settled from the data rather than assumed from the country.
Ayro returns the search with its location filters, budget range, and property types, so a client asking what is being watched on their behalf gets the actual criteria.
Ayro filters the saved searches by notification status, which answers the common complaint of hearing nothing about a search that was never switched on to alert.
Ayro triggers a realistic sample payload at your HTTPS endpoint, so the handler is proven against advert and contact data before real property matches start arriving.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Melo actions it has and picks the ones a request needs.
Authorize the Melo 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 Melo 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 freeMelo · Ayro
What can you do in Melo 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 Melo.
Not with these actions. Get Cities, List Searches, and Simulate Webhook cover city availability, saved searches, and webhook testing - none of them return individual adverts or price history. Ayro can tell you what a saved search is looking for, but not enumerate what it currently matches.
All 3 actions your agent can call on Melo, straight from the live MCP connection.
Retrieve a list of cities with optional filters.
Retrieves all property searches saved by the authenticated user from the Melo API.
Simulates sending a Melo webhook event to a specified endpoint for testing webhook integrations.
Same connection, same setup. Pick the next one your team already uses.
Resolves addresses to census geography, returns ACS and population estimates, sizes local business activity, and finds the right variable to query.
Searches the places index, finds points of interest near a coordinate, and pulls a venue's record, photos, and visitor tips by FSQ ID.
Geocodes addresses one at a time or in bulk, calculates routes, travel-time matrices and isochrones, and returns ready-to-share map images.
Reports which agents are running, stops or unschedules the ones that should not be, files the leads a run produced, and tracks quota use.
Runs image, maps, and academic scholar searches mid-conversation and answers with live results and their sources.
Runs a live, scoped web search when a question falls outside your own help content.

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