Model Context Protocol

Connect HAVN to your AI workspace.

HAVN MCP lets ChatGPT, Claude, VS Code, and other compatible clients ask for scoped real estate context from HAVN without exposing a direct database connection.

Endpoint https://mcp.havnre.app/mcp
HAVN mobile Settings screen showing MCP access and Create key button

Step 1

Create your HAVN MCP key

  1. Open HAVN on iPhone, iPad, Android, or the web app.
  2. Go to Settings and find MCP access.
  3. Tap Create key. HAVN shows the full key once so you can reveal and copy it.
  4. Use the key as a Bearer token with the HAVN MCP endpoint.

Step 2

Connect common AI clients

ChatGPT

Connect as a ChatGPT connector

  1. Open ChatGPT Settings and go to Connectors.
  2. Enable Developer Mode while HAVN is not yet listed as an official public app.
  3. Add the MCP server URL.
  4. When ChatGPT opens HAVN authorization, paste your HAVN MCP key and approve.
Open ChatGPT Connectors
Claude

Connect with Claude remote MCP

  1. Open Claude settings for integrations or connectors.
  2. Add a custom integration that points to the HAVN endpoint.
  3. Complete HAVN authorization with your MCP key when Claude opens the OAuth flow.
  4. For Claude Code, use the HTTP command below instead.
claude mcp add --transport http havn https://mcp.havnre.app/mcp \
  --header "Authorization: Bearer YOUR_HAVN_MCP_API_KEY"
VS Code and GitHub Copilot

Add the HTTP MCP server

  1. Open the MCP server configuration for VS Code.
  2. Add HAVN as an HTTP MCP server.
  3. Set the Authorization header to Bearer YOUR_HAVN_MCP_API_KEY.
{
  "mcpServers": {
    "havn": {
      "type": "http",
      "url": "https://mcp.havnre.app/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_HAVN_MCP_API_KEY"
      }
    }
  }
}
Cursor, Windsurf, and other clients

Use the standard remote MCP pattern

Most MCP-capable coding assistants accept either a remote MCP URL with headers or a JSON mcpServers configuration. Use the same endpoint and Bearer token shown above.

{
  "mcpServers": {
    "havn": {
      "type": "http",
      "url": "https://mcp.havnre.app/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_HAVN_MCP_API_KEY"
      }
    }
  }
}

What AI can ask for

Available HAVN tools

workspace_summary

A compact overview of the user's HAVN workspace.

search_properties

Find properties the user can access.

get_property_media

Fetch permission-checked property image links and metadata for HTML pages, brochures, and AI-generated drafts.

search_contacts

Search contacts connected to the user's role or agency.

search_open_houses

Find open houses and showing activity.

search_leads

Search leads for follow-up context.

search_tasks

Search accessible tasks with property, contact, lead, and open-house links.

search_seller_reports

Search seller reports with property context, report metrics, and AI summary data.

analytics_summary

Fetch scoped agency, property, lead-conversion, and open-house analytics.

search_files

Search accessible uploaded files and return signed URLs for private attachments.

search_media

Search property photos, contact media, agent avatars, agency icons, and contact pass assets.

Security model

Role-scoped access, not a database login

How HAVN limits access

  • Every user gets a separate MCP key.
  • Keys are validated by HAVN before any tool reads data.
  • Results are scoped to the user and agency role stored in HAVN.
  • Property media links are returned only for properties visible to that user or agency role.
  • Private attachment links are short-lived signed URLs generated only after HAVN confirms access.
  • Keys can be rotated or revoked from Settings.

How to handle your key

  • Treat the key like a password.
  • Do not paste it into public chats, tickets, screenshots, or source code.
  • Rotate the key if a device or AI account is shared with someone else.
  • Remove unused connectors in each AI client.

Provider docs

Official references