Fondaro MCP

Overview

Fondaro MCP lets you connect an AI assistant to your Fondaro account and work your CRM in plain language. Ask Claude to summarise a lead, have Cursor draft a follow-up note, or let an assistant search property sources for a buyer. Everything happens as you, with exactly the access you already have in the dashboard.

MCP (Model Context Protocol) is the open standard these assistants use to talk to outside tools. Fondaro runs a hosted MCP server, so there is nothing to install: you connect a client to one URL and sign in.

Two things make it safe to switch on:

• It acts as you. If you are a member, the assistant sees only the leads assigned to you. If you are an organization admin, it sees the whole organization. It can never do more through MCP than you can do in the dashboard.
• You stay in control. Connect over sign-in (OAuth) and you approve a consent screen before a client gets access. Prefer a key, and you can scope it, expire it, and revoke it whenever you like.

Finding the page

Open Settings, then Integrations, then the Fondaro MCP card. Members can also jump straight there from the Fondaro MCP link in the sidebar.

The page shows your connection URL, the tool scopes, and any API keys you have minted.

The connection URL

Every client connects to the same address:

Copy it exactly, including the /mcp/v1 path and with no trailing slash. The page has a copy button so you do not have to type it.

Connecting a client

You do not need a key for most desktop and web clients. They sign you in with your Fondaro account and show a consent screen the first time.

Claude (claude.ai or Claude Desktop)

1. In Claude, open Settings, then Connectors, then Add custom connector.
2. Paste the connection URL and confirm.
3. Sign in to Fondaro and approve the consent screen. Claude can now use your Fondaro tools.

Claude Code

1. Run claude mcp add --transport http fondaro https://api.fondaro.com/mcp/v1.
2. Run /mcp and follow the prompt to authenticate.
3. To use an API key instead of signing in, add --header "Authorization: Bearer fdr_mcp_YOUR_KEY" to the command in step 1.

Cursor

1. Open Settings, then MCP, then Add server (or add the snippet below to .cursor/mcp.json).
2. Cursor signs you in on first use. To use a key instead, add a headers block with your fdr_mcp_ token.

{
  "mcpServers": {
    "fondaro": {
      "url": "https://api.fondaro.com/mcp/v1"
    }
  }
}

ChatGPT

1. Add Fondaro as a connector and sign in when prompted.
2. ChatGPT connectors sign in over OAuth. API keys are not supported in ChatGPT.
3. Read tools work well here. Whether ChatGPT can run write actions depends on your ChatGPT plan.

Minting an API key

Use a key when a client connects with a static header rather than an interactive sign-in (for example a headless script). Any member can mint keys for themselves.

1. On the Fondaro MCP page, click Create key and give it a name (for example "Cursor laptop").
2. Optionally narrow its scopes or set an expiry (1 to 3650 days).
3. Copy the key. It is shown exactly once. If you lose it, revoke it and create a new one.
4. Paste it into your client as a Bearer token: Authorization: Bearer fdr_mcp_….

A key starts with fdr_mcp_ and is stored only as a secure hash, so nobody, including Fondaro, can read it back. That is why a lost key is replaced, not recovered.

Choosing scopes

Scopes decide what a key can do. Grant only what the client needs:

If you do not pick any scopes, the key gets all three. A read-only assistant is safest with just crm:read (add properties:read if it should search listings too).

Rotating a key

There is no rotate button, and you do not need one: create a new key, swap it into your client, confirm it works, then revoke the old one. Nothing goes down in between.

Managing keys

• Members see and manage their own keys.
• Organization admins see every key in the organization and can revoke any of them, which is useful when someone leaves the team.

Revoking a key takes effect immediately and cannot be undone. Any client still using it stops working, so mint a replacement first if you need one.

Removing someone's access

When a teammate leaves, or you simply want to cut their access, remove them from your organization. That severs both their sign-in (OAuth) connections and their API keys within a few minutes, so you do not have to track down each one by hand. If instead you want to keep them in the organization but retire a single key, revoke that key from this page.

What the assistant can do

Once connected, the assistant can work across your CRM and property data. Among other things it can:

• Leads: list and search your leads, read a lead's full detail and activity timeline, count leads by pipeline stage, create leads, update contact details, move a lead's status, and set tags.
• Tasks and notes: list, create, update, and delete tasks and notes on the leads you can access.
• Deals: list and read deals, create them, change stage, and close them won or lost.
• Calls and emails: read a lead's call history, stored transcripts and AI analysis, and email history. These are read-only and never start new billed transcription or analysis.
• Properties: list the property sources you can search, then search them, open a listing's full details, and resolve place names. Sources include the internal Fondaro MLS, your connected integrations (Resales Online, Zoddak, Inmobalia), and 19 public property portals.

A few actions are reserved for organization admins: reassigning a lead's owners and moving many leads' status at once. Members do not see those tools. And because writing needs an active subscription, an organization without one keeps the read tools but not the write ones.

How it relates to Autopilot

Autopilot is Fondaro's own in-dashboard assistant. Fondaro MCP is the reverse direction: it lets an assistant you already use elsewhere reach into Fondaro. You can use either, or both. They draw on the same CRM, so what one changes the other sees.

Troubleshooting

• The client cannot connect: check the URL is exactly https://api.fondaro.com/mcp/v1 with no trailing slash.
• A key stopped working: it may have expired or been revoked. Mint a fresh one and update your client.
• A tool is missing: your key may lack that tool's scope, the tool may be admin-only, or a write tool may be hidden because the organization has no active subscription. Mint a key with the scopes you need, or ask an admin.
• Searches say the daily allowance is reached: external property portals share a daily limit per organization. It resets at midnight UTC, and your internal MLS and connected sources keep working in the meantime.

The full technical reference, including every tool and its scope, lives in the MCP server API guide.

Questions? Write to support@fondaro.com.