Connect Follow Up Boss to Claude, ChatGPT, and any MCP client
The real answer to whether you can connect Follow Up Boss to your AI, with the tool list and the safety model out in the open.
Every system here gets an honest, affirmative path: verified and instant, buildable and provisioned, human-assisted, or a done-for-you conversation. Zero dead ends.
Where Follow Up Boss stands today
Pipelines, contacts, deals, and activity history: the context an assistant needs at hand when you ask about your book of business.
Also searched as followup boss, fub. The vendor's developer documentation lives at www.followupboss.com.
What a Follow Up Boss connector would expose
The proposal you review during intake, separated into Read and Write. Nothing writes without asking you first.
Extracted from the vendor's API docs and human-reviewed before going live. Writes start one notch stricter.
- search_contacts
Find contacts by name, email, company, or owner
- get_contact
Fetch one contact with its full field set
- list_deals
List deals filtered by stage, owner, or close date
- list_activities
List calls, emails, and notes on a record
- create_contactconfirm
Create a new contact record
fields: name, email, phone, company
- update_deal_stageconfirm
Move a deal to another pipeline stage
fields: stage, probability
- add_noteconfirm
Attach a note to a contact or deal
fields: body
- delete_contactdestructivedry-run
Permanently delete a contact record
fields: id
Every write asks first: it pauses on a preview of the exact change and runs only when you approve it, before anything reaches Follow Up Boss. Turn off anything you never want your AI to touch.
From "Follow Up Boss" to a working connector URL
Designed for operators, not developers. You never read API docs, manage tokens, or touch a line of code.
- 01
Name it
A 30-second eligibility check confirms your AI client accepts a custom connector URL, then you pick the software. This page pre-fills that step.
- 02
Describe what you need
Plain language, not configuration. What should the assistant be able to look up, and what should it be able to change?
- 03
Review your Connector Blueprint
The exact Read and Write tool list, before you pay anything. Every write ships on in confirm mode and asks before it runs, every tool is individually toggled, and anything destructive carries a distinct warning.
- 04
Deploy and paste the URL
You get a hosted connector URL plus paste-in instructions matched to your AI client, and a live test panel that confirms the connection.
Follow Up Boss runs as a one-account connector
Follow Up Boss supports a single credential, so the connector runs in Solo mode: it acts as one account and says so in plain language at auth time and in the dashboard. megamcp's own activity log still separates who did what by connection token.
You paste an API key generated in Follow Up Boss. It is encrypted at rest, sent only to Follow Up Boss's API, and destroyed within 24 hours if you cancel.
Write access to Follow Up Boss your IT team will approve
Reads run free; every write pauses on a preview a human approves, and every call is recorded in a per-connector activity log with redaction controls.
Confirm mode
Enabled writes run through Multi Round-Trip Requests: the tool pauses, shows a human-readable preview of the exact change, and only proceeds with approval. Nothing reaches Follow Up Boss on the model's intent alone.
Guardrails
Any tool can be turned off. Field-level constraints restrict what can be touched, per-tool rate limits are enforced at the gateway edge, and destructive operations ship in dry-run, demonstrating what they would do until you graduate them.
Activity log
Every tool call is logged: who, what, when, result. Write actions and confirmations are highlighted, redaction controls decide how much argument data is stored, and the log is append-only, with updates and deletes refused by the database.
Connecting Follow Up Boss: the specifics
Can my AI assistant write to Follow Up Boss?
Yes, with guardrails. Write tools work out of the box in confirm mode: every write asks first, pausing on a preview of the exact change before anything reaches Follow Up Boss. Destructive operations ship in dry-run and never execute until you graduate them, and you can turn off any tool you never want touched.
Is it safe to connect Follow Up Boss to an AI assistant?
Safety is the architecture, not a setting. Every write asks first: it pauses on a human confirmation with the exact change previewed before it reaches Follow Up Boss. Destructive operations demonstrate in dry-run and never execute until you graduate them, any tool can be turned off, and every call lands in an activity log with redaction controls.
If my team uses a Follow Up Boss connector, whose name is on the actions?
Follow Up Boss supports a single credential, so the connector runs in Solo mode and discloses it plainly: the connector acts as one account, stated at auth time and in the dashboard. megamcp's own activity log still preserves per-connection traceability, because every connection has its own token.
Which AI clients work with a Follow Up Boss connector?
Any client that accepts a remote MCP connector URL: Claude (Free, Pro, Max, Team, and Enterprise), ChatGPT on paid plans with developer mode enabled, Cursor, and other MCP-compatible clients. Team and Enterprise workspaces may need an admin to allow custom connectors first.
How long until a Follow Up Boss connector is live?
Typically 24 to 72 hours. The mapping is generated from the Follow Up Boss API documentation and human-reviewed before it goes live.
Anything specific to the Follow Up Boss API worth knowing?
Yes. From our index notes on Follow Up Boss: Real-estate CRM. API is real; exact docs subdomain not verified, so docs_url points at the vendor root.
More CRM systems
Same category, same connector quality. Every one gets an honest verdict.
Connect Follow Up Boss. We take it from there.
Start a 14-day free trial, no card: live reads plus 3 supervised writes, each executed only after you approve it.