Diese Seite wurde noch nicht in Ihre Sprache übersetzt. Angezeigt wird die Version Englisch (Vereinigtes Königreich).
MCP server
Connect an MCP client to Fondaro with OAuth or a scoped fdr_mcp_ key, and call 131 tools for leads, deals, properties, brochures, documents and the help docs.
Fondaro runs a hosted Model Context Protocol (MCP) server so an AI client can work with your leads, deals, tasks, notes, property sources, interactive brochures and documents as you. Every call runs with your own access: nothing over MCP reaches more than you can reach in the dashboard. The server exposes 131 tools from twenty-four explicitly allowlisted tool groups, and the tools are listed below.
To work with the same data from your own code instead of an AI client, use the REST API with an API key. Nearly every tool here has a matching /v1 route.
Endpoint
Use it exactly as written, with no trailing slash. The server prefers MCP 2026-07-28 over Streamable HTTP and also negotiates 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05 and 2024-10-07. It is stateless and answers JSON: only POST carries MCP traffic, there is no session and no SSE stream.
Authenticate
The server accepts two bearer credentials. Anything else, including a dashboard session token, returns 401.
| Credential | Shape | How you get it |
|---|---|---|
| OAuth access token | fdr_oat_… | Your client runs the browser sign-in for you. You never copy it. |
| MCP API key | fdr_mcp_ + 32 lowercase hex characters | Settings › Integrations › Fondaro MCP, or POST /mcp-keys |
OAuth
Clients discover OAuth from the endpoint, then use authorization code with S256 PKCE and refresh their own tokens.
| Document | URL |
|---|---|
| Authorization server metadata | https://api.fondaro.com/.well-known/oauth-authorization-server |
| Protected resource metadata | https://api.fondaro.com/.well-known/oauth-protected-resource/mcp/v1 |
The resource is https://api.fondaro.com/mcp/v1. A client that asks for no scope gets the four read scopes (crm:read, properties:read, brochures:read, documents:read); write scopes must be requested and approved.
API keys
A key belongs to the person who created it. The full key is shown once and stored only as a SHA-256 hash; if you lose it, revoke it and create another. Keys can expire after 1 to 3650 days.
Scopes
| Scope | Allows |
|---|---|
crm:read | Read leads, tasks, notes, deals, calls, email, messages, your Inbox, your calendar and records, search the help docs, and (admins) read the agency's settings |
crm:write | Create and change leads, tasks, notes and deals, move or cancel your own meetings and viewings, and (admins) change the agency's settings |
properties:read | Search property sources, read listings, viewings, open houses, collections and buyer requests |
brochures:read | List and read interactive brochures |
brochures:write | Create, edit, renew, revoke and delete interactive brochures |
documents:read | List and read documents in your library |
documents:write | Create and edit documents, share or revoke links, file them in folders, bin and restore them, attach them to leads and listings |
A tool whose scope the credential lacks is left out of tools/list and refused at call time. Creating a brochure, adding or refreshing a listing on one, and renewing one also need properties:read, because they read the listing from its source.
Who sees what
- Members reach only the leads assigned to them; organization admins reach the whole organization.
- Members see and change only the brochures they created; admins see the organization's.
- Documents follow the library: organization-wide and shared documents plus your own private ones, and everything for an admin. Anyone who can see a Team document can edit it; a private document only its creator or an admin. Sharing, moving, binning and deleting stay with the creator and admins.
- The admin tools (
set_lead_assignees,add_lead_assignees,bulk_assign_leads, every lead routing tool exceptset_routing_away, and every agency settings tool) are absent from a member's tool list. - The tools that change many leads at once (
bulk_update_lead_status,bulk_update_lead_tags,bulk_create_tasks,bulk_assign_leads) take 1 to 500 lead ids, never a filter, and answer how many changed, how many were already that way, and the ids left out. A member's change reaches only the leads they can see. list_duplicate_leadsfinds groups of leads sharing an email or phone (a member sees groups among the leads they can see), andmerge_leadsfolds up to 100 pairs of them (leadIdintointoLeadId) in one call. A merge cannot be undone and the kept lead keeps its own name, email and phone. A member merges two leads only when both are theirs; an admin, any two. One failing pair does not stop the others.- CRM write tools and every document tool need an active Fondaro subscription. Brochure tools do not.
Membership is checked on every request, with a role cache of about five minutes. Removing someone from the organization cuts off their keys and OAuth connections within that window.
Call a tool
Every POST is independent. With 2026-07-28, send these on each request:
| Header or field | Value |
|---|---|
Mcp-Protocol-Version | 2026-07-28 |
Mcp-Method | The JSON-RPC method |
Mcp-Name | The tool name, on tools/call |
params._meta | io.modelcontextprotocol/protocolVersion, io.modelcontextprotocol/clientInfo, io.modelcontextprotocol/clientCapabilities |
A missing or mismatched header returns a JSON-RPC error with HTTP 400. Do not send Mcp-Session-Id or Last-Event-ID.
Use server/discover (same headers, Mcp-Method: server/discover) to read the server's identity, and tools/list to read the tools you may call. The server advertises tools only: no prompts, resources or subscriptions. tools/list is sorted by name and carries a private five-minute cache hint, because it depends on the caller; never share one person's list with another.
Earlier protocol revisions
A client on 2025-11-25 or earlier may send initialize and plain JSON-RPC without the Mcp-* headers. No session is created, so tools/list and tools/call also work without a prior initialize. The tools, scopes and input schemas are the same.
Connect a client
| Client | Sign-in | Setup |
|---|---|---|
| ChatGPT | OAuth | Add Fondaro from its ChatGPT plugin page (or as a custom app with https://api.fondaro.com/mcp/v1), then sign in to Fondaro and choose Allow. |
| Claude | OAuth | Add Fondaro from Claude's directory (or as a custom connector with https://api.fondaro.com/mcp/v1), then sign in to Fondaro and choose Allow. |
| Claude Code | OAuth | Add the server without a header, open /mcp, choose Authenticate and sign in. |
| Codex CLI | API key | Point --bearer-token-env-var at a variable holding the key. |
| Cursor, Visual Studio Code | API key | Add the URL and an environment-backed Authorization header to your user-level MCP config. |
| Scripts | API key | Send Authorization: Bearer fdr_mcp_…. |
Keep a key out of config files, source control and shell history; reference an environment variable instead. The Fondaro MCP guide walks through each client. Every key and OAuth connection on your account is listed under Your connections on that page, where each can be revoked.
Manage keys
These endpoints take your dashboard session (Authorization: Bearer <session token>), not an fdr_mcp_ key.
POST /mcp-keys
Create a key for yourself.
| Field | Type | Required | Description |
|---|---|---|---|
name | string | Yes | 1 to 255 characters |
scopes | string[] | No | Any of the seven scopes, no repeats. Omit for all seven. |
expiresInDays | integer | No | 1 to 3650. Omit for a key that does not expire. |
key appears in this response only.
GET /mcp-keys
List keys, never with their value. A member sees their own; an admin sees every key in the organization.
DELETE /mcp-keys/:id
Revoke a key at once. Members revoke their own; admins revoke any. Answers { "success": true }.
Tools
131 tools. Writes marked entitled need an active subscription; admin tools are for organization admins only.
Leads
| Tool | Scope | Purpose |
|---|---|---|
list_leads | crm:read | List leads with filters, paginated |
list_sleeping_leads | crm:read | Your leads that went quiet (no contact and no reply for 14 to 365 days), newest replies first, each with why, whether a search is attached and which channels it has. Admins may pass assigneeId |
search_leads | crm:read | Fuzzy search by name, company name, email or phone |
get_lead | crm:read | One lead's contact details, tags, owners and totals |
get_lead_timeline | crm:read | A lead's activity: notes, tasks, calls, email, messages, viewings, documents |
get_lead_counts | crm:read | Number of leads in each pipeline stage |
list_tags | crm:read | The organization's tags, with lead counts |
list_org_members | crm:read | Members (id, name, email, role), for assigning |
list_org_teams | crm:read | Teams and their member ids, for assigning |
create_lead | crm:write, entitled | Create a lead, owned by you unless an admin names others |
update_lead_contact | crm:write, entitled | Change name, email, phone or company |
update_lead_status | crm:write, entitled | Move a lead to another stage |
set_lead_tags | crm:write, entitled | Replace a lead's tags |
save_lead_search | crm:write and properties:read, entitled | Save a property search for one of your leads across 1 to 5 sources; only homes that come in after now count as new in it |
set_lead_assignees | crm:write, admin | Replace a lead's owners |
add_lead_assignees | crm:write, admin | Add owners without removing any |
bulk_update_lead_status | crm:write, entitled | Move up to 500 leads to one stage |
bulk_update_lead_tags | crm:write, entitled | Add and remove tags on up to 500 leads; their other tags stay |
bulk_create_tasks | crm:write, entitled | Make the same task, yours, on up to 500 leads |
bulk_assign_leads | crm:write, admin | Replace or add the owners of up to 500 leads |
list_duplicate_leads | crm:read | Groups of leads sharing an email or phone, oldest first, as many as fit one answer |
merge_leads | crm:write, entitled | Fold up to 100 duplicate leads into the ones you keep; cannot be undone |
Lead routing
Routes are checked top to bottom; the first one that matches and has someone to give the lead to wins, then Smart routing, then Unassigned. See Lead routing.
| Tool | Scope | Purpose |
|---|---|---|
get_lead_routing | crm:read, admin | The routes in order, their people, Smart routing, problems and 30-day counts |
preview_lead_routing | crm:read, admin | Which route a lead would take and who gets it, without assigning it |
get_team_load | crm:read, admin | Who on the team is overloaded: leads waiting, new leads untouched for a day, tasks not done, who is away or at a daily cap |
create_lead_routing_rule | crm:write, admin | Add a route: conditions, people or live teams, how it shares leads, office hours, a daily cap |
update_lead_routing_rule | crm:write, admin | Change a route; fields you leave out stay as they are |
delete_lead_routing_rule | crm:write, admin | Delete a route |
reorder_lead_routing_rules | crm:write, admin | Put the routes in a new order |
set_smart_routing | crm:write, admin | Switch Smart routing on or off |
route_unassigned_leads | crm:write, admin | Route the leads waiting in Unassigned now (up to 500) |
set_routing_away | crm:write, entitled | Mark yourself (or, as an admin, anyone) away until a date |
Agency settings
What an agency admin changes in Settings. Every tool here is for admins; a member's call is refused. Changing the website's listing sources also needs an active Fondaro subscription. In Fondaro's assistant, every change waits for your approval. Billing, keys, integration credentials, phone numbers, the website's domain and publishing, connecting an inbox, team changes and switching calling on or off stay in the dashboard. See Agency settings for the fields.
| Tool | Scope | Purpose |
|---|---|---|
get_agency_branding | crm:read, admin | The agency's public profile: name, description, logos, icon, cover photo, brand colour, contact details, social profiles, address, languages, services, and whether automatic sales emails are on |
update_agency_branding | crm:write, admin | Change the public profile; fields you leave out stay as they are, and the agency must keep a name and both logos |
get_agency_ai_settings | crm:read, admin | Whether Fondaro's assistant is on for the agency, and what happens after a call |
update_agency_ai_settings | crm:write, admin | Switch the assistant on or off for the agency (on needs a plan), or change what happens after a call |
get_agency_inbox_intake | crm:read, admin | Who from outside the CRM reaches the Inbox, whether inboxes bring in past messages, whether people may share conversations |
update_agency_inbox_intake | crm:write, admin | Change any of the three, for every inbox of the agency |
get_agency_notification_channels | crm:read, admin | Where the agency's own email goes, and the address it goes to right now |
update_agency_notification_channels | crm:write, admin | Replace where the agency's email goes. The primary email is also the billing email on invoices and receipts |
get_agency_network_profile | crm:read, admin | The agency page's address on the agent network and who may read it |
update_agency_network_profile | crm:write, admin | Change the page's address or who may read it |
get_website_listing_sources | crm:read, admin | The sources the website lists homes from, every source it could list, and whether each is ready |
set_website_listing_sources | crm:write, entitled, admin | Replace the website's sources, in order (1 to 5); each must be connected |
Your notification settings
These act only on you, the person the key or sign-in belongs to. Nothing takes a user id.
| Tool | Scope | Purpose |
|---|---|---|
get_notification_settings | crm:read | Every switch for your own alerts: push and WhatsApp by kind (each with a plain description), Ring me first, where Fondaro is for you, learning, the call summary after every call, and the morning briefing time, days and zone |
update_notification_settings | crm:write, entitled | Change any of them; only the fields you send change, and an unknown kind is refused with the valid list. Turning learning off deletes what Fondaro learned of how you write. The briefing needs WhatsApp linked in this agency |
Queues
A queue is a saved view with lanes: who is in it, which lane a lead lands in (the first lane that matches wins), the order inside each lane, and whether everyone else shows last or not at all. You change or delete only queues you made; an admin also chooses who a queue is given to.
| Tool | Scope | Purpose |
|---|---|---|
list_queues | crm:read | The queues you can open, each in plain words and as a full definition |
get_queue | crm:read | One queue by id |
list_calls_due | crm:read | Who to call today: the people your morning briefing names, with why each is there. Your own lists, also for an admin |
preview_queue | crm:read | Lane counts and the first ten leads of each lane, with why each one is there, for a saved queue or an unsaved definition |
create_queue | crm:write, entitled | Create a queue; use $me as the owner to make it personal for whoever opens it |
update_queue | crm:write, entitled | Change a queue you made; fields you leave out stay as they are |
set_queue_audience | crm:write, entitled, admin | Set who a queue is given to, on any queue you can open: add, remove or replace people (list_org_members) and teams (list_org_teams). It goes into their Leads sidebar and a team includes people who join later |
delete_queue | crm:write, entitled | Delete a queue you made |
Inbox, calendar and tasks
| Tool | Scope | Purpose |
|---|---|---|
list_inbox | crm:read | Your Inbox in page order (Waiting, New or All) |
get_calendar | crm:read | Your meetings, viewings and tasks for up to 42 days in a time zone |
get_free_times | crm:read | Free slots of a given length, up to 14 days ahead |
update_event | crm:write, entitled | Move or edit one of your own meetings or viewings; anyone invited is told from your own calendar |
cancel_event | crm:write, entitled | Cancel one of your own meetings or viewings; it stays on record as cancelled and anyone invited is told |
record_viewing_feedback | crm:write, entitled | Record how a viewing went (loved, maybe or no): completes it, replaces an earlier answer and adds a note to its lead |
list_tasks | crm:read | Your tasks, or one lead's, oldest due first; only the overdue ones, or those due by today, if you ask |
create_task | crm:write, entitled | Add a task to a lead |
update_task | crm:write, entitled | Change title, description, due date or done state |
delete_task | crm:write, entitled | Delete a task |
Notes
| Tool | Scope | Purpose |
|---|---|---|
list_notes | crm:read | A lead's notes, newest first |
create_note | crm:write, entitled | Add a note to a lead |
update_note | crm:write, entitled | Change a note |
delete_note | crm:write, entitled | Delete a note (your own, or any as admin) |
Deals
| Tool | Scope | Purpose |
|---|---|---|
list_deals | crm:read | One lead's deals, or the 1,000 most recent deals with filters |
get_deal | crm:read | One deal with its commission participants |
create_deal | crm:write, entitled | Create a deal on a lead |
update_deal | crm:write, entitled | Change amount, listing, dates, commission, invoice or owner |
change_deal_stage | crm:write, entitled | Move a deal to another stage |
close_deal_won | crm:write, entitled | Mark a deal won |
close_deal_lost | crm:write, entitled | Mark a deal lost, with an optional reason |
reopen_deal | crm:write, entitled | Reopen a won or lost deal |
Calls, email and messages
| Tool | Scope | Purpose |
|---|---|---|
get_call_history | crm:read | A lead's calls: direction, outcome, duration, recorded caller |
get_call_transcript | crm:read | The stored transcript of a call |
get_call_analysis | crm:read | The stored call review: sentiment, objections, next steps |
list_call_analyses | crm:read | A person's analysed calls in a window, to coach them: sentiment, interest, objections, next steps and tips per call. Members read their own; admins any member's |
get_email_history | crm:read | A lead's email |
get_conversation | crm:read | A lead's WhatsApp, Instagram, LinkedIn and Telegram messages |
Search and records
| Tool | Scope | Purpose |
|---|---|---|
search_crm_semantic | crm:read | Find leads by meaning across notes, call transcripts and email |
match_leads_to_listing | crm:read | Leads whose history fits a listing |
resolve_records | crm:read | Summaries of up to 20 records of any kind, as you see them |
Properties
| Tool | Scope | Purpose |
|---|---|---|
list_property_sources | properties:read | Sources, whether each is connected, and the names of their facets. Pass source for one source's full facet detail |
list_property_search_options | properties:read | Exact values for one search facet |
autocomplete_location | properties:read | Resolve a place to ids for search_properties |
search_properties | properties:read | Search one source (Fondaro: your stock or the network) |
get_property | properties:read | Full detail for one listing |
find_similar_homes | properties:read | Up to 6 homes like one Fondaro listing, most alike first: your stock and other agencies' active listings, never the listing itself |
list_new_homes_in_search | properties:read | Up to 10 homes in one of your searches you have not seen yet, newest first |
resolve_listing_link | properties:read | One pasted property-portal listing link to the listing identity create_brochure takes, with its title, price, place and bedrooms |
list_viewings | properties:read | Registered viewings of your listings |
get_viewing | properties:read | One viewing |
list_open_houses | properties:read | Network open houses, or your own |
get_open_house | properties:read | One open house |
list_collections | properties:read | Listing collections you are in |
get_collection | properties:read | One collection and its homes |
list_buyer_requests | properties:read | Buyer requests on the network, or your agency's |
Interactive brochures
| Tool | Scope | Purpose |
|---|---|---|
list_brochures | brochures:read | Brochures you can see, newest first |
get_brochure | brochures:read | One brochure with its listing summaries and publicUrl |
create_brochure | brochures:write, properties:read | Create a brochure from 1 to 25 listings |
update_brochure | brochures:write | Change title, recipient, theme, accent or location visibility |
add_brochure_listing | brochures:write, properties:read | Add one listing (25 at most) |
remove_brochure_listing | brochures:write | Remove one listing |
reorder_brochure_listings | brochures:write | Set the full listing order |
refresh_brochure_listing | brochures:write, properties:read | Read one listing again from its source |
set_brochure_listing_location | brochures:write | Change one listing's address and coordinates |
update_brochure_listing_details | brochures:write | Override one listing's details and visibility |
revoke_brochure | brochures:write | Turn off the link, keeping the brochure |
renew_brochure | brochures:write, properties:read | Restore an expired or revoked link, optionally refreshing listings |
delete_brochure | brochures:write | Delete a brochure for good |
Pass property identities (source, id, optional country) exactly as search_properties or get_property returned them. Listing edits take the brochure-listing id from create_brochure or get_brochure.
Documents
All document tools are entitled.
| Tool | Scope | Purpose |
|---|---|---|
list_documents | documents:read | Documents you can see, most recently changed first |
list_document_folders | documents:read | Folders, with how many items you can see in each |
get_document | documents:read | One document with its Markdown body (a whiteboard as a plain-text outline) |
list_lead_documents | documents:read | Documents attached to a lead |
list_listing_documents | documents:read | Documents attached to one of your listings |
create_markdown_document | documents:write | Create a private Markdown document |
update_document | documents:write | Replace a document's title or body |
share_document | documents:write | Publish a link and return its shareUrl |
revoke_document_share | documents:write | Take the link down |
attach_document_to_lead | documents:write | Attach a document to a lead |
detach_document_from_lead | documents:write | Remove that attachment |
move_document | documents:write | File a document in a folder, or back at the top level |
bin_document | documents:write | Move a document to the bin, where it can be restored |
restore_document | documents:write | Bring a document back from the bin |
attach_document_to_listing | documents:write | Attach a document to one of your organization's own listings |
detach_document_from_listing | documents:write | Remove that attachment |
Attaching needs access to both the document and the lead, and is not a grant: a private document stays private. A listing must be one of your organization's own. Moving, binning and restoring are for the document's creator and admins. Binning is not deleting: a binned document can be restored for a while.
Help docs
How to use Fondaro, from these docs. Nothing here is your data, so the two tools need no subscription and no admin role.
| Tool | Scope | Purpose |
|---|---|---|
search_docs | crm:read | Up to 10 articles for a question, best first, each with the paragraph that matches |
get_doc | crm:read | One article as Markdown, by the path search_docs returned |
A long article comes back cut at a paragraph with truncated: true; the whole page is at its markdownUrl (every docs page also answers as Markdown at its URL plus .md). An unknown path answers DOCS_NOT_FOUND. From your own code, read the pages over HTTPS with no key: https://www.fondaro.com/llms.txt indexes them.
Results and paging
- Responses have a size budget. A long lead timeline returns the entries that fit, marks shortened text with
_preview, and givesnextOffset; continue fromnextOffset, not from your offset pluslimit.totalIsExact: falsemeans the total is a lower bound. get_call_historyacceptslimit(default 20, at most 100) andoffsetand answers{ calls, total, hasMore, nextOffset }. A history too large to return whole without them fails withCALL_HISTORY_PAGINATION_REQUIRED.- A call's
ownerIdis the person recorded as making or taking it, which can differ from the lead's current owners. search_crm_semantictakes a query of up to 500 characters and returns 1 to 30 matches (10 by default). An empty answer means nothing relevant is indexed, not that no such lead exists.list_tasksandlist_dealsanswer short rows a page at a time:limit(default 25, at most 100) andcursor, and the answer'snextCursorreaches the next page. A page also stops where the answer would outgrow the budget.truncated: truemeans more rows exist than the page holds. A task row's description is cut to 200 characters; a deal's import fields (externalId,importBatchId,sourceMetadata), collection and invoice fields and commission participants are onget_deal.list_taskstakesdue:overdue, orby_today(overdue or due by the end of today), counted intimeZone(an IANA zone such asEurope/Madrid; UTC when you give none). PasswithContact: trueand each row also says when its lead was last contacted:lastContactAt(the newest answered call, sent email that was not an automatic one, or outbound message, by anyone) andcontactedSince(that contact came after the task was created).- Other lists that would exceed the budget fail with an error rather than drop rows: ask for fewer results.
Limits and errors
| Limit | Value |
|---|---|
| Requests per key or OAuth connection | 120 per minute |
| Failed sign-ins per IP | 120 per minute |
| Property portal reads | 300 uncached portal calls per organization per UTC day |
When a limit is reached the server answers 429 with Retry-After. Once the portal allowance is spent, uncached portal reads return an error until midnight UTC; the Fondaro network and Resales Online keep working.
| Status | Meaning |
|---|---|
400 | Protocol headers missing or disagreeing with the body |
401 | Missing, unknown, revoked or expired credential (with a WWW-Authenticate challenge) |
403 | No longer a member of the organization, or the organization is disabled (code: "ORG_DISABLED") |
405 | GET or DELETE on the endpoint |
429 | Rate limit reached |
A tool refused for scope, role or access returns a JSON-RPC error with no data from the record.