Connect Follow Up Boss to Claude Code

Make Claude log activity and update lead stages in Follow Up Boss. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Follow Up Boss to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Follow Up Boss, you add a Follow Up Boss MCP server: a small hosted service that exposes Follow Up Boss's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Follow Up Boss account. No API keys pasted into config files.

claude mcp add --transport http follow-up-boss https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Follow Up Boss once connected?

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

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Follow Up Boss access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Follow Up Boss API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Follow Up Boss changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Follow Up Boss connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Follow Up Boss connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Follow Up Boss account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Follow Up Boss's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Follow Up Boss?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Follow Up Boss account it signs in with. Revoking access is one click in Follow Up Boss.

More on the Follow Up Boss connector

Follow Up Boss connector for claude.ai MyCase + Claude Code PracticePanther + Claude Code Filevine + Claude Code

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.

Build my connector Talk to us