Follow Up Boss MCP by usefulapi is an MCP server with 25 tools an agent can call, among them fub_add_note, fub_check_duplicate_person, fub_create_deal. It answers at https://follow-up-boss.usefulapi.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 29 September 2026; the last check, on 15 November 2026, succeeded.
Search Follow Up Boss leads, review calls and deals, and add notes, tasks and deal updates.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
fub_add_note | Add a note to a contact's timeline. FUB: POST /v1/notes. Inputs: personId, subject, body, isHtml |
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. Inputs: email, phone |
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. Inputs: name, stageId, description, peopleIds, userIds, price |
fub_create_task | Create a task on a contact, assigned to a user (assignedUserId or assignedTo is required). FUB: POST /v1/tasks. Inputs: personId, assignedUserId, assignedTo, name, type, isCompleted |
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_get_person | Fetch one contact by id. Pass fields="allFields" to include custom fields and everything else. FUB: GET /v1/people/{id}. Inputs: id, fields |
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_p Inputs: sources, createdAfter, closedStages, userIds, includeLenders |
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. Inputs: status, ids, sort, limit, offset |
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. Inputs: personId, userId, start, end, limit, offset |
fub_list_calls | Logged phone calls with outcome, direction and duration. Filter by person or number. FUB: GET /v1/calls. Inputs: personId, phone, toNumber, fromNumber, limit, offset |
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. Inputs: label, limit, offset |
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. Inputs: pipelineId, userId, personId, status, includeArchived, includeDeleted |
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. Inputs: personId, type, hasProperty, propertyAddress, limit, offset |
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 Inputs: personId, actionPlanId, limit, offset |
fub_list_pipelines | Deal pipelines with their stages (the stage ids that fub_create_deal / fub_update_deal take). FUB: GET /v1/pipelines. Inputs: name |
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. Inputs: sort, limit, offset |
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. Inputs: personId, assignedUserId, assignedTo, name, type, isCompleted |
fub_list_text_messages | Text messages for a person or a phone number. This tool needs personId, toNumber or fromNumber (find the person with fub_search_people first). Message bodies may be hidden by FUB for privacy. FUB: GET /v1/textMessages. Inputs: personId, toNumber, fromNumber, limit, offset |
fub_list_users | Users in the account (agents, brokers, lenders) — the ids to assign people, tasks and deals to. FUB: GET /v1/users. Inputs: role, name, email, sort, limit, offset |
fub_log_call | Record a phone call made or received outside FUB, with its outcome. Does not place a call. FUB: POST /v1/calls. Inputs: personId, phone, isIncoming, note, outcome, duration |
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 Inputs: name, firstName, lastName, email, phone, stage |
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 fo Inputs: type, source, system, message, description, occurredAt |
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}. Inputs: id, name, stageId, description, peopleIds, userIds |
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 afte Inputs: id, mergeTags, firstName, lastName, stage, contacted |
fub_update_task | Update a task — mark it complete, rename, retype or reassign it. FUB: PUT /v1/tasks/{id}. Inputs: id, isCompleted, name, type, personId, assignedUserId |
Every block below points at https://follow-up-boss.usefulapi.io/mcp. Pick your client and copy.
claude mcp add --transport http follow-up-boss-mcp-by-usefulapi https://follow-up-boss.usefulapi.io/mcp
{
"mcpServers": {
"follow-up-boss-mcp-by-usefulapi": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://follow-up-boss.usefulapi.io/mcp"]
}
}
}{
"mcpServers": {
"follow-up-boss-mcp-by-usefulapi": {
"url": "https://follow-up-boss.usefulapi.io/mcp"
}
}
}{
"servers": {
"follow-up-boss-mcp-by-usefulapi": {
"type": "http",
"url": "https://follow-up-boss.usefulapi.io/mcp"
}
}
}{
"context_servers": {
"follow-up-boss-mcp-by-usefulapi": {
"url": "https://follow-up-boss.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"follow-up-boss-mcp-by-usefulapi": {
"serverUrl": "https://follow-up-boss.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"follow-up-boss-mcp-by-usefulapi": {
"url": "https://follow-up-boss.usefulapi.io/mcp"
}
}
}name: Follow Up Boss MCP by usefulapi
version: 0.0.1
schema: v1
mcpServers:
- name: Follow Up Boss MCP by usefulapi
type: streamable-http
url: https://follow-up-boss.usefulapi.io/mcp{
"mcpServers": {
"follow-up-boss-mcp-by-usefulapi": {
"httpUrl": "https://follow-up-boss.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"follow-up-boss-mcp-by-usefulapi": {
"type": "http",
"url": "https://follow-up-boss.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"follow-up-boss-mcp-by-usefulapi": {
"url": "https://follow-up-boss.usefulapi.io/mcp"
}
}
}goose://extension?url=https%3A%2F%2Ffollow-up-boss.usefulapi.io%2Fmcp&type=streamable_http&id=follow-up-boss-mcp-by-usefulapi&name=Follow%20Up%20Boss%20MCP%20by%20usefulapi
It answered our last check on 15 November 2026 in 203 ms. Over 4 checks since 29 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by usefulapi.io and served from follow-up-boss.usefulapi.io, the vendor's own domain: https://follow-up-boss.usefulapi.io/mcp.
25, as returned by the server's own tools/list on 18 November 2026: fub_add_note, fub_check_duplicate_person, fub_create_deal, fub_create_task, fub_get_identity, fub_get_person, fub_lead_source_report, fub_list_action_plans, and 17 more.
It answered our last check on 15 November 2026 in 203 ms. Over 4 checks since 29 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://follow-up-boss.usefulapi.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.usefulapi. Endpoint host: follow-up-boss.usefulapi.io. ARD identifier: urn:air:io.usefulapi:mcp:follow-up-boss.
First indexed 29 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.