VaultRE MCP Server

Enquiries, contacts, properties, viewings and notes in your VaultRE CRM.

Hosted MCP Server

npx add-mcp 'https://cotlet.dev/mcp/v1/vaultre'

Installs into Claude Code, Codex, Cursor and more

Documentation

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

VaultRE API and MCP server: Let your AI agent clear the VaultRE Holding Area.

VaultRE, now sold as MRI Vault, has no MCP server (checked 27 Oct 2026). Its API is documented in the open, but a developer must first be approved as an integrator by MRI, and your agency then creates a token for them under Office Integrations > Third-Party Access. Cotlet runs 14 VaultRE tools hosted, over MCP for agents and REST for scripts, with your own MRI Vault login.

Enquiries, contacts, properties, viewings and notes in your VaultRE CRM. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

Free 7-day trial, no card
Unofficial, not affiliated with MRI Software
Page: https://cotlet.dev/integrations/vaultre-api-mcp-server

What can you automate in VaultRE?

Process portal enquiries
Book scheduled viewings
Add appraisals from owner leads
Log call notes on contacts
Add the week's open homes
Report appraisals and listings weekly

Does VaultRE have an MCP server or an API?

MRI says new integrations are "generally" set up "within two business days" after it reviews the request.
The API reads the Holding Area and can submit a new enquiry, but has no call that processes or ignores one.
Zapier has one action, Create Enquiry in Holding Area, and one trigger, New Property Listing (Sales).

What you need	VaultRE API	Zapier	Cotlet
Read Holding Area enquiries	Yes	No	Yes
Process or ignore an enquiry	No	Adds one only	Yes, after your OK
Contacts and notes	Yes	No	Yes
Viewings, open homes, calendar	Yes	No	Yes, after your OK
Hosted MCP for your agent	No	The 2 steps above	Yes
What you need first	A developer MRI approves	A token and a Zapier plan	Your MRI Vault login

Checked 27 Oct 2026. Sources: VaultRE API docs: Getting Started, VaultRE API docs: Technical Guide, VaultRE OpenAPI v1.3, MRI Vault: request integration access, VaultRE on Zapier

How does Cotlet connect to VaultRE?

Sign in to VaultRE. Use your own account in its Cotlet Cloud Browser.
Choose MCP or REST. Connect your agent or create a Cotlet API key.
Run your workflow. Ask your agent or send an HTTP request.

We never keep your MRI Vault password, and no enquiry, contact, note, appraisal or calendar event is saved in Vault before you approve it.

Connect VaultRE to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

Sign in to MRI Vault in a Cloud Browser. Make a Cotlet account, open VaultRE in its Cloud Browser, log in with your own MRI Vault user and press Enable for agents.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 in the MCP server or connector field of your agent.
Approve the connection. Chat apps send you to a Cotlet sign-in page. Code editors, n8n and scripts send an API key from the console.

https://cotlet.dev/mcp/v1 serves every Cotlet app you enable, VaultRE included. Enable VaultRE after connecting and the connector needs a refresh before its tools show.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: vaultre_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: vaultre_write

How to use the VaultRE REST API

Create your Cotlet API key

Create a Cotlet API key with access to VaultRE and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect VaultRE in Cotlet and enable it for agents. Account access: Your own MRI Vault (VaultRE) user. What the agent can see and change follows your user profile permissions.

Make your first VaultRE API request

REST:

curl "https://cotlet.dev/api/v1/vaultre/enquiries?limit=5" \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read enquiries and apply the operation limits

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "vaultre",
  "tool": "list_enquiries",
  "result": {
    "enquiries": [
      {
        "enquiry_id": "enq_80412",
        "status": "awaiting_review",
        "received_at": "2026-10-22T09:12:00+11:00",
        "source": "realestate.com.au",
        "department": "sales",
        "name": "Priya Nair",
        "email": "priya.nair@example.com",
        "mobile": "0400 000 123",
        "message": "Hi, is the open home on Saturday still on?",
        "property": "14 Wattle Street, Marrickville NSW 2204",
        "possible_duplicate": {
          "contact_id": "51377",
          "name": "Priya Nair",
          "matched_on": "email"
        }
      }
    ],
    "next_cursor": null
  }
}

