vaultre-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, obtained at https://cotlet.dev/app. Used as a Bearer token (Authorization: Bearer $COTLET_API_KEY). Without it, tool calls answer: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app". |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
VaultRE through Cotlet.dev. Call vaultre_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vaultre_guideA | How to work in VaultRE (manage enquiries, contacts, properties and viewings): its screens and the sign-in link. Call this first. |
| vaultre_statusB | Check that your Cotlet.dev account and VaultRE are ready: account, credits and VaultRE connection. |
| 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. |
| vaultre_readB | Read the current VaultRE page: its text and numbered buttons, links and fields. |
| vaultre_clickB | Click a numbered element on the current VaultRE page. |
| vaultre_typeB | Type text into a numbered field on the current VaultRE page. |
| vaultre_closeA | Close the VaultRE browser session when the work is done, so credits stop running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
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.
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.
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.
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.