Fondaro MCP

Overview

Fondaro MCP lets you connect an MCP assistant to your Fondaro account in plain language. Ask it to summarise a lead, draft a follow-up note, search property sources for a buyer, or create a shareable interactive brochure from the listings you choose. 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 the server, so there is nothing to install on the server side. MCP 2026-07-28 is preferred, and earlier revisions from 2025-11-25 back to 2024-10-07 are accepted through protocol negotiation. OAuth-capable clients use Fondaro browser sign-in, while API-key clients use a scoped Fondaro API key.

Two things make it safe to switch on:

• It acts as you. Everything the assistant does runs as your account in the organization you have selected. If you are a member, it 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. Each browser sign-in creates its own connected-app grant, while each manual setup uses its own API key. You can disconnect or revoke either one 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 has two modes:

• Connect sets up a new client.
• Your connections lists every credential you already have and lets you revoke any of them.

The connection endpoint

Every supported client uses the same address:

Copy it exactly, including the /mcp/v1 path and with no trailing slash. ChatGPT and Claude Code use the endpoint to discover Fondaro browser sign-in. API-key clients must also send their key as Authorization: Bearer fdr_mcp_….

Clients that support MCP 2026-07-28 use server discovery, the required request headers, and the request metadata envelope. Released clients on an earlier supported revision negotiate the compatibility path automatically. Both paths are stateless, use the same permissions and tools, and return JSON without a session or SSE stream.

Connect

Each setup panel shows one connection path. OAuth panels use browser sign-in, so there is no token or API key to copy. API-key panels load a private value called FONDARO_MCP_API_KEY into the same terminal that starts the client. Use a current released version of the client before following either path.

1. Choose your client

Pick your client at the top of Connect. The page then shows one setup panel for that client and nothing else. The available setup panels are ChatGPT, Codex CLI, Claude Code, Cursor, Visual Studio Code, and Another client for anything with a private header or secret field.

ChatGPT: connect with browser sign-in

ChatGPT supports Fondaro OAuth directly through a custom app:

1. In ChatGPT, open Settings, then Apps & Connectors. Enable Developer mode if your workspace requires it, then create a custom app.
2. Use https://api.fondaro.com/mcp/v1 as the app's MCP server URL and choose Connect.
3. Sign in to Fondaro, choose the organization the app should use, review the five requested permissions, and approve access.
4. Return to ChatGPT. If the action catalogue does not appear immediately, refresh the app's actions.

ChatGPT owns the OAuth client, PKCE verifier, access token, and refresh token. Fondaro never asks you to copy or paste any of them. The connection appears under Your connections, where you can disconnect it immediately without affecting any API keys.

The custom-app controls available to you depend on your ChatGPT workspace. OpenAI's authentication guide describes the OAuth flow and the ChatGPT-managed client identity.

Claude Code: connect with browser sign-in

Claude Code supports Fondaro OAuth directly through its user-scoped remote MCP configuration:

1. Update Claude Code to a current released version.
2. Run claude mcp add --transport http --scope user fondaro https://api.fondaro.com/mcp/v1 with no --header option.
3. Start Claude Code, open /mcp, choose fondaro, then choose Authenticate.
4. Sign in to Fondaro, choose the organization, review the five permissions, and choose Allow.

Claude Code owns the public client identity, PKCE verifier, access token, and rotating refresh token. Fondaro never asks you to copy or paste any of them. If you cancel an explicit re-login, Claude Code may show Needs authentication because it revokes the previous local session before opening the new consent page; run /mcp and authenticate again.

Anthropic's Claude Code MCP documentation describes the client's remote-server and authentication controls. This setup is for Claude Code only; hosted Claude connectors are a separate product surface.

API-key clients: 1. Create a scoped key

Create one dedicated key for each client and computer. Give it a clear name, keep only the scopes it needs, and optionally choose an expiry. A key starts with fdr_mcp_ and its full value is shown once. Save it in a password manager before continuing.

Fondaro stores only a secure hash. If you return to an existing key, choose one of the two honest paths:

• I saved this key: get the saved value from your password manager and continue.
• I no longer have it: create and verify a replacement, then revoke the lost key.

Reusing one key across several clients is possible, but not recommended. Activity from another client sharing the key can make connection verification ambiguous.

API-key clients: 2. Load the key for the current terminal session

