Full read-write Claude connector for Follow Up Boss
Make Claude log activity and update lead stages in Follow Up Boss
Stop tabbing between screens to log a call or move a lead. Claude logs notes and activity, updates the stage, creates and assigns tasks, and applies tags right inside the lead record, with destructive actions waiting for your approval.
Follow Up Boss is a real estate CRM that agents and teams run their lead follow-up from. Teams want Claude to do more than read a contact: to log activity, update stages, and create tasks inside the right lead record.
What is a Follow Up Boss MCP server?
A Follow Up Boss MCP server is a small hosted service that exposes Follow Up Boss's data and actions to Claude over the Model Context Protocol, so Claude can industry-specific platforms inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.
What can Follow Up Boss's current connector do today?
Today, Follow Up Boss does not offer a first-party Claude connector, and we are not aware of an official Follow Up Boss MCP server to point to. Reaching it from Claude means a custom integration against the Follow Up Boss API. A purpose-built connector can add scoped read and write actions, so Claude works inside the lead record rather than beside it.
What does full read-write Follow Up Boss access unlock?
Full read-write Follow Up Boss access lets Claude log notes and calls, update a lead's stage, create and assign tasks, add or update contact details, and apply tags. The follow-up logging and pipeline upkeep that used to mean tabbing between screens happen where the lead already lives.
- Log a note, call, or activity entry on a lead record
- Update a contact's stage as it moves through the pipeline
- Create and assign a follow-up task to an agent
- Add or correct a contact's phone, email, or details
- Apply or remove tags to organize and segment leads
- Find every contact matching a query and propose batched updates
Can Claude log notes and calls in Follow Up Boss?
Yes. With a custom read-write connector, Claude logs notes, calls, and activity entries directly on the right lead record, so follow-up history lands where the lead already lives. Each write tool is scoped to the permissions you grant, and Claude never reaches a contact your account cannot.
Can Claude update a lead's stage and create tasks in Follow Up Boss?
Updating a lead's stage and creating tasks both work through the connector. Claude can move a contact through the pipeline, create and assign a follow-up task to an agent, add or correct phone and email details, and apply or remove tags, all inside the existing lead record.
Will Claude change or delete records in Follow Up Boss without my approval?
No. Read and write tools stay separate, and destructive actions like deleting a record are gated behind your confirmation. Claude can prepare an update or draft a note, but those steps only commit after you approve them. You decide which actions run automatically and which need a confirmation step.
How a Follow Up Boss connector works
We build a small MCP server that authenticates to Follow Up Boss through scoped API access using the narrowest permissions the work needs. Read tools (search, read contact) and write tools (log note, update stage, create task) are separated, and outbound or destructive actions like sending or deleting require your confirmation. Claude never has more access than the Follow Up Boss account it runs under, and we can add IP allowlisting where your setup supports it.
Frequently asked questions
Can Claude log activity and update stages in Follow Up Boss, not just read a contact?
Will Claude change records or send things from Follow Up Boss without my approval?
Is lead data safe, and does the connector get more access than I have?
Related connectors
Tell us what you run. We'll build the connector.
Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.