Connect an MCP client: Claude, ChatGPT, Cursor, VS Code, Zed

Add one connector, https://platform.casafari.com/mcp, sign in once, and every product's tools are there.

https://platform.casafari.com/mcp

Any MCP client that supports remote MCP servers over Streamable HTTP with OAuth can connect; in Claude and ChatGPT that means adding a custom MCP connector. You sign in with OAuth in the browser, with no key to copy; if you have no account yet, you create one at the sign-in (Free plan, no card). Name the connector Casafari (the entry casafari in a configuration file). The full guide, with REST and API keys, is Connect to the Casafari Platform.

Already a Casafari client? Use the same server: sign up at https://platform.casafari.com/console/, and if you have a contract, Casafari sets your account up on the Custom plan. mcp.casafari.com is the legacy gateway, still answering, moving to https://platform.casafari.com/mcp/<product>.

#Client by client

#Claude

1. Open Customize → Connectors, choose + Add and then Add custom connector.
2. Name it Casafari and paste https://platform.casafari.com/mcp as the URL.
3. Choose Connect, sign in or create your account, accept the Platform Terms of Use and approve.

The connector works in claude.ai, Claude Desktop and the Claude mobile apps alike.

Using Claude Team or Enterprise? In a company Claude workspace only an organisation owner can add a custom connector; members see Add custom connector greyed out ("Ask an organization owner to add this for your team"). An owner adds the one connector once, under Organization settings → Connectors → Add custom connector, named Casafari with the URL https://platform.casafari.com/mcp.

Each member then chooses Connect on the connector and signs in with their own Casafari Platform account, so plans and usage stay with each person's account. No owner at hand? Claude Code adds a server for you alone: claude mcp add --transport http casafari https://platform.casafari.com/mcp.

#ChatGPT

1. Turn on Developer mode in ChatGPT's settings (Apps & Connectors, advanced settings).
2. Create a connector named Casafari, paste https://platform.casafari.com/mcp as the MCP server URL and choose OAuth.
3. Sign in or create your account and approve.

#Claude Code

claude mcp add --transport http casafari https://platform.casafari.com/mcp

Then run /mcp inside Claude Code and choose Authenticate.

#Cursor

Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "casafari": { "url": "https://platform.casafari.com/mcp" }
  }
}

#VS Code

Add to .vscode/mcp.json:

{
  "servers": {
    "casafari": { "type": "http", "url": "https://platform.casafari.com/mcp" }
  }
}

#Codex CLI

codex mcp add casafari --url https://platform.casafari.com/mcp
codex mcp login casafari

codex mcp login opens Casafari's sign-in page in the browser. The entry is [mcp_servers.casafari] with url = "https://platform.casafari.com/mcp" in ~/.codex/config.toml, which the Codex IDE extension shares.

#Gemini CLI

gemini mcp add --transport http casafari https://platform.casafari.com/mcp

Then run /mcp auth casafari inside Gemini CLI and sign in in the browser. The entry lands in .gemini/settings.json as "httpUrl"; add --scope user to keep it in ~/.gemini/settings.json for every project.

#Devin Desktop (formerly Windsurf)

Add to ~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows), which Devin CLI reads too:

{
  "mcpServers": {
    "casafari": { "url": "https://platform.casafari.com/mcp" }
  }
}

Devin opens Casafari's sign-in page the first time it uses the server; in Devin CLI, devin mcp login casafari does it on demand.

#Visual Studio

GitHub Copilot in Visual Studio 2022 17.14 or later. Add to %USERPROFILE%\.mcp.json (or .mcp.json in the solution folder):

{
  "servers": {
    "casafari": { "url": "https://platform.casafari.com/mcp" }
  }
}

Then choose Manage Authentication in the CodeLens above the server and sign in in the browser.

#Zed

Open Settings → AI → MCP Servers, choose Add Server, then Add Remote Server. Or add to ~/.config/zed/settings.json (%APPDATA%\Zed\settings.json on Windows):

{
  "context_servers": {
    "casafari": { "url": "https://platform.casafari.com/mcp" }
  }
}

