Skip to main content
Glama
vaultre-mcp

vaultre-mcp

How to connect VaultRE to Claude Code, ChatGPT and any AI agent

Yes, ChatGPT, Claude and other AI agents can work in your VaultRE account. Cotlet.dev connects your own signed-in VaultRE account to any AI agent, so you can ask in plain words and the AI manages enquiries, contacts, properties and viewings for you.

What you can ask

List all new VaultRE enquiries from realestate.com.au and show the property and possible duplicate contact.

Process Priya Nair's enquiry for 14 Wattle Street and add a buyer requirement for the property.

Find contacts in the sales department whose email contains example.com and add a note to Priya's record.

Show this week's open homes and schedule a viewing for Alex Morgan on Saturday at 11 am.

Give me a weekly report of appraisals, listings and upcoming viewings for the sales team.

Related MCP server: Desktop Commander MCP (Transductive Edge Edition)

Connect in 2 minutes

Get your API key at https://cotlet.dev/app and export it as COTLET_API_KEY.

Claude Code

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

ChatGPT

Settings → Apps → add connector URL https://cotlet.dev/mcp/v1, then sign in with Cotlet.dev. No API key needed.

Cursor

Copy .cursor/mcp.json from this repo into your project:

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

Run it locally (stdio)

This repo is a real MCP server. It speaks MCP over stdio, lists its VaultRE tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.

{"mcpServers":{"vaultre":{"command":"uvx","args":["vaultre-mcp"],"env":{"COTLET_API_KEY":"your-key"}}}}

Or with Docker:

docker build -t vaultre-mcp .
docker run -i --rm -e COTLET_API_KEY vaultre-mcp

Tools: vaultre_guide, vaultre_status, vaultre_open, vaultre_read, vaultre_click, vaultre_type, vaultre_close. Without COTLET_API_KEY a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".

Command line

Python 3.10+, nothing else to install. From PyPI:

pip install vaultre-mcp        # or run it once: uvx vaultre-mcp connect
vaultre-mcp connect

Or straight from this repo:

export COTLET_API_KEY="your-key"
python3 vaultre_agent.py connect   # ready config for Claude Code, Cursor, ChatGPT
python3 vaultre_agent.py status    # is VaultRE ready in your Cotlet.dev account
python3 vaultre_agent.py guide     # VaultRE screens and sign-in link
python3 vaultre_agent.py read      # open VaultRE, read the page, close the browser
python3 vaultre_agent.py tools     # list Cotlet.dev tools
python3 vaultre_agent.py serve     # start the stdio MCP server (same as no argument)

Questions from VaultRE users

Does VaultRE have an API?

VaultRE, now sold as MRI Vault, has an API for approved developers, but no official MCP server (checked 27 Oct 2026). Cotlet.dev works in your own signed-in VaultRE account, so your AI agent can manage enquiries and property workflows with no API key and no code.

How do I connect VaultRE to ChatGPT?

Add Cotlet.dev as an app in ChatGPT with the connector URL https://cotlet.dev/mcp/v1, sign in to VaultRE once in your Cotlet.dev Cloud Browser, and ask ChatGPT in plain words.

Is there a way to use Claude with VaultRE?

Yes. In Claude Code run the one-line claude mcp add command above; in the Claude app add https://cotlet.dev/mcp/v1 as a custom connector. Claude then works in your own VaultRE account.

Is there a VaultRE MCP server?

VaultRE has no official MCP server. Cotlet.dev is a hosted MCP server that works in VaultRE with ChatGPT, Claude, Cursor, Codex, n8n, Make and scripts.

Find it on

Also works with


More: https://cotlet.dev/integrations/vaultre-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=vaultre

Start free: https://cotlet.dev/signup?app=vaultre&utm_source=github&utm_medium=readme&utm_campaign=vaultre

Available Tools

7 tools
vaultre_clickB

Click a numbered element on the current VaultRE page.

Inputs: element (required).

vaultre_closeA

Close the VaultRE browser session when the work is done, so credits stop running.

Inputs: no named parameters.

vaultre_guideA

How to work in VaultRE (manage enquiries, contacts, properties and viewings): its screens and the sign-in link. Call this first.

Inputs: task.

vaultre_openB

Open a VaultRE page in your signed-in Cloud Browser (default https://vaultre.com.au) to work with manage enquiries, contacts, properties and viewings.

Inputs: url.

vaultre_readB

Read the current VaultRE page: its text and numbered buttons, links and fields.

Inputs: element.

vaultre_statusB

Check that your Cotlet.dev account and VaultRE are ready: account, credits and VaultRE connection.

Inputs: no named parameters.

vaultre_typeB

Type text into a numbered field on the current VaultRE page.

Inputs: text (required), element (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: reading, clicking, typing, guidance, status checking, opening, and closing. The boundary between vaultre_open and vaultre_guide is clear because one starts a session and the other provides instructions.

    Naming Consistency5/5

    All tools follow a consistent vaultre_ + verb pattern: vaultre_read, vaultre_click, vaultre_type, vaultre_guide, vaultre_status, vaultre_open, vaultre_close. The convention is predictable and easy to scan.

    Tool Count5/5

    Seven tools are well-scoped for a browser-automation server: a compact lifecycle of open, inspect, interact, check status, get guidance, and close. Each tool earns its place without redundant operations.

    Completeness4/5

    The surface covers the essential browser lifecycle and core interactions needed for VaultRE workflows. Minor gaps exist for specialized interactions like dropdown selection, file upload, scrolling, or waiting, but the read/click/type trio provides workarounds for most tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to operate property management systems via natural language, covering repair orders, owner info, payments, notices, and inspections. Features a full agentic workflow with human-in-the-loop and observability.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read and act on SmartAgent real estate CRM data, such as finding leads, creating tasks, moving deals through pipelines, looking up property listings, and leaving notes.
      MIT