Grok + Lofty (Chime): No Connector, and the Way In
Grok has no Lofty connector, built in or in its catalog. Your leads, tasks and transactions sit in Lofty (the CRM that used to be Chime), out of Grok’s reach. Add Carly to Grok once and Lofty comes with it, in the same chat as your mail and calendar.
Where Lofty sits against Grok’s connector list
Grok’s built-in connectors cover Gmail and Google Calendar, Google Drive, Outlook Mail and Calendar, Microsoft Teams, OneDrive, SharePoint and Salesforce. The catalog xAI publishes beside them adds Box, Canva, Gamma, GitHub, Linear, Meltwater, Notion, S&P Global and Vercel. Lofty is on neither list, and Grok Bot’s plugin repository has no Lofty entry either.
That gap lands on the part of the job that pays. Grok can read the inquiry that just hit your inbox. It cannot tell you whether that person is already in the database, which agent owns them, what the last text said, or whether anyone has called yet. You end up reading the answer in one window and typing the record into another.
Lofty did build an MCP server, with no sign-in for Grok
This is the part most write-ups get wrong, in both directions. Lofty has shipped a real one. Its developer site documents a hosted server at mcp.lofty.com, speaking Streamable HTTP, exposing eighteen tools that cover 123 REST operations across leads, activity timelines, tasks, transactions, listings, messaging and webhooks. Call it with no credential and it answers with a proper authorization challenge, so it is live, public and not a marketing page.
The catch is the sign-in. Lofty’s authorization server does not support Dynamic Client Registration, the step where a client introduces itself automatically. Lofty’s own documentation says applications are registered by hand in its vendor portal, which issues a client id, and that every authorize request still needs one. Lofty then prints the client ids it has registered for specific tools: there are published ones for Claude and for Claude Code, and an app in ChatGPT’s directory. There is no Grok entry among them.
Grok’s custom connector dialog takes a server URL and then hands you off to whatever sign-in the server asks for. There is nowhere in it to paste a client id. So the server exists, your Lofty account can reach it from other tools, and the one path into Grok is a custom connector that brings its own credentials. That is what Carly is.
Add Lofty to Grok through Carly
- In Lofty, go to Settings → Integrations → API and create an API key. The key is scoped to you, so it can only touch records you could touch yourself. Then paste it into Carly on the integrations page.
- In Grok, go to
grok.com/connectors, click New Connector, then choose Custom. - Enter
https://carlyassistant.com/mcp/and complete the sign-in. - Ask Grok about Lofty. The Carly connector answers with your live pipeline.
On Grok Business and Enterprise, a team admin provisions custom connectors in the cloud console before members can add them. In Grok Bot the same server goes in as a plugin: open Plugins from the sidebar, add https://carlyassistant.com/mcp/, and sign in. Your Cursor team’s MCP policy decides whether members can add servers of their own.
What Grok can do with Lofty once Carly is in
- “Which leads from the weekend have had no call or text yet, and who are they assigned to?”
- “Log the showing on Alameda Street with Emily Brooks and set a follow-up task for Thursday morning.”
- “Move the Harrison Avenue transaction to under contract and tell me what is still open on it.”
- “Michael Reeves toured two listings last month and went quiet. Show me the whole thread and draft something worth sending.”
With Grok’s Gmail or Outlook connector sitting beside the Carly connector, the inquiry email and the lead record land in the same answer, which is the thing a second browser tab never does.
Lofty’s own AI is not a Grok integration
Lofty sells a stack of AI under its own roof, and it is easy to mistake for an integration. Cowork handles day-to-day operations inside the CRM. Sales Agent is a virtual ISA that works inbound leads around the clock and books appointments. Social Agent posts and generates leads across social. Homeowner Agent works your past database for seller opportunities. Custom Agents let you build one for a repetitive job of your own.
All of it is good at what it does, and all of it runs inside Lofty. None of it connects to your Grok account, reads your inbox, or answers you in a Grok chat. “Lofty has AI” and “Lofty works with Grok” are two different sentences.
The Lofty work that happens after the chat closes
A connector answers when you ask. Nothing in Grok watches Lofty.
Grok was the first big assistant to react to an event rather than a clock, and the event is always an email. Automations fire on a schedule, or on an inbox match by sender, recipient, or subject, with email triggers reserved for SuperGrok. No other app can start one. Carly's triggers reach past the inbox, to a booking arriving, a form coming in, or a record changing in the apps you already use.
Real estate runs on events, not on questions. A lead registers on the IDX site and the first reply has to go out inside a minute, not whenever someone next opens a chat. A showing gets booked and the confirmation plus the calendar hold should follow on their own. A task goes overdue and somebody should be working it. A listing changes status and the buyers whose saved searches match it should hear about it.
Carly is the part that watches for those and starts the work. It holds your Lofty key, sends the first response from the right mailbox, logs the touch, and keeps going when every window is closed. Carly connects to thousands of apps, so the same connector that brings Lofty into Grok also reaches Gmail, Outlook, your calendars and your booking pages, all of them behind one sign-in. Free Zapier-style workflows; AI agents from $35/month. Get started at carlyassistant.com.
Grok alone vs Grok with Carly
| Grok alone | Grok + Carly | |
|---|---|---|
| Reaches Lofty from a chat | No documented path | Yes |
| Looks up leads, tasks and transactions | No | Yes |
| Reads a lead’s call, text and email history | No | Yes |
| Works the same way in Grok Bot | No | Yes |
| Starts when a new lead registers | No, a connector answers when asked | Yes |
| Sends the first reply while you are at a showing | No, it waits for you in the chat | Yes |
| Keeps running with the chat closed | No | Yes |
| Mail, calendar and CRM in one answer | Separate connectors, separate sign-ins | Yes, behind one |
| Setup | An OAuth client registered by hand in Lofty’s vendor portal | Paste an API key, add one URL |
What people report going wrong with Grok’s custom connectors
Custom connectors are young, and two public reports are worth reading before you lean on one. An issue opened on GitHub on 6 September 2026, against the Unraid MCP plugin, describes exactly the failure this page is about: the author wanted Grok’s custom connector to sign in through OAuth, discovery worked, and the flow died at Dynamic Client Registration when the server rejected Grok’s own callback address. The author’s summary is that Grok’s interface supports only OAuth with PKCE and dynamic registration, and cannot attach a fixed token instead. The issue is still open.
Separately, a thread on Cursor’s community forum opened on 14 August 2026 describes custom MCP servers in Grok Bot hanging and taking every other connector down with a deadline error, while staying invisible in the Plugins screen so they could not be removed. More than twenty people reported the same thing before Cursor shipped a fix on 7 September.
If a connection stalls, remove it at grok.com/connectors and add it again before assuming the server is at fault.
FAQ
Does Grok have a Lofty connector?
No. Lofty is not among Grok’s built-in connectors (Gmail, Google Calendar, Google Drive, Outlook, Teams, OneDrive, SharePoint and Salesforce) and it is not in the catalog. The way in is a custom connector, and Carly’s is https://carlyassistant.com/mcp/.
Lofty has an MCP server. Can I just paste that URL into Grok? The server is real and public, but its sign-in expects a client id registered in Lofty’s vendor portal, and Lofty publishes those for specific tools rather than for Grok. Grok’s custom connector dialog has no field for one. Carly’s connector brings its own credentials, so there is nothing to register.
Where do I find my Lofty API key? Under Settings → Integrations → API. The key is scoped to your user, so anything it does in Lofty is something you could have done yourself.
Can Grok Bot work with Lofty?
Not through a plugin of its own, because Grok Bot’s plugin list has no Lofty entry. Add Carly as a plugin with https://carlyassistant.com/mcp/ and Grok Bot reaches Lofty through it.
More: Grok connectors · Grok Bot · Claude + Lofty · ChatGPT + Lofty · Grok + Follow Up Boss
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."
