Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FUB_API_KEYYesYour Follow Up Boss API key, found in Admin > API.
FUB_SAFE_MODENoToggle between Safe Mode (default) and Full Access. Safe Mode prevents the ability to delete data. Set to 'true' for Safe Mode or 'false' for Full Access.true

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Follow Up Boss CRM tools. Answer common questions in ONE call:

  • New leads: listPeople stage="Lead" (newest created first by default). For "today" or "this week", read each person's created date and stop at the first one older than the start date.

  • Find a contact: getPersonByEmail for an email; listPeople name="First Last" or phone= otherwise.

  • Tasks: listTasks isCompleted=false with due="today" or due="overdue"; add assignedUserId for one agent, personId for one contact. Get your own user ID from getCurrentUser.

  • Appointments: listAppointments start= end=; add userId or personId to narrow.

  • Deals: listDeals with pipelineId, stageId, userId or personId. Stage and pipeline IDs come from listStages and listPipelines.

  • Notes: createNote personId + body. Tasks: createTask personId + name + dueDate (YYYY-MM-DD) + assignedUserId. Rules:

  • Stage filters on listPeople take the stage NAME; listStages gives this account's names.

  • updatePerson tags REPLACES all tags unless mergeTags=true. To remove one tag use removeTagFromPerson.

  • Lists return 10 rows unless limit is set (max 100). If _metadata.next is set, call again with next=.

  • Pass fields=id,name,stage,created,... to keep responses small.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
listEventsA

List events, newest first by FUB default. Filter by person, event type, or property.

createEventA

Create an event (lead registration, inquiry, page view). Dedupes the person by phone/email and creates them if new. Events older than 1 day count as historical and fire no workflows. 'Inquiry' becomes Property Inquiry if property is set, else General Inquiry.

getEventC

Get a single event by ID

listPeopleA

List/search people, newest created first by default. Custom-field filters: pass any custom* key (e.g. customClosingDate); dates: ',2026-01-01' = on or before, '2026-01-01' = on or after, 'a,b' = inclusive. Filter by name, email, phone, stage name, tags (ANY), owner, price, smart list.

createPersonA

Create a person. Custom fields: add top-level keys prefixed 'custom' (e.g. customClosingDate; see listCustomFields). Set deduplicate=true to avoid duplicates. source and sourceUrl can only be set here, not on update.

getPersonA

Get one person by ID. Pass fields=allFields or allCustom to include custom fields.

updatePersonA

Update a person. tags replaces all tags unless mergeTags=true; phones replaces all numbers. Custom fields: top-level 'custom*' keys; JSON null clears one. source/sourceUrl cannot be changed.

checkDuplicateC

Check if a person already exists by email or phone

listUnclaimedB

List unclaimed people (in ponds, not assigned)

claimPersonC

Claim an unclaimed person

createPersonAttachmentA

Attach an externally-hosted file to a person. "Restricted - Registered Systems Only": requires FUB_SYSTEM + FUB_SYSTEM_KEY env vars. uri must point to an externally hosted file — FUB does NOT host uploads via this endpoint (omitting URI returns 403).

getPersonAttachmentC

Get a person attachment by ID

updatePersonAttachmentB

Update a person attachment (externally hosted file). Needs registered-system credentials (X-System headers).

listRelationshipsA

List relationship contacts (spouse, partner, etc.), optionally for one person or by name.

createRelationshipA

Create a relationship contact (own record, e.g. Spouse) linked to a person. It is not a link between two existing people.

getRelationshipC

Get a relationship by ID

updateRelationshipA

Update a relationship contact. emails/phones/addresses arrays OVERWRITE existing values (empty array = unchanged). personId cannot be changed.

getIdentityA

Get identity/account information for the API key

getCurrentUserA

Get the current authenticated user (GET /me)

listNotesB

List notes, optionally filtered by personId

createNoteC

Create a note on a person.

getNoteC

Get a note by ID

updateNoteB

Update a note. Send only fields to change.

listCallsA

List calls, filterable by person or phone numbers.

createCallB

Log a call on a person. personId, phone, and isIncoming are required. userId can only be set by administrators (defaults to API user).

getCallB

Get a call by ID

updateCallA

Update a call record. Only calls created by the same API system/account can be updated.

listTextMessagesA

List text messages. FUB requires at least one filter: personId, phone, toNumber, fromNumber, threadId, sharedInboxId, groupTextId, participants or id.

createTextMessageA