With no Authorization header in the entry, Zed signs in with the standard MCP OAuth flow and opens Casafari's sign-in page.

#Cline

In Cline's MCP Servers panel, open Remote Servers, name the server casafari, paste the URL and choose Streamable HTTP. In the MCP settings file (Configure MCP Servers) the entry is:

{
  "mcpServers": {
    "casafari": { "type": "streamableHttp", "url": "https://platform.casafari.com/mcp" }
  }
}

Cline authorizes a remote server in the browser; in Cline CLI, cline mcp has Authorize OAuth.

#JetBrains Junie

Add to ~/.junie/mcp/mcp.json (or .junie/mcp/mcp.json in a project); Junie in JetBrains IDEs and Junie CLI read the same configuration:

{
  "mcpServers": {
    "casafari": { "url": "https://platform.casafari.com/mcp" }
  }
}

The server shows Authorization required until you sign in: in Junie CLI run /mcp, choose Authorize on the server and sign in in the browser.

#Kiro

Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in a workspace):

{
  "mcpServers": {
    "casafari": { "url": "https://platform.casafari.com/mcp" }
  }
}

Kiro runs the OAuth sign-in in the browser when it connects.

#Warp

Open Settings → Agents → MCP servers, choose + Add and paste:

{
  "casafari": { "url": "https://platform.casafari.com/mcp" }
}

Warp opens the browser for sign-in the first time the server starts.

#goose

Run goose configure, choose Add Extension, then Remote Extension (Streamable HTTP), and give https://platform.casafari.com/mcp as the URL (in goose Desktop: Extensions → Add custom extension). goose registers itself and signs in with OAuth in the browser.

#Any other client or agent

Point the client at https://platform.casafari.com/mcp. It registers itself (OAuth 2.1 with dynamic client registration and PKCE) and opens Casafari's sign-in page; the authorization server's metadata is at https://platform.casafari.com/.well-known/oauth-authorization-server.

#Check it works

Ask your assistant to call account_status: it answers with your plan and balance. Place names become location ids with locations_search, free, on the same server.

#Where else to find Casafari

Every entry below points at the same servers under https://platform.casafari.com/mcp and signs in with OAuth 2.1, so no API key is needed.

• Claude: Claro AI by Casafari is in Claude's Connectors Directory; everything else is the custom connector above.
• Cursor: Casafari in the Cursor Directory, with Add to Cursor next to each server.
• Postman: Casafari on Postman's API Network, with a collection of the MCP servers and REST collections.
• Glama: one connector per server, such as Claro AI on Glama.
• Official MCP Registry: search the registry for casafari.
• GitHub: casafari/casafari-mcp holds the Claude Code plugin, the Cursor plugin, the Gemini CLI extension and REST examples.

#One product at a time

Each product is also its own server, for a connector limited to one product or an existing connection:

• Location Lookup: https://platform.casafari.com/mcp/locations
• Area Insights: https://platform.casafari.com/mcp/area-insights
• Comparables: https://platform.casafari.com/mcp/comparables
• Comparables with Transactions: https://platform.casafari.com/mcp/comparables-transactions
• Property Sourcing: https://platform.casafari.com/mcp/property-sourcing
• Private Seller Leads: https://platform.casafari.com/mcp/private-sellers
• AgencyGraph: https://platform.casafari.com/mcp/agencygraph
• Cadastre: https://platform.casafari.com/mcp/cadastre
• Parcel Zoning: https://platform.casafari.com/mcp/parcel-zoning
• Claro AI: https://platform.casafari.com/mcp/claro

Each of these is its own protected resource with its own sign-in; its tools and prices are the same as on the one server. For a product's server, use its URL in the steps above and name the entry casafari-<product>, for example casafari-comparables. Alerts and High Potential Seller Leads have no MCP server.

#Questions about this

• What is Casafari MCP?
• Which address do I use: api.casafari.com or platform.casafari.com (mcp.casafari.com is the legacy gateway)?
• I already have Casafari MCP or API access. Does anything change for me?
• How do I connect Casafari to Claude, ChatGPT, Claude Code or Cursor?