Follow Up Boss MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Docs, sheets & office work

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://follow-up-boss.usefulapi.io/mcp

claude mcp add --transport http follow-up-boss https://follow-up-boss.usefulapi.io/mcp

{
  "mcpServers": {
    "follow-up-boss": {
      "url": "https://follow-up-boss.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "follow-up-boss": {
      "type": "http",
      "url": "https://follow-up-boss.usefulapi.io/mcp"
    }
  }
}

https://follow-up-boss.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

• fub_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

  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_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

  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

  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

  Logged phone calls with outcome, direction and duration. Filter by person or number. FUB: GET /v1/calls.

• fub_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

  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

  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

  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

  Deal pipelines with their stages (the stage ids that fub_create_deal / fub_update_deal take). FUB: GET /v1/pipelines.

• fub_list_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

  Users in the account (agents, brokers, lenders) — the ids to assign people, tasks and deals to. FUB: GET /v1/users.

• fub_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

  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

  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.to

• fub_lead_source_report

  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-

• fub_send_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 me

• fub_update_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

  Add a note to a contact's timeline. FUB: POST /v1/notes.

• fub_log_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

  Create a task on a contact, assigned to a user (assignedUserId or assignedTo is required). FUB: POST /v1/tasks.

• fub_update_task

  Update a task — mark it complete, rename, retype or reassign it. FUB: PUT /v1/tasks/{id}.

• fub_create_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

  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}.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 128 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 25 tool descriptions and found no hidden instructions to the AI

Compared with others in Docs, sheets & office worki

• More stars than 0% of the other 2197 servers in this category
• Published to the registry more recently than 96% of the other 2197 servers in this category
• Basic checks equal to or better than 100% of the other 2197 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{