LOG a text already sent by a registered SMS system; it does not send anything. Needs X-System credentials. personId, message, toNumber, fromNumber are all required.

getTextMessageB

Get a text message by ID

listUsersB

List users (agents, brokers, lenders). Filter by role, exact name, or email.

getUserC

Get a user by ID

listSmartListsA

List all smart lists. By default only classic FUB smart lists are returned. Pass all: true to also include smart lists created in the current FUB UI (otherwise modern smart lists are invisible).

getSmartListC

Get a smart list by ID

listActionPlansC

List action plans. Filter by status, names, or IDs.

listActionPlansPeopleC

List people assigned to action plans

addPersonToActionPlanB

Add a person to an action plan

updateActionPlanPersonC

Update a person's action plan status

listAutomationsB

List Automations 2.0 automations. Needs registered-system credentials and Automations 2.0.

getAutomationC

Get an automation by ID

listAutomationsPeopleB

List person/automation pairings. Needs registered-system credentials.

getAutomationPersonC

Get an automation-person entry by ID

addPersonToAutomationC

Add a person to an automation

updateAutomationPersonA

Pause or resume a person in an automation. Needs registered-system credentials.

listTemplatesC

List email templates

createTemplateB

Create an email template. Merge fields (e.g. %contact_first_name%) work only in subject and body.

getTemplateB

Get an email template by ID

updateTemplateB

Update an email template. Merge fields work only in subject and body.

mergeTemplateA

Merge an email template with a person's data and return the rendered email. Does not send anything.

listTextMessageTemplatesC

List text message templates

createTextMessageTemplateC

Create a text message template. Message text goes in message.

getTextMessageTemplateB

Get a text message template by ID

updateTextMessageTemplateC

Update a text message template. Message text goes in message.

mergeTextMessageTemplateA

Merge a text message template with a person's data and return the rendered text. Does not send anything.

listEmEventsC

List email marketing events (delivered, opened, clicked, etc).

createEmEventB

Send email marketing events to FUB, up to 1000 per call. Recipients with no matching contact are skipped and listed in recipientsNotFound.

listEmCampaignsA

List email marketing campaigns, optionally by origin system and origin ID.

createEmCampaignA

Create an email marketing campaign. The origin + originId pair must be unique; never reuse it. Subject and bodyHtml support merge fields.

updateEmCampaignA

Update an email campaign's subject or body. Only account owners and admins can do this. Merge fields are allowed.

listCustomFieldsB

List custom fields. Use limit=100 to get all in one call.

createCustomFieldA

Create a custom field (account owners only). The type cannot be changed later.

getCustomFieldC

Get a custom field by ID

updateCustomFieldA

Update a custom field (account owners only). The type cannot be changed; delete and recreate instead.

listStagesC

List pipeline stages. Default sort is orderWeight.

createStageA

Create a stage. orderWeight defaults to 1000; FUB then renumbers all stages in steps of 1000.

getStageC

Get a stage by ID

updateStageA

Update a stage's name or position. Stages with isProtected=true cannot be renamed. FUB renumbers all stage weights in steps of 1000.

listTasksA

List tasks. Use due=overdue for overdue tasks, due=today for today's, assignedUserId for one user's tasks, personId for one contact's. Add isCompleted=false for open tasks only. Filters combine.

createTaskA

Create a task on a person. personId is required, and one of assignedUserId or assignedTo is required. dueDate is YYYY-MM-DD; use dueDateTime for a specific time.

getTaskC

Get a task by ID

updateTaskB

Update a task. Mark done with isCompleted=true. dueDate is YYYY-MM-DD; use dueDateTime for a specific time.

listAppointmentsA

List appointments. Filter by personId (comma list allowed), userId, or a start+end date range (both required together).

createAppointmentA

Create an appointment. Use start/end (UTC; offset suffix allowed), typeId/outcomeId, invitees [{userId}] or [{personId}]. sendInvitation=true emails invitees (SMS too if reminders are on); default false.

getAppointmentC

Get an appointment by ID

updateAppointmentA

Update an appointment. FUB requires start and end on EVERY update (even partial edits) or it returns 'Valid Start and End dates are required'. Refetch with getAppointment first if you only have the id. Invitees: [{userId:int}] for a FUB user, [{personId:int}] for a contact (optional name/email). The shape {type,id} is NOT FUB's; it is auto-converted, but prefer userId/personId. This tool never sends invitation emails (sendInvitation is not sent; FUB's default is off), but FUB syncs appointments to Google/Outlook calendars for invitees, so a person invitee may still get a calendar invite from the calendar side.

