Search Follow Up Boss leads, review calls and deals, and add notes, tasks and deal updates. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"follow-up-boss": {
"url": "https://follow-up-boss.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"follow-up-boss": {
"type": "http",
"url": "https://follow-up-boss.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Follow Up Boss API key.
Find it in Follow Up Boss → Admin → API. Every user has their own key, with exactly the permissions of that user (an agent key sees only that agent’s contacts; a broker or owner key sees the whole account). Your key is used only to call the Follow Up Boss API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Follow Up Boss API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Follow Up Boss connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
fub_get_identity | read | Get identity Who the credential belongs to: the account (id, domain, owner) and the authenticated user. A cheap way to confirm the API key works. FUB: GET /v1/identity. |
fub_search_people | read | Search people (contacts/leads) Search contacts and leads. Criteria combine with AND. Name filters are partial matches. Newest first by default. People in the Trash stage are excluded unless includeTrash is true. Not every field is returned by default — pass `fields` (e.g. "allFields" or a comma list) for more. FUB: GET /v1/people. |
fub_get_person | read | Get one person Fetch one contact by id. Pass fields="allFields" to include custom fields and everything else. FUB: GET /v1/people/{id}. |
fub_check_duplicate_person | read | Check whether a person exists Check if a contact with this email or phone already exists anywhere in the account (even ones this user cannot see) and who it is assigned to. Use before adding a lead. FUB: GET /v1/people/checkDuplicate. |
fub_list_events | read | List lead events Lead activity: registrations, inquiries, viewed/saved properties, website visits, etc. Filter by person or type. Some events are only visible in the FUB app. FUB: GET /v1/events. |
fub_list_calls | read | List calls Logged phone calls with outcome, direction and duration. Filter by person or number. FUB: GET /v1/calls. |
fub_list_text_messages | read | List text messages Text messages for a person or a phone number (message bodies may be hidden by FUB for privacy). FUB: GET /v1/textMessages. |
fub_list_tasks | read | List tasks Tasks (follow-ups, calls, showings…). Filter by person, assignee, type, completion, or due window (due="today"|"overdue"|"upcoming"). FUB: GET /v1/tasks. |
fub_list_appointments | read | List appointments Calendar appointments with invitees, type and outcome. Filter by person, user, or a start+end window (both required together). FUB: GET /v1/appointments. |
fub_list_deals | read | List deals Deals (transactions) with stage, price, people, agents and commission. Filter by pipeline, user, person or status. The response metadata includes totalByStageId. FUB: GET /v1/deals. |
fub_list_pipelines | read | List deal pipelines Deal pipelines with their stages (the stage ids that fub_create_deal / fub_update_deal take). FUB: GET /v1/pipelines. |
fub_list_stages | read | List contact stages Contact lifecycle stages (Lead, Nurture, Past Client, Trash…) with people counts — the names fub_search_people and fub_update_person take as "stage". FUB: GET /v1/stages. |
fub_list_users | read | List users (agents) Users in the account (agents, brokers, lenders) — the ids to assign people, tasks and deals to. FUB: GET /v1/users. |
fub_list_custom_fields | read | List custom fields The account's contact custom fields: label, API name (customXxx), type and dropdown choices. Use the name as a key in customFields. FUB: GET /v1/customFields. |
fub_list_action_plans | read | List action plans The account's action plans (drip campaigns): id, name and status. Gives the names for the actionPlanId values of fub_list_person_action_plans. FUB: GET /v1/actionPlans. |
fub_list_person_action_plans | read | List action plans applied to people Which people are on which action plan, with the status of each assignment (e.g. "Running", "Paused"). Give personId for one contact's plans, or actionPlanId for everyone on one plan. For many contacts, list each active plan's people (limit 100; page with offset until _metadata.total is covered) instead of one call per contact. Shows classic action plans only; Automations 2.0 are in fub_list_person_automations when that tool is listed. FUB: GET /v1/actionPlansPeople. |
fub_lead_source_report | read | Lead source report by agent Count leads from lead sources (e.g. Zillow) per assigned agent, how many reached the closed stage(s) (conversion rate), and leads per lender user (e.g. Zillow Home Loans loan officers). Use it to count instead of paging through fub_search_people. The numbers approximate FUB's in-app Lead Source report, which has no API, and cover only the people the API key can see (use an owner, admin or broker key for the whole account). At most 100 FUB requests per call (one per count). FUB: GET /v1/people totals, GET /v1/users. |
fub_send_lead_event | write | Send in a lead / lead event Add a new lead or record activity on an existing one — FUB's documented way to create leads. FUB de-duplicates by email/phone (or use person.id to target a contact), routes the lead per Lead Flow, notifies the agent and runs action plans for Registration / Inquiry types. A 204 means the lead flow for this source is archived and the event was ignored. FUB: POST /v1/events. |
fub_update_person | write | Update a person Update a contact's fields. CAUTION: `tags` REPLACES all tags unless mergeTags is true; `phones` and `emails` REPLACE the full list (send existing ones too). Setting contacted=true pauses action plans. source/sourceUrl cannot be changed after creation. FUB: PUT /v1/people/{id}. |
fub_add_note | write | Add a note Add a note to a contact's timeline. FUB: POST /v1/notes. |
fub_log_call | write | Log a call Record a phone call made or received outside FUB, with its outcome. Does not place a call. FUB: POST /v1/calls. |
fub_create_task | write | Create a task Create a task on a contact, assigned to a user (assignedUserId or assignedTo is required). FUB: POST /v1/tasks. |
fub_update_task | write | Update a task Update a task — mark it complete, rename, retype or reassign it. FUB: PUT /v1/tasks/{id}. |
fub_create_deal | write | Create a deal Create a deal in a pipeline stage (stage ids from fub_list_pipelines). Include userIds — a deal with no users is invisible to agents. FUB: POST /v1/deals. |
fub_update_deal | write | Update a deal Update a deal — move it to another stage, change price, dates, people or agents. peopleIds/userIds replace the full list. FUB: PUT /v1/deals/{id}. |
fub_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
fub_request_feature | Request a missing feature Tell usefulapi that the user needs something the Follow Up Boss tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
fub_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Follow Up Boss (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
fub_cancel_subscription | Cancel the Pro subscription Cancel the caller's Follow Up Boss Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run fub_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Follow Up Boss server only. Subscribe with fub_upgrade (it returns a Stripe Checkout link). Cancel any time with fub_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running fub_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Follow Up Boss. The server calls the Follow Up Boss API with your own Follow Up Boss access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Follow Up Boss API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Follow Up Boss API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Follow Up Boss API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Follow Up Boss.
Yes, if you approve it. 8 of the 25 Follow Up Boss tools can create or change data. The other 17 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Follow Up Boss server only. Cancel any time: Pro then runs to the end of the paid period. Run fub_usage_status to see how many calls you used.
Ask the AI to run fub_upgrade: it returns a Stripe Checkout link. To cancel, run fub_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with fub_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.