MCP Server
Released the Lofty MCP server — connect Claude, ChatGPT, or any other Model Context Protocol client to the Lofty API with nothing to install and no generated SDK:search_leads / manage_leads, search_lead_activities (notes, calls, texts, emails and the unified timeline), search_tasks / manage_tasks (tasks and calendar events together), search_transactions / manage_transactions, search_listings, search_sales_agent / manage_sales_agent, send_message (to a lead) and notify_agent (to a teammate), search_team_config / manage_team_config, search_webhooks / manage_webhooks, and search_lead_insights / generate_lead_insight.One naming rule covers the whole surface: a tool whose name starts with search_ never writes. Writes past a risk threshold do not execute straight away — they return a confirmation token first, which is single-use, valid for five minutes, and bound to those exact arguments.Authentication uses your existing credentials — an API key or an OAuth 2.0 access token, with nothing to register specifically for MCP. Note that the MCP transport requires Authorization: Bearer <token> for both kinds, including API keys, which use the token prefix on the direct REST API. Calls run as the authenticated caller under the same permissions, scopes, and rate limits as a direct REST request.See the MCP Server documentation to get connected.Lofty app in ChatGPT
Lofty is now published in the ChatGPT app directory. Search for Lofty and install it — there is no URL to paste, noclient_id, and no API key; ChatGPT sends you to Lofty to sign in on first use. It runs on the same MCP server as every other client, with the same tools and the same permissions.See Connect your client for this and every other client.How updates reach you
Tool calls always run against the live server, so a fix to what a tool does takes effect as soon as it is deployed. Tool definitions — names, descriptions, parameter schemas — refresh on a schedule the client controls, not ours, so an improved parameter description can take a while to show up even though the behaviour behind it has already changed.In ChatGPT, the app directory keeps its own copy of the definitions taken when the app was published, and refreshes it when OpenAI re-scans this server and the new definitions pass its automated checks. Until then you see the previous descriptions.In Claude and other MCP clients, definitions are read when a connection is established, so a new session picks up the current set. This server does not advertisetools/listChanged, so a session already open does not update itself.Either way there is nothing to re-install or re-authorize, and connector links stay valid. Two changes would need action, and both would be announced here first: moving the server to a different URL, and any change to a tool that is not backward compatible.Leads — Saved searches
AddedGET /v1.0/leads/{leadId}/savedSearches — returns every saved property search of a lead, including its conditions and alert delivery settings.source— comma-separated origins to keep:AGENT_CREATED,LEAD_CREATED,SYSTEM_CREATED. Defaults to all. When migrating to another system, excludeSYSTEM_CREATED— the target usually generates its own, and importing ours duplicates the alerts.includeInactive(defaultfalse) — include searches whose alerts are switched off. AnINSTANTLYcadence counts as active, not off.
403 when the token’s user can’t access the lead.Fixes
- Tasks V2 / Calendar V2 —
startAt/endAtare now parsed correctly when the time zone is supplied separately astimeZoneCode. A bare ISO timestamp such as2026-03-01T15:00:00sent alongside atimeZoneCodepreviously failed to parse and returned HTTP500(20005); timestamps carrying their own offset were unaffected. An offset in the string still takes precedence overtimeZoneCode. - Time parameters — a timestamp that can’t be parsed now returns HTTP
400(20012 INVALID_PARAMETER), with a message naming the offending value and the expected format, instead of HTTP500(20005).