Returns the enquiries Vault holds from portals, your office website and QR check-ins, filtered like the Holding Area screen. status picks Awaiting review, Processed or Ignored. possible_duplicate is the contact Vault preselects as a match, with what it matched on. Pass enquiry_id to process_enquiry or ignore_enquiry.

limit: Maximum enquiries to return.

cursor: Next page cursor from the previous call.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

VaultRE workflows for agents and automations

Tool	Connect through	Example workflow
n8n	HTTP Request	Find people, companies and suppliers by name, contact ID, company, phone, email or category. Use `search_contacts` in your configured property report.
Make	HTTP > Make a request	One property card: status, agents, owners, method of sale, price, open homes and offers. Use `get_property` in your configured property report.
Python or Node.js	REST API	Events, appraisals and scheduled viewings in a user's calendar between two dates. Use `list_calendar_events` in your configured property report.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads VaultRE; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

VaultRE API endpoints and MCP tools

Holding Area enquiries

The VaultRE API cannot process or ignore an enquiry; these tools do it on the Review screen. Vault deletes ignored enquiries for good after 3 months.

List enquiries (list_enquiries, read): Holding Area enquiries with source, message, property asked about and the duplicate Vault suggests.
Process enquiry (process_enquiry, write, asks first): Add a Holding Area enquiry to the database as a contact, with its note and optional buyer requirement.
Ignore enquiry (ignore_enquiry, write, asks first): Mark a Holding Area enquiry as ignored, for spam or leads you do not want in the database.

Contacts and notes

Search before adding, since a new contact's emails can land in your eMarketing lists. A note stays editable unless you ask for read-only.

Search contacts (search_contacts, read): Find people, companies and suppliers by name, contact ID, company, phone, email or category.
Get contact (get_contact, read): One contact card: details, categories, requirements, linked properties and upcoming events.
List contact notes (list_contact_notes, read): Notes on a contact card, newest first, with type, text, reminder and who wrote them.
Add contact (add_contact, write, asks first): Add a person, company, supplier or solicitor, with a source of enquiry, categories and a first note.
Add note (add_note, write, asks first): Add a note to a contact or a property, with an optional reminder.

Properties, appraisals and open homes

No tool publishes a listing; portals get it only when you pick them and save in Vault.

Search properties (search_properties, read): Properties by class, type, status, agent, location or address, with agents and last update.
Get property (get_property, read): One property card: status, agents, owners, method of sale, price, open homes and offers.
Add appraisal (add_appraisal, write, asks first): Add an appraisal for an owner and a property, assigned to an appraiser with a date in their calendar.
Add open home (add_open_home, write, asks first): Add an open home to a property with date, times, a primary agent and optional secondary agents.

Calendar and viewings

Booking into another agent's calendar needs Global Calendar access on your Vault user.

List calendar events (list_calendar_events, read): Events, appraisals and scheduled viewings in a user's calendar between two dates.
Schedule viewing (schedule_viewing, write, asks first): Book a scheduled viewing for a property in an agent's calendar, with the attendee attached.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/vaultre-api-mcp-server#tools

Who can see my VaultRE session, and how do I revoke it?

What we store. Your signed-in MRI Vault profile, encrypted with AES-256-GCM, in Finland. Never the password.
What your agent gets. 14 VaultRE tools. No cookie and no login.
What the session sees. What your Vault user profile allows, down to each contact's View/Read and Edit access.
What no tool touches. eMarketing sends, SMS, portal publishing, offers and user management.
If Vault logs you out. We email you a sign-in link. You log in yourself, we never do.
How to cut access. Disable for agents, reset the browser or delete the key. The next call fails.

The cleanest setup is a Vault user made for the agent, with only the property and contact access you want it to have; Vault's own permissions then do the limiting. The Cotlet site has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results); there is no SOC 2 report or third-party pentest yet.

Is it against VaultRE's terms? Account safety

An independent contractor, agent or other third party acting on behalf of Client may be deemed a Client User upon prior written consent of MRI, which MRI shall determine in its sole discretion

MRI Software Australia Terms and Conditions, section 1.7 (read 27 Oct 2026)

MRI's Australian master agreement has no clause on robots, scripts or scraping in the part we read, and it does not name Vault, so the agreement your agency signed may differ. What it does say is that only Client Users may use the software, and a third party acting for you needs MRI's written consent. Your agent logs in as your own Vault user, but if that matters to you, ask your MRI account manager. We found no public case of a Vault account blocked over automation (checked 27 Oct 2026).

How we keep your account looking like you:

Your own MRI Vault login, typed in by you
One Cloud Browser with a steady IP and cookies, like the office desktop
Every write waits for your OK, from a note to a viewing
No tool exports the contact database or sends eMarketing
If MRI objects, we pause the VaultRE tools for everyone within 24 h

A Holding Area with 40 enquiries is worked one at a time, at the pace of the Review screen, not in one burst.

What happens when VaultRE changes?

12 h between tests of the VaultRE enquiry, contact, property and calendar reads
24 h between tests of the writes: notes, contacts, viewings, appraisals
$0 for a call to a VaultRE tool paused for a fix

Vault keeps moving: the login page now says MRI Vault, MRI posted "What's new in MRI Vault CRM this quarter" in June 2026, and the API changelog has five entries in 2026, the latest on 22 Sep 2026. When a screen moves, we repair the tool and keep its name. status.cotlet.dev checks the site, console and API every 3 minutes.

Approvals, undo and mistakes

Reads the queue. Every enquiry awaiting review, with the match Vault suggests.
Checks the match. Email and mobile against your contacts, so one buyer is not added twice.
Waits for your OK. Each add and each ignore sits in your Cotlet console with the reason.
Reports back. Added, ignored, and the ones left for you with a one-line reason.

Action	Undo
Process an enquiry	Fix the contact in Vault; the enquiry note stays on it
Ignore an enquiry	Vault deletes it after 3 months; no tool restores it
Add a contact	Archive it in Vault
Add a note	Edit or remove it, unless it was saved read-only
Add an appraisal	Click Withdrawn on the property
Schedule a viewing	Mark it Cancelled; that toggle can text the attendee
Add an open home	Edit or remove it on the property in Vault

All 7 write tools ask first, because each one changes the shared office database. Reads run at once. For a scheduled run you can switch the wait off per tool, for example for add_note after a day of calls.

schedule_viewing leaves Confirmed off and sends nothing. The buyer hears from you only when someone ticks Confirmed in Vault and its email or SMS template goes out.

MCP call:

{
  "name": "schedule_viewing",
  "arguments": {
    "property_id": "22810",
    "contact_id": "51377",
    "starts_at": "2026-10-24T10:30:00+11:00",
    "ends_at": "2026-10-24T11:00:00+11:00",
    "calendar_user": "sam@harbourlane.example",
    "accompanied": true
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/vaultre/properties/22810/viewing/schedule \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"contact_id":"51377","starts_at":"2026-10-24T10:30:00+11:00","ends_at":"2026-10-24T11:00:00+11:00","calendar_user":"sam@harbourlane.example","accompanied":true}'

Response:

{
  "event_id": "evt_90331",
  "type": "scheduled_viewing",
  "property": "14 Wattle Street, Marrickville NSW 2204",
  "attendee": "Priya Nair",
  "calendar_user": "sam@harbourlane.example",
  "starts_at": "2026-10-24T10:30:00+11:00",
  "ends_at": "2026-10-24T11:00:00+11:00",
  "accompanied": true,
  "confirmed": false
}

A website form handler or a nightly job can call the same tools over REST at /api/v1/vaultre, with one key and one price, and with no integrator key or 10,000-requests-a-day quota. A call your Vault user may not make returns an error and costs nothing. Every tool row above lists its REST path.

How much does the VaultRE MCP server cost?

About $48 a month for one sales office with 6 agents, 8,340 credits. Your MRI Vault subscription stays as it is, and no developer needs MRI's approval.

Job	Calls	Credits
Holding Area enquiries, daily	8 × 30	2,400
Book a scheduled viewing	4 × 40	1,600
Log a call note on a contact	2 × 100	2,000
Appraisal from an owner lead	4 × 8	320
Open homes for the week	5 × 4	200
Appraisals and listings report, weekly	8 × 4	320
Cloud Browser, 30 days		1,500
Total		8,340

Free 7-day trial, no card
10 credits per successful call, MCP or REST
50 credits a day for the Cloud Browser
No integrator registration or API token needed

The month is our example: 6 agents, the Holding Area cleared daily, 40 viewings, 100 call notes, 8 appraisals, weekly open homes and a weekly report. MRI publishes neither an agency size nor its own prices; third-party estimates put MRI Vault near A$165 to A$200 a user a month. Dollars at the $29 pack rate.

VaultRE MCP server on GitHub, Make or hosted: which to use

Option	What it does	Where it stops
VaultRE by Maxmel Tech (Make)	A community Make app: contacts, properties, notes, owners and tenants, watch triggers and a raw API call. Updated 9 Dec 2025.	No enquiry processing or viewings module; you build each scenario.
VaultGroup/api-samples	The vendor's sample API queries. 4 stars, last push 24 Jul 2024.	Samples, not a server; needs an integrator key.
mihaikelemen/vaultre	A small client for the API. 0 stars, last push 28 Feb 2021.	Unmaintained; needs an integrator key.

VaultGroup's own vaultre-mcp-registry on GitHub lists MCP servers for MRI's staff (Jira, Zendesk, logs), not for agency data. If your web developer is building a listings site, the approved-integrator API is the right route. If leads only need to reach the Holding Area, Zapier does that. If your agent should work the Holding Area, book viewings and log notes, Cotlet does that hosted.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Take Group sp. z o.o. runs Cotlet: a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the VaultRE tools go to contact@cotlet.dev.

VaultRE API and MCP: questions

How do I get access?

Sign up free at https://cotlet.dev, find VaultRE under Integrations in the console and log in to MRI Vault in its Cloud Browser. The trial starts when you sign up and needs no card.

How do I connect VaultRE to ChatGPT or Claude?

Sign up at cotlet.dev, log in to VaultRE once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your VaultRE account through Cotlet, in their phone apps too.

What can ChatGPT do in VaultRE?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in VaultRE: process portal enquiries; book property viewings; add an appraisal from an owner lead. You ask in plain words, and anything that reaches other people waits for your OK first.

Is VaultRE the same as MRI Vault?

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.

Do VaultRE's API rate limits apply to Cotlet?

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.

Can I limit what the agent can see?

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.

Does VaultRE have webhooks?

Yes, for approved integrators: VaultRE sends webhook events about data changes to an endpoint the developer names. Cotlet has none. To react to new enquiries, run your agent on a schedule, for example every 30 minutes on weekdays.

Is the MCP server different from the REST API?

Only in how you call it. Both expose the same 14 tools with the same inputs and answers, one API key and one price. Agents use MCP; scripts and form handlers use REST.

Is Cotlet affiliated with VaultRE or MRI Software?

No. Cotlet is independent and not affiliated with VaultRE, MRI Vault or MRI Software.

Can I use the VaultRE API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.

Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.