listAppointmentTypesC

List appointment types. Default sort is orderWeight.

createAppointmentTypeB

Create an appointment type (account owner only).

getAppointmentTypeC

Get appointment type by ID

updateAppointmentTypeB

Update an appointment type (account owner only).

listAppointmentOutcomesB

List appointment outcomes. Default sort is orderWeight.

createAppointmentOutcomeB

Create an appointment outcome (account owner only).

getAppointmentOutcomeC

Get appointment outcome by ID

updateAppointmentOutcomeB

Update an appointment outcome (account owner only).

listWebhooksA

List webhooks. Account owner or registered system only. Filter by event or status.

createWebhookB

Create a webhook for one event. url must be https. Account owner or registered system only.

getWebhookB

Get a webhook by ID. Account owner or registered system only.

updateWebhookA

Update a webhook. url must be https. Account owner or registered system only.

getWebhookEventsA

Get the events delivered for a webhook (id, eventCreated, event, resourceIds, uri). Account owner or registered system only.

listPipelinesB

List pipelines, optionally by exact name.

createPipelineA

Create a pipeline with optional stages (account owner only). Each stage needs name and closedStage.

getPipelineB

Get a pipeline by ID

updatePipelineA

Update a pipeline and its stages (owner only). Stages with id are updated, without id are created.

listDealsA

List deals, filtered by pipeline, user, person or status. Archived and Deleted deals are hidden unless includeArchived=1 or includeDeleted=1. Use getDeal for one deal by ID.

createDealA

Create a deal. name and stageId are required. Use peopleIds (array) and price (whole number); do not use personId or value. Custom field values may be passed as extra properties (e.g. customField1).

getDealC

Get a deal by ID

updateDealA

Update a deal by ID; send only fields to change. peopleIds and userIds replace the full list. Use peopleIds (not personId) and price (not value). Custom field values may be passed as extra properties (e.g. customField1).

createDealAttachmentA

Attach an externally hosted file to a deal by URI. Restricted to registered systems (needs FUB_SYSTEM and FUB_SYSTEM_KEY). FUB does not host uploads here; omitting uri returns 403.

getDealAttachmentC

Get a deal attachment by ID

updateDealAttachmentA

Update a deal attachment by ID. FUB requires dealId, uri and fileName on every update, even if unchanged.

listDealCustomFieldsA

List deal custom fields. Paginated: FUB returns 10 per page unless limit is set; pass limit=100 to get more in one call.

createDealCustomFieldA

Create a deal custom field. Only the account owner can do this. label and type are required; choices applies only to dropdown fields.

getDealCustomFieldB

Get a deal custom field by ID

updateDealCustomFieldA

Update a deal custom field by ID. Only the account owner can do this. Send only fields to change.

listGroupsA

List lead-routing groups (not accessible to lender accounts). Returns up to 100 per call; if _metadata.next is set, call again with next.

listRoundRobinGroupsA

List round robin groups, including each group's next round-robin user. Not accessible to lender accounts.

createGroupA

Create a lead-routing group. Admin accounts only. name and users (user IDs) are required; the member list key is users, not userIds.

getGroupC

Get a group by ID

updateGroupA

Update a group by ID. Admin accounts only. Send only fields to change; the current users are kept when users is not sent.

listTeamsA

List teams with their userIds and leaderIds. Returns up to 100 per call; if _metadata.next is set, call again with next.

createTeamA

Create a team. name and userIds (all member user IDs) are required; leaderIds is the complete list of team leaders. Needs team access (403 otherwise).

getTeamC

Get a team by ID

updateTeamA

Update a team by ID. If userIds or leaderIds is sent, send the COMPLETE list; it replaces the existing one.

listTeamInboxesA

List team inboxes with their users. Returns up to 100 per call; if _metadata.next is set, call again with next.

listPondsA

List ponds (shared lead pools). Returns up to 100 per call; if _metadata.next is set, call again with next.

createPondB

Create a pond. name, userId (the pond lead agent) and userIds (all member user IDs) are all required.

getPondC

Get a pond by ID

updatePondA

Update a pond by ID. If userIds is sent, send the COMPLETE member list; it replaces the existing one.

listTimeframesA

List timeframes (lead time-to-buy options). Returns up to 100 per call; if _metadata.next is set, call again with next.

inboxAppAddMessageA

Add a message to an inbox app conversation (creates the conversation on first use). Conversations are keyed by YOUR externalConversationId. person and owner are needed on the first message of a conversation.