Copy the command for your computer and run it. Each command prompts for the key with hidden input; the key itself is never part of the command or terminal history.

macOS Terminal (zsh):

read -s "FONDARO_MCP_API_KEY?Paste your Fondaro key, then press Return: "; export FONDARO_MCP_API_KEY; echo

Linux Terminal (bash):

read -rsp "Paste your Fondaro key, then press Enter: " FONDARO_MCP_API_KEY; export FONDARO_MCP_API_KEY; echo

Windows PowerShell:

$env:FONDARO_MCP_API_KEY = [System.Net.NetworkCredential]::new('', (Read-Host 'Paste your Fondaro key' -AsSecureString)).Password

The terminal waits after you run the command. Copy the key again from the still-open panel (or your password manager), paste it, and press Return/Enter. Nothing appears while pasting because the input is hidden.

Check only whether the value exists. These commands never print the key:

if [ -n "${FONDARO_MCP_API_KEY:-}" ]; then echo "Key loaded"; else echo "Key missing"; fi

if ($env:FONDARO_MCP_API_KEY) { 'Key loaded' } else { 'Key missing' }

This is a current terminal session setup: the value is available until you close that terminal window. Start the client from the same terminal. In a new terminal, run the secure prompt again and load the value saved in your password manager.

Do not paste the key into .zshrc, .bashrc, shell commands, project .env files, committed mcp.json, or config.toml. Fondaro does not publish a persistent setup path because that needs a verified OS credential store on each platform.

API-key clients: 3. Configure, launch, and verify

Codex CLI

Run these commands in the terminal where the key is loaded:

codex mcp add fondaro --url https://api.fondaro.com/mcp/v1 \
  --bearer-token-env-var FONDARO_MCP_API_KEY
codex mcp list

The shared Codex configuration stores the variable name, not the key. Start codex from this same terminal, open /mcp, and make one read-only Fondaro request. Return to the dashboard and select Check connection.

Cursor

Use a global or private mcp.json, not a project file that may be committed:

{
  "mcpServers": {
    "fondaro": {
      "url": "https://api.fondaro.com/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${env:FONDARO_MCP_API_KEY}"
      }
    }
  }
}

Launch Cursor with cursor . from the prepared terminal and inspect Fondaro in Cursor's MCP settings. If the launcher is unavailable or the variable reference is not resolved, use Codex CLI or Claude Code instead.

Visual Studio Code

Add Fondaro as a remote MCP server in your user configuration, not a repository file, so the key reference is never committed. Use the endpoint https://api.fondaro.com/mcp/v1 and an Authorization header whose value reads the prepared environment variable, then start Visual Studio Code from the terminal where the key is loaded. Consult your editor's own MCP configuration reference for the exact file and syntax it expects, and make one read-only Fondaro request before selecting Check connection.

Another client

Configure the endpoint https://api.fondaro.com/mcp/v1 and header name Authorization. Paste Bearer followed by the saved key only into a control explicitly described as a private secret or header field. If the client offers no such field, do not connect it.

What “Check connection” proves

After you make a request, Check connection briefly retries the key list. It succeeds only when that exact key has a newer last-request time or a higher request count, and says: Fondaro received a request from this key. It does not claim that a stateless MCP server is permanently online.

If no request appears, the setup panel keeps its state and gives client-specific checks. A revoked or expired key is rejected. After success, the one-time plaintext is cleared from browser memory.

Plain-language glossary

• API key: A password for one client connection.
• Browser sign-in: Fondaro OAuth approval handled between the client and your browser, without copying a token.
• Environment variable: A private value an app reads from the computer that started it.
• Current terminal session: Available until you close this terminal window.
• Saved configuration: Contains the variable name, not your Fondaro key.

Choosing scopes

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

Both document scopes only work while your organization has an active subscription. Documents is part of a paid plan, so a connected assistant cannot list or open your library without one.

If you leave every scope selected, the key gets all seven scopes available when it is created. A read-only CRM assistant is safest with just crm:read. A brochure-reading client needs brochures:read. A client that creates brochures normally needs brochures:write and properties:read, because Fondaro must snapshot the selected source listings; add brochures:read if it should list or reopen them later.

Keys keep the exact scope set stored when they were created. An older three-scope key does not gain brochure or document access automatically. Create a replacement with the scopes you need, reconnect the client with the new value, confirm it works, and then revoke the old key.

