Real estate
Idealista
Your listings and leads on Idealista, managed by an agent.
14 endpoints
VaultRE's API opens only to integrators MRI approves, and its Zapier app only adds enquiries and reports new listings. Sign in to VaultRE once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.
Not affiliated with VaultRE.
| What you need | VaultRE's API | GitHub MCP server | Cotlet |
|---|---|---|---|
| Contacts, notes, viewings, appraisals | No | No | Yes, 14 tools |
| Acts as you, signed in 24/7 | No | No | Yes, Cloud Browser |
| Fixed for you when VaultRE changes | N/A | No | Yes, tested every 6h |
| Runs with your laptop off | N/A | No | Yes, hosted |
Checked Oct 22, 2026. Sources: MRI Vault: API integrations (request form) · VaultRE API docs: Getting Started · VaultRE API docs: Technical Guide · MRI Vault Help: Integrate with Zapier
AI agents connect over MCP, scripts call the REST API. Both reach the same 14 tools with one API key.
Add Cotlet to your agent once. VaultRE and every other app you connect show up as its tools.
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" {
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": {
"Authorization": "Bearer ${COTLET_API_KEY}"
}
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.
Every tool is an endpoint under /api/v1/vaultre with its own method and path, such as POST /api/v1/vaultre/properties/{property_id}/viewing/schedule, with the same API key. Our open-source repo has ready scripts to start from.
14 tools on your own VaultRE account. Agents call them as operations of the MCP tools vaultre_read and vaultre_write; scripts call each one at its own REST endpoint, with the same inputs and answers.
| Tool | What it does | Access |
|---|---|---|
| list_enquiries | Holding Area enquiries with source, message, property asked about and the duplicate Vault suggests. | read |
| search_contacts | Find people, companies and suppliers by name, contact ID, company, phone, email or category. | read |
| get_contact | One contact card: details, categories, requirements, linked properties and upcoming events. | read |
| list_contact_notes | Notes on a contact card, newest first, with type, text, reminder and who wrote them. | read |
| search_properties | Properties by class, type, status, agent, location or address, with agents and last update. | read |
| get_property | One property card: status, agents, owners, method of sale, price, open homes and offers. | read |
| list_calendar_events | Events, appraisals and scheduled viewings in a user's calendar between two dates. | read |
| process_enquiry | Add a Holding Area enquiry to the database as a contact, with its note and optional buyer requirement. | writeasks first |
| ignore_enquiry | Mark a Holding Area enquiry as ignored, for spam or leads you do not want in the database. | writeasks first |
| add_contact | Add a person, company, supplier or solicitor, with a source of enquiry, categories and a first note. | writeasks first |
| add_note | Add a note to a contact or a property, with an optional reminder. | writeasks first |
| add_appraisal | Add an appraisal for an owner and a property, assigned to an appraiser with a date in their calendar. | writeasks first |
| schedule_viewing | Book a scheduled viewing for a property in an agent's calendar, with the attendee attached. | writeasks first |
| add_open_home | Add an open home to a property with date, times, a primary agent and optional secondary agents. | writeasks first |
Scroll the table for all 14 tools.
You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.
One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while VaultRE is enabled for agents, so 20 calls a day come to 550 credits.
| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
Yes, but only for approved integrators (checked 22 Oct 2026). VaultRE, now MRI Vault, publishes API docs, yet a developer needs an integrator key from MRI first, and the agency then creates an access token for that developer under Office Integrations > Third-Party Access. There is no official MCP server.
Sign up free, open VaultRE under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.
No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 14 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.
Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to VaultRE yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so VaultRE sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.
Not on anything that reaches other people: process_enquiry, ignore_enquiry, add_contact, add_note, add_appraisal, schedule_viewing, add_open_home wait for your OK by default. You can switch that off per tool for scheduled runs.
Yes. VaultRE is now sold as MRI Vault by MRI Software, and its sign-in page and help center use the MRI Vault name. The API and its docs still carry the VaultRE name. Cotlet works in the same signed-in app under either name.
No. The VaultRE API is rate limited to 10 requests per second and 10,000 requests per day for integrators. Cotlet does not call that API: it works in your signed-in account, at the pace of the app.
Yes. The agent acts as the Vault user you sign in with, so Vault's own permissions apply: property visibility follows the user profile, and contacts carry View/Read and Edit access settings. Sign in as a user with the access you want the agent to have.
Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when VaultRE changes. Pick Cotlet if you want it hosted and kept working for you.
Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.
Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.
No. Cotlet is independent and not affiliated with VaultRE.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy