[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# VaultRE API and MCP server

> 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.

MRI Vault, formerly VaultRE, is a cloud CRM for real estate agencies in Australia and New Zealand: contacts, properties, appraisals, listings, a calendar and portal enquiries in one database.

## What is the VaultRE API?

Cotlet's VaultRE API exposes 14 endpoints for your own VaultRE account: list enquiries, search contacts, get contact, list contact notes, search properties, get property, list calendar events, process enquiry, ignore enquiry, add contact, add note, add appraisal, schedule viewing and add open home. The list_enquiries endpoint returns holding Area enquiries with source, message, property asked about and the duplicate Vault suggests. Each endpoint takes simple JSON inputs like property_id, contact_id or limit and works both as an operation of the vaultre_read or vaultre_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Real estate](https://cotlet.dev/integrations/category/real-estate.md)
- **Endpoints:** 14 (7 read, 7 write)
- **Updated:** 2026-10-21

Yes, but only for approved integrators (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for VaultRE with 14 endpoints (7 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does VaultRE have an official API?

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.

| Task | VaultRE official | Cotlet |
|---|---|---|
| Search contacts | Partly: The API reads contacts; approved integrators only, with a token from the agency | Yes |
| Add a contact | Partly: The docs name website enquiries becoming contacts as an example; approved integrators only | Yes |
| Add an enquiry to the Holding Area | Partly: The Zapier action adds one; nothing in it reviews, processes or ignores enquiries | Yes |
| Search properties and listings | Partly: The docs show listings on an agency website; approved integrators only | Yes |
| Connect an AI agent to your own account | No: No official MCP server | Yes |
| Use it without MRI approving a developer | No: Integrator request first, then a token from the agency | Yes |

Sources: [MRI Vault: API integrations (request form)](https://www.mrisoftware.com/au/products/vault/api-integrations/), [VaultRE API docs: Getting Started](https://docs.api.vaultre.com.au/basics.html), [VaultRE API docs: Technical Guide](https://docs.api.vaultre.com.au/guide.html), [MRI Vault Help: Integrate with Zapier](https://support.vaultre.com.au/hc/en-au/articles/10401807483151-Integrate-with-Zapier)

## For AI agents

```text
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.
Cotlet provides a hosted MCP server and REST API for VaultRE: 14 tools (7 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=vaultre, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    vaultre_read, vaultre_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/vaultre, each operation at its own route, e.g. POST /api/v1/vaultre/properties/{property_id}/viewing/schedule
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_enquiries, search_contacts, get_contact, list_contact_notes, search_properties, get_property, list_calendar_events, process_enquiry, ignore_enquiry, add_contact, add_note, add_appraisal, schedule_viewing, add_open_home
Confirm      process_enquiry, ignore_enquiry, add_contact, add_note, add_appraisal, schedule_viewing, add_open_home (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/vaultre-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=vaultre, requests VaultRE in the Cotlet console and creates an API key there.
2. The user signs in to VaultRE once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables VaultRE for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted VaultRE server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to VaultRE in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get VaultRE only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no VaultRE login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following VaultRE's terms; Cotlet is not affiliated with VaultRE.
```

## What can an AI agent do in VaultRE?

Cotlet is best for real estate agencies and agents who want an AI agent to process portal enquiries, book viewings, add appraisals and log notes in their VaultRE CRM without running or fixing a server.

- **[Process portal enquiries](https://cotlet.dev/integrations/vaultre-api-mcp-server/process-property-enquiries.md)** (runs: daily): "Go through the VaultRE Holding Area enquiries awaiting review. Add real buyers to their existing contact or a new one with a buyer requirement, ignore spam, and leave anything unclear for me with a one-line reason." → `list_enquiries`, `search_contacts`, `process_enquiry`, `ignore_enquiry`
- **[Book property viewings](https://cotlet.dev/integrations/vaultre-api-mcp-server/book-property-viewings.md)** (runs: daily): "Book a scheduled viewing at 14 Wattle Street, Marrickville for Priya Nair on Saturday at 10:30 in Sam's calendar. Check Sam is free first, add Priya as a contact if she is not in VaultRE, and mark it accompanied." → `search_properties`, `search_contacts`, `add_contact`, `list_calendar_events`, `schedule_viewing`
- **[Add an appraisal from an owner lead](https://cotlet.dev/integrations/vaultre-api-mcp-server/add-appraisal-from-lead.md)** (runs: weekly): "Priya Nair (contact 51377) wants an appraisal of 31 Banksia Avenue, Dulwich Hill for sale. Book Sam for Tuesday at 9:00, add the appraisal and note that she found us through a letterbox drop." → `search_contacts`, `search_properties`, `add_appraisal`, `add_note`
- **Log call notes on contacts** (runs: daily): "Here are today's call summaries. Find each person by mobile number in VaultRE and add the summary as a note with a reminder in 3 days." → `search_contacts`, `add_note`
- **Weekly appraisals and listings report** (runs: weekly): "Every Monday, list the properties updated in the last 7 days with status Appraisal or Listing, with agent and address, grouped by agent." → `search_properties`, `get_property`

## Can VaultRE automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a VaultRE connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to process portal enquiries, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/vaultre/enquiries. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/vaultre/enquiries with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to VaultRE.

### list_enquiries

Holding Area enquiries with source, message, property asked about and the duplicate Vault suggests. Access: read. REST: `GET /api/v1/vaultre/enquiries`. MCP: `vaultre_read → list_enquiries`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | awaiting_review (default), processed or ignored. |
| `department` | enum | no | sales or leasing. Default: both. |
| `since` | date | no | Only enquiries received on or after this date. |
| `source` | string | no | Where the enquiry came from, e.g. 'realestate.com.au'. |
| `agent` | string | no | Agent email. |
| `property_id` | string | no | Only enquiries about this property. |
| `limit` | integer | no | Maximum enquiries to return. |
| `cursor` | string | no | Next page cursor from the previous call. |

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.

Example response:

```json
{
  "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
}
```

### search_contacts

Find people, companies and suppliers by name, contact ID, company, phone, email or category. Access: read. REST: `GET /api/v1/vaultre/contacts/search`. MCP: `vaultre_read → search_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | enum | no | person, company or creditor_supplier. |
| `name` | string | no | First name, surname or contact ID. |
| `company_name` | string | no | Company name. |
| `phone_or_email` | string | no | A contact number or an email address. |
| `category` | string | no | A contact category of your account. |
| `include_archived` | boolean | no | Also search archived contacts. Default: false. |
| `limit` | integer | no | Maximum contacts to return. |
| `cursor` | string | no | Next page cursor from the previous call. |

Searches Contacts > Search with the criteria you give; more criteria narrow the result. Each row has the name, company, email, mobile, marketing contacts and last update, the columns Vault shows. Archived contacts stay out unless include_archived is true. Use it before add_contact to avoid a duplicate.

Example response:

```json
{
  "contacts": [
    {
      "contact_id": "51377",
      "type": "person",
      "name": "Priya Nair",
      "company": null,
      "email": "priya.nair@example.com",
      "mobile": "0400 000 123",
      "marketing_contacts": [
        "Sam Reid"
      ],
      "updated_at": "2026-10-20T16:40:00+11:00"
    }
  ],
  "next_cursor": null
}
```

### get_contact

One contact card: details, categories, requirements, linked properties and upcoming events. Access: read. REST: `GET /api/v1/vaultre/contacts/{contact_id}`. MCP: `vaultre_read → get_contact`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from search_contacts. |

Returns the contact as the card and its snapshot show it: type, all numbers and emails, address, sources of enquiry, categories, buy or rent requirements, linked properties and upcoming events and tasks. What you get back depends on the access settings of your Vault user, so a contact you cannot view fails with APP_PERMISSION_DENIED.

Example response:

```json
{
  "contact_id": "51377",
  "type": "person",
  "name": "Priya Nair",
  "emails": [
    "priya.nair@example.com"
  ],
  "mobiles": [
    "0400 000 123"
  ],
  "address": "12 Station Road, Marrickville NSW 2204",
  "sources_of_enquiry": [
    "realestate.com.au"
  ],
  "categories": [
    "Buyer"
  ],
  "requirements": [
    {
      "kind": "buy",
      "description": "3 bedroom house, Marrickville"
    }
  ],
  "properties": [
    {
      "property_id": "22810",
      "address": "14 Wattle Street, Marrickville NSW 2204",
      "role": "enquirer"
    }
  ],
  "upcoming_events": [
    {
      "type": "scheduled_viewing",
      "starts_at": "2026-10-24T10:30:00+11:00"
    }
  ]
}
```

### list_contact_notes

Notes on a contact card, newest first, with type, text, reminder and who wrote them. Access: read. REST: `GET /api/v1/vaultre/contact-notes`. MCP: `vaultre_read → list_contact_notes`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from search_contacts. |
| `limit` | integer | no | Maximum notes to return. |

Returns the notes from the contact's Notes tab. Notes Vault writes itself, such as the enquiry note with date, source and message, are included. read_only is true for notes nobody can edit or remove.

Example response:

```json
{
  "notes": [
    {
      "note_id": "n_90211",
      "note_type": "Enquiry",
      "text": "Enquiry via realestate.com.au on 22 Oct 2026: is the open home on Saturday still on?",
      "created_by": "Vault",
      "created_at": "2026-10-22T09:20:00+11:00",
      "reminder_at": null,
      "read_only": false
    }
  ]
}
```

### search_properties

Properties by class, type, status, agent, location or address, with agents and last update. Access: read. REST: `GET /api/v1/vaultre/properties/search`. MCP: `vaultre_read → search_properties`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `class` | enum | no | residential, commercial, land or rural. |
| `type` | enum | no | sale or lease. |
| `status` | enum | no | listing, prospect, appraisal, conditional or unconditional. |
| `agent` | string | no | Agent email. |
| `location` | string | no | A suburb or custom region. |
| `address` | string | no | Street number and name. |
| `updated_since` | date | no | Only properties updated on or after this date. |
| `limit` | integer | no | Maximum properties to return. |
| `cursor` | string | no | Next page cursor from the previous call. |

Searches Properties > Search. Each row has the full address, class, status, agents and last update. You only see the properties your Vault user is allowed to see; an administrator can widen that in Vault. updated_since limits the result to properties changed on or after that date.

Example response:

```json
{
  "properties": [
    {
      "property_id": "22810",
      "address": "14 Wattle Street, Marrickville NSW 2204",
      "class": "residential",
      "type": "sale",
      "status": "listing",
      "agents": [
        "Sam Reid"
      ],
      "updated_at": "2026-10-21T14:05:00+11:00"
    }
  ],
  "next_cursor": null
}
```

### get_property

One property card: status, agents, owners, method of sale, price, open homes and offers. Access: read. REST: `GET /api/v1/vaultre/properties/{property_id}`. MCP: `vaultre_read → get_property`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | string | yes | Property ID from search_properties. |

Returns the property card with its owners, agents, the method of sale (Private Treaty, Auction, Tender or Set Sale Date), the price, the open homes and the offers with their status (Pending, Rejected or Withdrawn). Listing fields appear only for a property that is a listing.

Example response:

```json
{
  "property_id": "22810",
  "address": "14 Wattle Street, Marrickville NSW 2204",
  "class": "residential",
  "type": "sale",
  "status": "listing",
  "agents": [
    "Sam Reid"
  ],
  "owners": [
    {
      "contact_id": "48820",
      "name": "Helen Ward"
    }
  ],
  "method_of_sale": "Private Treaty",
  "price": 1450000,
  "open_homes": [
    {
      "date": "2026-10-24",
      "start_time": "10:00",
      "end_time": "10:30",
      "primary_agent": "Sam Reid"
    }
  ],
  "offers": [
    {
      "buyer": "Priya Nair",
      "status": "pending",
      "amount": 1420000
    }
  ]
}
```

### list_calendar_events

Events, appraisals and scheduled viewings in a user's calendar between two dates. Access: read. REST: `GET /api/v1/vaultre/calendar-events`. MCP: `vaultre_read → list_calendar_events`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | datetime | yes | Start of the window. |
| `to` | datetime | yes | End of the window. |
| `calendar_user` | string | no | Email of the Vault user whose calendar to read. Default: you. |
| `type` | enum | no | event, appraisal or scheduled_viewing. |

Returns the events on one calendar in date order: summary, type, start and end, the property and contacts attached, and whether the event is confirmed or cancelled. Reading another user's calendar needs Global Calendar access or Settings (Module Access) in Vault's User Management.

Example response:

```json
{
  "events": [
    {
      "event_id": "evt_90102",
      "type": "scheduled_viewing",
      "summary": "Viewing 14 Wattle Street",
      "starts_at": "2026-10-24T09:30:00+11:00",
      "ends_at": "2026-10-24T10:00:00+11:00",
      "property": "14 Wattle Street, Marrickville NSW 2204",
      "contacts": [
        "Daniel Kim"
      ],
      "confirmed": true,
      "cancelled": false
    }
  ]
}
```

### process_enquiry

Add a Holding Area enquiry to the database as a contact, with its note and optional buyer requirement. Access: write, asks the user first. REST: `POST /api/v1/vaultre/enquiries/{enquiry_id}/process`. MCP: `vaultre_write → process_enquiry`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `enquiry_id` | string | yes | Enquiry ID from list_enquiries. |
| `contact_id` | string | no | Add the enquiry to this existing contact. |
| `create_new_contact` | boolean | no | Create a new contact even if Vault suggests a match. Default: false. |
| `categories` | array | no | Contact categories to apply. |
| `create_buyer_requirement` | boolean | no | Add a buyer requirement for the property asked about. Default: false. |

Does what Review and Create Enquiry does. Without contact_id, Vault's suggested match is used if there is one; set create_new_contact to true when the enquiry is a different person. Vault writes the enquiry as a note on the contact, and with create_buyer_requirement it links a requirement to the property asked about. Office automations in Vault can react to the new contact. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "enquiry_id": "enq_80412",
  "status": "processed",
  "contact_id": "51377",
  "contact_created": false,
  "note_added": true,
  "buyer_requirement_created": true
}
```

### ignore_enquiry

Mark a Holding Area enquiry as ignored, for spam or leads you do not want in the database. Access: write, asks the user first. REST: `POST /api/v1/vaultre/enquiries/{enquiry_id}/ignore`. MCP: `vaultre_write → ignore_enquiry`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `enquiry_id` | string | yes | Enquiry ID from list_enquiries. |

Does what Ignore Enquiry does on an Awaiting review enquiry. Vault deletes ignored enquiries permanently after 3 months, and Cotlet has no tool to restore one. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "enquiry_id": "enq_80419",
  "status": "ignored"
}
```

### add_contact

Add a person, company, supplier or solicitor, with a source of enquiry, categories and a first note. Access: write, asks the user first. REST: `POST /api/v1/vaultre/contacts`. MCP: `vaultre_write → add_contact`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | enum | yes | person, company, creditor_supplier or solicitor. |
| `first_name` | string | no | First name (not for company). |
| `last_name` | string | no | Surname (not for company). |
| `company_name` | string | no | Company name. |
| `email` | string | no | Email address. |
| `mobile` | string | no | Contact number. |
| `source_of_enquiry` | string | no | One of your account's sources of enquiry. |
| `categories` | array | no | Contact categories to apply. |
| `note` | string | no | First note with the enquiry or conversation. |

Does what Contacts > Add Contact Wizard does. A person needs first_name, last_name and a way to reach them; a company uses company_name instead of a person name. A contact's email addresses can be included in your Vault eMarketing, so check with search_contacts first and confirm. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "contact_id": "51402",
  "type": "person",
  "name": "Daniel Kim",
  "source_of_enquiry": "Office website",
  "categories": [
    "Buyer"
  ],
  "note_added": true
}
```

### add_note

Add a note to a contact or a property, with an optional reminder. Access: write, asks the user first. REST: `POST /api/v1/vaultre/notes`. MCP: `vaultre_write → add_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `text` | string | yes | The note. |
| `contact_id` | string | no | Contact to add the note to. |
| `property_id` | string | no | Property to add the note to, instead of a contact. |
| `note_type` | string | no | One of your account's note types for a contact or property. |
| `reminder_at` | datetime | no | Set a reminder for this time. |
| `read_only` | boolean | no | Lock the note so nobody can edit or remove it. Default: false. |

Adds a note as the Notes tab does. Give contact_id or property_id. note_type is one of your account's note types, and a reminder can be set. A note added with read_only true cannot be edited or removed by anyone in Vault, so the default is false. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "note_id": "n_90234",
  "contact_id": "51377",
  "note_type": "Phone call",
  "reminder_at": "2026-10-26T09:00:00+11:00",
  "read_only": false
}
```

### add_appraisal

Add an appraisal for an owner and a property, assigned to an appraiser with a date in their calendar. Access: write, asks the user first. REST: `POST /api/v1/vaultre/appraisals`. MCP: `vaultre_write → add_appraisal`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_type` | enum | yes | sale or lease. |
| `address` | string | yes | Street address of the property. |
| `appraiser` | string | yes | Email of the Vault user doing the appraisal. |
| `starts_at` | datetime | yes | Date and time of the appraisal. |
| `owner_contact_id` | string | no | Existing contact to attach as the owner. |
| `owner_name` | string | no | New owner's name, when there is no owner_contact_id. |
| `owner_email` | string | no | New owner's email. |
| `owner_phone` | string | no | New owner's phone number. |

Does what Properties > Appraisal Wizard does. Give an existing owner_contact_id, or the owner's name, email and phone so Vault can check for a duplicate. Vault adds the appointment to the appraiser's calendar. No email or SMS reminder is set. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "property_id": "23044",
  "status": "appraisal",
  "type": "sale",
  "address": "31 Banksia Avenue, Dulwich Hill NSW 2203",
  "owner_contact_id": "51377",
  "appraiser": "sam@harbourlane.example",
  "starts_at": "2026-10-27T09:00:00+11:00"
}
```

### schedule_viewing

Book a scheduled viewing for a property in an agent's calendar, with the attendee attached. Access: write, asks the user first. REST: `POST /api/v1/vaultre/properties/{property_id}/viewing/schedule`. MCP: `vaultre_write → schedule_viewing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | string | yes | Property ID from search_properties. |
| `contact_id` | string | yes | Attendee, a contact ID from search_contacts. |
| `starts_at` | datetime | yes | Start of the viewing. |
| `ends_at` | datetime | yes | End of the viewing. |
| `calendar_user` | string | no | Email of the Vault user whose calendar gets the event. Default: you. |
| `accompanied` | boolean | no | Tick the accompanied box. Default: false. |
| `confirmed` | boolean | no | Tick the confirmed box. Default: false. |
| `notes` | string | no | Event notes. |

Adds an event of type Scheduled Viewing, as Calendar > Add Event does. accompanied and confirmed are the two status boxes. Nothing is sent to the attendee, because Vault's email or SMS on confirming is a separate toggle on the event. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "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
}
```

### add_open_home

Add an open home to a property with date, times, a primary agent and optional secondary agents. Access: write, asks the user first. REST: `POST /api/v1/vaultre/properties/{property_id}/open-homes`. MCP: `vaultre_write → add_open_home`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | string | yes | Property ID from search_properties. |
| `date` | date | yes | Date of the open home. |
| `start_time` | string | yes | Start time, e.g. '10:00'. |
| `end_time` | string | yes | End time, e.g. '10:30'. |
| `primary_agent` | string | yes | Email of the agent running the open home. |
| `secondary_agents` | array | no | Emails of additional agents. |

Does what Add Open Home on the property card does. Vault adds the event to the calendars of the agents named. Editing or removing an open home is done in Vault. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "open_home_id": "oh_5521",
  "property_id": "22810",
  "date": "2026-10-24",
  "start_time": "10:00",
  "end_time": "10:30",
  "primary_agent": "sam@harbourlane.example",
  "secondary_agents": []
}
```

## How do I connect VaultRE to Claude Code, Codex or Cursor?

Connecting VaultRE takes three steps: sign up, sign in to VaultRE once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect VaultRE to your agent.

1. **Create an account** Sign up and add VaultRE in the console. Your API key is there too.

2. **Sign in to VaultRE in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to VaultRE there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

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

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

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

4. **Ask your agent** Ask in plain words. Your agent finds the VaultRE tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Go through the VaultRE Holding Area enquiries awaiting review. Add real buyers to their existing contact or a new one with a buyer requirement, ignore spam, and leave anything unclear for me with a one-line reason.
```

### Call VaultRE from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/vaultre with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
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}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "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
}
```

## Why use Cotlet for VaultRE?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to VaultRE yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When VaultRE changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect VaultRE to Cotlet?

Yes. You sign in to VaultRE yourself, in your own Cloud Browser, and we never save your password. Your agents only get VaultRE once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

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.

**Is this an official VaultRE integration?**

No, Cotlet is independent of VaultRE. VaultRE's own API is open only to approved partners. Cotlet works through your own VaultRE account, the way you use VaultRE in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to VaultRE in your console: your agents lose access at once and you stay signed in. Signing out of VaultRE in the browser works too, and Reset browser deletes the whole profile.

## Is there a VaultRE MCP server on GitHub?

The realistic option is VaultRE's Zapier app. It has one action, Create Enquiry in Holding Area, and one trigger, New Property Listing (Sales). It does not read contacts or properties, add notes, or book anything. Cotlet covers the rest of the CRM through your own signed-in account and works next to Zapier, n8n and Make.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Create a token under Office Integrations > Third-Party Access, paste it into Zapier, build each Zap | Sign up, sign in to VaultRE once, add one MCP server or API key |
| What it can do | Add an enquiry to the Holding Area, start a Zap on a new listing | Search contacts and properties, process enquiries, add notes, appraisals, viewings and open homes |
| When VaultRE changes | Zapier maintains its VaultRE app | Our team tests it daily and fixes it for you; failed calls are free |
| Your VaultRE access | An API token you can revoke in Vault | Your own Cloud Browser in the EU, session encrypted, only for the apps you enable, disabled for agents in one click |
| Upkeep | You build and watch each Zap; your plan limits monthly tasks | Nothing to host or update |
| Where it runs | In Zapier; polled triggers run at your plan's interval | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | A Zapier plan, with a monthly task limit | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when VaultRE changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the VaultRE API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the VaultRE API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| 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. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own VaultRE account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to VaultRE yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get VaultRE only after you enable it. When VaultRE signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to VaultRE, sign out of VaultRE in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **VaultRE's terms:** You use your own VaultRE account and stay responsible for following VaultRE's terms. Cotlet is independent and not affiliated with VaultRE. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open VaultRE in the console and press Request access. Then you create your API key and connect VaultRE there.

**Do I need to be technical?**

No. You sign in to VaultRE once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect VaultRE to Cotlet?**

Yes. You sign in to VaultRE yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get VaultRE once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My VaultRE sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your VaultRE cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through VaultRE's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. VaultRE sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no VaultRE login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

VaultRE offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**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.

**Can my agent post or send messages in VaultRE without asking me?**

No. Every call to process_enquiry, ignore_enquiry, add_contact, add_note, add_appraisal, schedule_viewing or add_open_home waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the VaultRE API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/vaultre from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

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.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.