Your connections

Your connections is one list of everything currently connected to your Fondaro account. Each row shows:

• Credential type, so you can tell a key you configured yourself from an app you signed in to.
• Owner, the person the connection acts as.
• Permissions, the exact scopes it carries.
• Last use, the most recent request Fondaro received from it.
• Expiry, if one was set.
• Status, so an expired or revoked credential is obvious.

Every row can be revoked from here, and each credential is revoked independently: removing one never touches another. If you have connected an app that signs you in through your browser, it appears in this list too and can be disconnected at any time; disconnecting it leaves your fdr_mcp_ keys untouched.

Visibility follows your role:

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

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

An active key with no requests has a Finish setup action. Because the full value is not stored, the page asks whether you saved it or need to create a replacement.

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.

Removing someone's access

When a teammate leaves, or you simply want to cut their access, remove them from your organization. That severs their connected apps and 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 one connection, disconnect that app or 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, discover exact source-specific filter options, search them with verified filters, 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.
• Interactive brochures: create a 1–25-listing brochure, list and open brochures, update its recipient and styling, add/remove/reorder/refresh listings, correct listing details or locations, and renew, revoke, or permanently delete it. The result includes the same public /b/… link used by the dashboard viewer.
• Documents: list and read the documents you can access, write a new markdown document, edit one, publish it behind a public /d/… link or take that link down, and attach a document to a lead or detach it. Uploading a PDF and deleting a document stay in the dashboard.

Fondaro MCP exposes 63 tools in total, including all 13 interactive brochure operations and 9 document operations. A few CRM actions are reserved for organization admins: reassigning a lead's owners and moving many leads' status at once. Members do not see those tools. CRM writes and document writes require an active subscription; brochure writes remain available as a free Fondaro feature. Members see and change only brochures they created, while organization admins can operate across the organization. Documents follow the same shape: you can read what your organization shares plus your own private documents, and only the person who created a document, or an organization admin, can change or share it.

Create and share a brochure

First ask the assistant to choose a property source and resolve the place. It can use the source's bounded option list for exact types and amenities, then search with those values. A successful search reports which criteria were applied; unsupported or ambiguous filters stop with a suggested correction rather than returning an unfiltered list. Choose listings only from that successful result, then ask it to create the brochure. For example:

Search Idealista for homes for sale in Estepona. Show me the results before taking action. Then create “Estepona homes for Andrew” from these five result IDs, addressed to Andrew with the note “Five homes selected for your review,” and give me the share link.

Fondaro passes each result's exact source and source-native id into the brochure snapshot. Eligible sources are the internal Fondaro MLS (internal), Resales Online (resales_online), and all 19 public portal sources. Zoddak and Inmobalia can be searched but cannot currently be snapshotted into a brochure through MCP. Do not substitute a listing URL or edit an id. Idealista results also keep their es, it, or pt country value.

The returned public link works immediately, although durable image ingest and coordinate enrichment may continue in the background. Anyone with the link can view it until it expires or is revoked. Recipient names and notes, and the returned share link, are also placed in the selected AI client's conversation history. Use only personal data appropriate for that client's retention policy.

How it relates to Ask Fondaro

Ask Fondaro 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

• ChatGPT does not open Fondaro sign-in: confirm the custom app uses exactly https://api.fondaro.com/mcp/v1, then refresh its actions. If your Fondaro connection was disconnected, choose Reconnect in ChatGPT.
• Claude Code shows Needs authentication: open /mcp, choose fondaro, and authenticate again. Confirm the saved server uses the exact endpoint and has no Authorization header.
• An API-key client cannot connect: check the URL is exactly https://api.fondaro.com/mcp/v1 with no trailing slash, the environment variable is visible to the client process, and the key is sent as a bearer token.
• The client reports a protocol or handshake error: update to a current client release and reconnect. Fondaro prefers MCP 2026-07-28 and negotiates supported revisions from 2025-11-25 back to 2024-10-07 automatically.
• A key stopped working: it may have expired or been revoked. Create 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 CRM write or document write tool may be hidden because the organization has no active subscription. Brochure create/add/refresh/renew tools need both brochures:write and properties:read. Create a replacement key with the scopes you need, reconnect, 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.