Search authorized real estate in Mexico and manage favorites and publishing with OAuth.
Scored across 13 tools
Most tools target clearly distinct resources and actions: search, get details, save/remove favorites, manage lists, publish, and render results. The only close boundaries are get_property_list versus list_property_lists, and render_property_results versus restore_property_results, but their descriptions largely clarify the difference.
The set consistently uses snake_case and mostly follows a verb_noun pattern such as search_properties, get_property, save_property_to_list, and delete_property_list. The main deviation is my_listings, which lacks a verb, and get_property_contact is slightly less predictable than the rest.
Thirteen tools is well within a reasonable range for a property marketplace server covering search, details, favorites, publishing, and UI rendering. Each tool appears to earn its place, with no obviously redundant operations.
Core workflows are covered: property search, detail retrieval, contact, favorites management, publishing, and reviewing one's listings. However, there is no explicit create_property_list operation for custom favorite lists, and published listings can be created and reviewed but not updated or deleted through the tool surface.
Use this when an authenticated user explicitly asks to permanently delete one of their PropFácil favorite lists and its saved entries. Do not use it for removing a single property.
Inputs: listId (required). Returns: listId, deleted
Use this when the user wants the details of one PropFácil listing and has supplied a listingKey or ID from search_properties.
Inputs: id (required). Returns: property
Use this when the user explicitly asks to contact the advertiser or open the original listing for a property previously returned by PropFácil.
Inputs: id (required). Returns: contact
Use this when an authenticated user wants to inspect one of their PropFácil favorite lists and its saved properties.
Inputs: listId (required). Returns: list, items
Use this when an authenticated user wants to see their PropFácil favorite lists. This returns only lists owned by the linked user.
Inputs: no named parameters. Returns: lists
Use this when an authenticated user asks to review the property listings they published on PropFácil.
Inputs: no named parameters. Returns: listings
Use this when an authenticated user explicitly asks to publish a property on PropFácil. This creates a private draft that goes public only after the user reviews and activates it on PropFácil at the returned confirmUrl. Safe to retry with the same idempotencyKey.
Inputs: city (required), price (required), title (required), description (required), +10 more. Returns: id, url, status, reasons, +2 more
Use this when an authenticated user asks to remove a saved property from one of their PropFácil lists. The list remains available if it becomes empty.
Inputs: listId (required), propertyId (required). Returns: listId, removed, propertyId
Use this when an authenticated user asks to rename one of their PropFácil favorite lists.
Inputs: name (required), listId (required). Returns: list
Use this when, after search_properties, the user would benefit from interactive property cards, comparison, details, or a map. Pass only listing IDs already returned by a data tool.
Inputs: propertyIds (required), title. Returns: count, title, properties
Use this when the PropFácil app needs to restore the latest public property selection for the current MCP session after its widget is recreated.
Inputs: no named parameters. Returns: render
Use this when an authenticated user asks to save a property to a favorite list. If no list is supplied, use the idempotent default list named Favoritos.
Inputs: propertyId (required), note, listId, listName. Returns: list, saved, propertyId
Use this when the user wants to find PropFácil property listings in Mexico by city, transaction type, price, bedrooms, or geographic radius.
Inputs: city, near, limit, radius, +4 more. Returns: count, results, nextCursor
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Real estate agency CRM: listings, clients, leads and viewings from your AI assistant (OAuth).
International real-estate search and buyer workflows for AI agents via MCP and OAuth 2.1.
Search SimplyRETS MLS listings and open houses; read listing and market analytics.
Search commercial real estate listings. Reads need no token; authoring is self-serve OAuth (DCR).
Add one secure layer between your agents and this server.