Claude + Lofty (Chime): What the Integration Can (and Can't) Do in 2026
Yes, as of September 2026. Lofty shipped an official MCP server, and Claude can sign into it. Lofty (the real-estate CRM formerly called Chime) still isn’t in Claude’s connector directory, so you add it yourself as a custom connector: Lofty’s developer docs give the server address, mcp.lofty.com, and publish the client ID Claude needs to sign in. Behind it is a self-serve API covering leads, tasks, listings, transactions, and communications, with real-time webhook events (notifications the moment something changes). You generate your own API key under Settings → Integrations → API. But even connected, a Claude setup runs when you ask or on a schedule you set, never because something happened in Lofty: a scheduled task can check your pipeline every hour, but nothing reacts the moment a lead registers.
Here’s what’s actually available, the limits, and what to use if you want Lofty work that runs on its own.
The API is open, and Lofty now runs the connector itself
Unlike its closest competitor BoldTrail, Lofty doesn’t hide its API behind a partner tier. Any user can generate an API key under Settings → Integrations → API, and the API exposes leads, listings, tasks, and transactions, plus webhook notifications for real-time change events. (One housekeeping note: Lofty’s legacy API docs are being retired on August 1, 2026 in favor of developer.lofty.com — build against the new docs.) Lofty is also explicit that API keys should stay internal and not be handed to outside vendors, so this is a self-serve path for your own tooling.
Until September 2026 the bridge to Claude was the part you had to build. Lofty’s changelog for that month lists its MCP server release, so the bridge now comes from Lofty. One wrinkle: Lofty’s sign-in does not register new clients automatically, so Claude needs a client ID. Lofty publishes one for Claude and Claude Code in its developer docs, which is why this works in Claude and not in every assistant.
How you’d actually connect Claude to Lofty today
Two realistic paths:
- Lofty’s own MCP server. In Claude, go to Customize → Connectors, add a custom connector, and enter
https://mcp.lofty.com/mcpalong with the client ID Lofty’s developer docs list for Claude. Sign in to Lofty once and authorize. Claude then acts as the Lofty user who authorized it, and anything that sends a message asks you to confirm first. (MCP is just the standard these connectors are built on.) - Zapier as the bridge. Lofty supports Zapier, so Zapier can expose Lofty actions to Claude without your writing code, though each action still runs only when you prompt it or a scheduled task does.
Either way you end up with a set of Lofty actions Claude can run when you ask it to, or on a schedule you set. Adding a custom connector on claude.ai needs a paid Claude plan.
Lofty AI Assistant is not a Claude integration
Worth separating: Lofty ships its own AI. AI Assistant is Lofty’s built-in chatbot — it surfaces top-priority leads from natural-language questions, summarizes call recordings and suggests next steps, and drafts or rewrites messages for SMS, email, and social. That’s an in-product feature, and it doesn’t connect to your Claude account. “Lofty has AI” and “Lofty works with Claude” are different claims.
The limits that actually matter
Even with a working connection, the shape is “an assistant you operate,” not “an agent that runs.” Three limits define it:
- No triggers, no monitoring. Lofty’s webhooks can fire the moment a lead comes in or a task is due, but Claude runs when you ask or on a timer, and nothing in Lofty can start it. There’s nothing on Claude’s side to catch that event and act. No “when a new lead registers, text them and log the first touch.”
- On request or on a clock. Claude looks up a contact or drafts a follow-up when you ask (or when a scheduled task runs); it doesn’t sit on your pipeline nurturing leads or working your task list as things change.
- A timer, not a trigger. Claude’s scheduled tasks fire on a fixed clock you set, not the instant a lead registers or a task comes due. That’s not an always-on, event-driven lead-response agent — the one thing speed-to-lead actually rewards.
And on email: Claude’s Gmail connector asks you to approve every send, and its Outlook add-in doesn’t send at all, so the last click is still yours. So Claude is good for “draft a follow-up to this lead and add a task” and not built for “respond to every new lead within a minute, day and night.”
If you want Lofty work that runs on its own: Carly
The moment you want something to happen around Lofty because something happened (text a new lead the instant they register, log the first touch, work a task the moment it comes due), you’ve crossed past what Claude is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers. Paste your Lofty API key into Carly on the integrations page, and Carly works the API and webhooks for you:
- When a new lead registers, Carly texts and emails them within the minute and logs the first touch, inside the speed-to-lead window an hourly schedule can’t hit.
- When a lead replies to a nurture message, Carly reads the thread, drafts and sends the response, and flags a hot lead for a call.
- When a task comes due, Carly works it — sends the follow-up, updates the record — instead of letting it sit overdue.
- On a listing status change, Carly notifies the interested buyers and updates the contacts tied to that property.
Free Zapier-style workflows; AI agents from $35/month. Carly connects to thousands of apps, and Lofty is one of them. See integrations.
Claude vs Carly for Lofty
| Claude (with Lofty’s MCP server) | Carly | |
|---|---|---|
| Look up leads & tasks | Yes | Yes |
| Draft follow-up emails | Yes | Yes |
| Acts on Lofty triggers / events | No | Yes |
| Responds to new leads on its own | No | Yes |
| Has its own inbox to receive work | No | Yes |
| Sends the emails itself, not just drafts | No, every send waits on your approval | Yes |
| What it takes to set up | Add a custom connector with Lofty’s client ID | Paste your Lofty API key |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude with Lofty’s connector is a Lofty lookup inside a chat. Carly is a teammate that responds to leads as they arrive.
Frequently Asked Questions
Does Claude work with Lofty (Chime)?
Yes. Lofty released an official MCP server in September 2026 and publishes a client ID for Claude, so you can add it under Customize → Connectors as a custom connector. It isn’t in Claude’s connector directory, and it runs when you ask or on a schedule, never on a Lofty event.
Is the Lofty API self-serve?
Yes. You generate an API key under Settings → Integrations → API, and the API comes with webhook notifications for real-time events. Note the legacy docs retire on August 1, 2026 — build against developer.lofty.com.
Isn’t Lofty’s AI Assistant a Claude integration?
No. AI Assistant is Lofty’s own in-product chatbot for finding leads, summarizing calls, and drafting messages. It doesn’t connect to your Claude account.
What if I want Lofty to act on its own — respond to leads, work my tasks?
That’s outside what Claude does; it runs when you ask or on a schedule and doesn’t act on webhooks. Carly fires on Lofty events and schedules 24/7 in the cloud and can text new leads, log first touches, work overdue tasks, and send pipeline summaries. AI agents start at $35/month.
More: Claude connectors · Claude + Follow Up Boss · Claude + BoldTrail · Can Claude send emails · Claude vs Carly · Best AI CRM tools · ChatGPT + Lofty · Grok + Lofty
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
