MCP — for Claude and developer tools

Coming soon. The MCP server is being rolled out; this page describes how it works once it is live.

letsrealty runs a remote Model Context Protocol server, so an AI assistant can work your CRM in conversation: "which Hot Leads haven't we called this week?", "log this WhatsApp chat as a note on Ana's Lead".

• URL: https://api.letsrealty.io/mcp (Streamable HTTP)
• Auth: an API Key as Authorization: Bearer lr_live_…

The server uses the same API Keys, scopes, rate limits and rules as the REST API. Calls through MCP cost letsrealty no AI and do not count toward your AI allowance.

Choose the key's scopes

The tools a key can use follow its scopes. For an assistant that only answers questions, give it leads:read and activities:read. Add leads:write and activities:write only if it should change things — tools that change status, archive or reassign a Lead are marked as destructive, so your client asks you before running them.

Claude Code

claude mcp add --transport http letsrealty https://api.letsrealty.io/mcp \
  --header "Authorization: Bearer $LETSREALTY_API_KEY"

Claude Desktop and Claude.ai

Add a custom connector with the URL https://api.letsrealty.io/mcp and the header Authorization: Bearer lr_live_…. Header authentication for connectors is in beta in Claude; if your plan doesn't offer it yet, use Claude Code or another client below.

Cursor and other clients

Any client that accepts static headers works. For Cursor, in .cursor/mcp.json:

{
  "mcpServers": {
    "letsrealty": {
      "url": "https://api.letsrealty.io/mcp",
      "headers": { "Authorization": "Bearer lr_live_…" }
    }
  }
}

Not yet supported

ChatGPT connectors require OAuth sign-in, which letsrealty doesn't offer yet. Browsing history and website chat transcripts are never available over MCP or the API.