inboxAppUpdateMessageA

Update the delivery status of an inbox app message. Identify the message by id or externalMessageId. Message text cannot be changed here.

inboxAppAddNoteB

Add an internal note to an inbox app conversation, keyed by your externalConversationId.

inboxAppUpdateConversationA

Update an inbox app conversation: subject, archive state, person, or assignment. Send only fields to change.

inboxAppGetParticipantsC

List participants of an inbox app conversation.

inboxAppCreateParticipantB

Add a participant to an inbox app conversation. Give exactly one of personId, userId, relationshipId, or name/email/phone.

inboxAppInstallA

Install an inbox app for a user or account-wide. Needs the publishedInboxAppId from FUB's app catalog and a webhook subscriptionUrl for replies.

listInboxAppInstallationsA

List installations of one published inbox app. Needs a registered third-party system (FUB_SYSTEM and FUB_SYSTEM_KEY).

getReactionsA

Get ONE reaction by the reaction's own ID. To list a note's reactions, fetch the note with includeReactions=true instead.

createReactionA

Add an emoji reaction to a Note, Call or ThreadedReply as the API key owner. Beta endpoint.

getThreadedRepliesA

Get ONE threaded reply by the reply's own ID. To list a note's replies, fetch the note with includeThreadedReplies=true instead.

removeTagFromPersonA

Remove one tag from a person, leaving other tags untouched (case-insensitive). Use this instead of updatePerson tags, which replaces ALL tags.

getPersonByEmailA

Look up one person by email. Returns the contact, or an ambiguity result with candidate IDs. Use this to find a contact; use listPeople for other filters.

searchPeopleByTagA

Find people with a tag (GET /people?tags=). Use this for a simple tag lookup; use listPeople when combining tags with other filters. OR-matching of multiple tags is unverified.

bulkUpdatePeopleA

Apply the same updatePerson changes to many people, throttled (pauses 11s per 20 people). Use this instead of looping updatePerson. Returns per-person success.

listAvailableTagsA

List distinct tags by scanning recent contacts (up to 500, 100 per page). Rarely used tags may be missed. Use searchPeopleByTag to find people with a known tag.

aboutA

Get information about this MCP server, its author, and the projects behind it. Call this when the user asks 'what is this MCP', 'who built this', or 'tell me about this server'. Returns author bio, related projects, and how to give thanks (real estate referrals welcome).

helpA

Get usage tips for this MCP server, common tool examples, and how to report bugs or request features. Call this when the user asks for help, examples, or how to use this MCP.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 136 tools

Disambiguation4/5

The vast surface is still largely partitioned by resource+action, and descriptions actively steer between near-neighbors (getPersonByEmail vs listPeople, searchPeopleByTag vs listPeople, removeTagFromPerson vs updatePerson, bulkUpdatePeople vs updatePerson, templates vs text message templates vs email campaigns). A few genuine overlaps remain — checkDuplicate vs getPersonByEmail, listCustomFields vs listDealCustomFields vs listStages, and getReactions/getThreadedReplies that only fetch by ID while listing lives elsewhere — but on the whole an agent can pick correctly.

Naming Consistency4/5

The dominant pattern is verb_noun camelCase (listPeople, createDeal, updateAppointment, getWebhook), applied across nearly all 136 tools. Deviations are minor: namespace-prefixed tools (inboxAppAddMessage, inboxAppInstall, listInboxAppInstallations), plural names for single-item getters (getReactions, getThreadedReplies), the Em abbreviation (listEmEvents, createEmCampaign), and non-verb utility tools (about, help).

Tool Count2/5

136 tools is far past the point where a single agent can hold the surface in mind, even though the underlying Follow Up Boss CRM is genuinely sprawling (people, deals, pipelines, appointments, automations, inbox apps, teams, ponds, webhooks). Many resources contribute 4-5 near-identical CRUD variants, so the count is defensible in principle but overwhelming in practice; splitting or namespace-scoping would help considerably.

Completeness4/5

Coverage is unusually broad: CRUD across people, deals, tasks, appointments, notes, calls, pipelines, stages, groups, teams, ponds, webhooks, automations, action plans, custom fields, plus specialized lookups. Gaps are mostly deletions (no delete tools for any resource), missing list operations for attachments and reactions/threaded replies (only get-by-ID), and no update paths for people's source/sourceUrl, but these are largely upstream API limitations rather than oversights.

Maintenance

ActivityMaintained
ResponsivenessLimited data