# Follow Up Boss MCP connector

The Follow Up Boss connector brings your leads, notes, calls, texts and lead events into Claude, ChatGPT, Cursor and the Elaichi Agent, so each agent works their own people from any AI client under one governed endpoint.

Source: https://elaichi.ai/connectors/followupboss/

## Facts

| | |
| --- | --- |
| Application | Follow Up Boss |
| Category | CRM |
| AI tools | 139 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Follow Up Boss is connected

- Which unclaimed leads came in this week and where from?
- Summarize my calls with the Nguyen family this month.
- Add a note to Maria Lopez about today's showing on Elm Street.

## Connect Follow Up Boss in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Follow Up Boss.
2. Optionally set Share with, then press Connect.
3. Paste a Follow Up Boss API key. One person generates a token in Follow Up Boss and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Follow Up Boss tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Follow Up Boss MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Follow Up Boss MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## Follow Up Boss MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Follow Up Boss to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Follow Up Boss tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Follow Up Boss through Elaichi

### Catch a lead up after a showing

Sales. Ask the agent to add a note to the buyer in Follow Up Boss with what they liked, what they passed on, and the next step you agreed.

### Work the unclaimed lead pool

Inside sales. Pull the leads nobody has claimed yet, claim the ones you can call in the next hour, and ignore the obvious duplicates and spam.

### Review yesterday's calls before the huddle

Team leads. Get a plain summary of the calls logged across the team, who was reached, who was not, and which leads have gone quiet.

### Log a lead event from an open house

Marketing. Create a Follow Up Boss event for each sign-in from the weekend so the source and the property stay attached to the person.

### Check the text thread before a call

Transaction coordination. Read back the recent text messages with a client so you know what was already promised before you pick up the phone.

### Keep the user list tidy

Operations. List the Follow Up Boss users on the account, spot seats that belong to agents who have moved on, and remove them.

## Frequently asked questions

### How do I connect Follow Up Boss to Claude?

Connect Follow Up Boss in Elaichi by pasting the API key from your Follow Up Boss admin settings, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate. Sign in to Elaichi from Claude and your Follow Up Boss leads are available in the chat.

### Does Follow Up Boss work with ChatGPT and Cursor as well as Claude?

Yes. Once Follow Up Boss is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Follow Up Boss once and every client picks it up.

### What can an AI agent actually do with my Follow Up Boss data?

An agent can find people in Follow Up Boss, read and add notes, log calls, review recent text messages, and create lead events. It can claim or ignore unclaimed leads, update a person after a showing, and list the users on your account. Short, concrete asks such as "log a note on the Patels about today's showing" work better than long paragraphs.

### Does connecting Follow Up Boss give the AI access to every lead in the account?

No. Access follows the person who signed in, so an agent in Follow Up Boss sees only the people, notes and calls their own Follow Up Boss account can see. Elaichi can narrow that further with restrictions, and it can never widen it beyond what the person already has.

### Can my team share one Follow Up Boss connection?

Yes. One person connects Follow Up Boss in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every note, call and lead change.

### Can I stop an agent from deleting or changing things in Follow Up Boss?

Yes. Restrictions in Elaichi apply per action, so you can allow reading people and adding notes while blocking deleting a person or removing a Follow Up Boss user. A restricted action is never advertised to the AI client at all, so no prompt, however worded, can reach it.

### What happens to a Follow Up Boss connection when someone leaves?

Offboarding a person in Elaichi ends their access to Follow Up Boss through every AI client at once. If they were using a shared connection, it keeps working for everyone else on the team. Disconnecting Follow Up Boss once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

### Does the Follow Up Boss MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Follow Up Boss is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

## All 139 Follow Up Boss tools

Every tool below is callable through https://api.elaichi.ai/mcp once Follow Up Boss is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Follow Up Boss people** (List). List people (contacts and leads) in Follow Up Boss. Returns each person's id, firstName, lastName, emails, phones, stage, and tags. Custom fields are only included when fields=allFields is passed. Max 100 per page.
- **Get single Follow Up Boss person by ID** (Get). Get a single person (lead/contact) in Follow Up Boss by id. Returns the full person record including name (first/last), stage, source, assigned agent, tags, and contact details across emails, phones, and addresses. Required: id.
- **Create a Follow Up Boss person** (Create). Manually add a new person (contact) in Follow Up Boss. Returns the created person record with fields such as id, firstName, lastName, stage, emails, phones, addresses, tags, and assignedTo. No fields are strictly required; with deduplicate=true, an existing matching person is returned unchanged. Note: this does not run lead automations — use POST /v1/events to send leads.
- **Update a Follow Up Boss person by ID** (Update). Update a person in Follow Up Boss by id. Returns the updated person record including id, firstName, lastName, stage, emails, phones, and tags. Required: id. Tags and phones arrays overwrite existing values (set mergeTags=true to merge new tags); source and sourceUrl cannot be changed after creation.
- **Delete a Follow Up Boss person by ID** (Delete). Delete a person in Follow Up Boss by id. Deleting a person also deletes all associated data (notes, calls, text messages, etc.). Returns the deleted person record including id, firstName, lastName, stage, and emails. Required: id.
- **Follow Up Boss people search** (Search). Check whether a person already exists in Follow Up Boss by email address or phone number. Returns: found, matchedBy, assignedTo. Supply email or phone in the request body.
- **Follow Up Boss people list unclaimed** (List). List First To Claim leads in Follow Up Boss that have not been claimed yet and are available to claim. Returns: id, created, name, firstName, lastName, source, sourceId, delayed, picture, claimed. Unclaimed leads are assigned to a fallback agent after a short time (default 15 minutes), so this list is usually empty.
- **Follow Up Boss people claim** (Action). Claim a lead offered via First To Claim in Follow Up Boss. Returns the full lead object including id, name, firstName, lastName, stage, source, assignedTo, and email/phone/address details. Required: personId. Returns a conflict if the lead was already claimed by someone else.
- **Follow Up Boss people ignore** (Action). Confirm receipt of a First To Claim lead offer in Follow Up Boss without claiming it. Returns an empty 204 response on success. Required: personId. Ignored leads still appear in the unclaimed list.
- **List all Follow Up Boss events** (List). Search Follow Up Boss events such as inquiries, property views, and calls. Returns: id, created, updated, personId, message, description, noteId, source, property, propertySearch, pageTitle, pageUrl, pageDuration. Some lead events are not accessible via API and are only visible within the Follow Up Boss application.
- **Get single Follow Up Boss event by ID** (Get). Get a single Follow Up Boss event by id. Returns the event record including id, type, personId, message, source, and created, with related property and property-search details. Required: id.
- **Create a Follow Up Boss event** (Create). Send a lead or lead event to Follow Up Boss; the contact is de-duplicated and created or updated. Returns the lead record — not the event — with id, firstName, lastName, stage, source, and emails. 200 updates an existing person, 201 creates one, 204 means the lead flow is archived, and an unmatched person.id returns 404. campaign.source is required when campaign is sent.
- **List all Follow Up Boss users** (List). Search Follow Up Boss users by role, full name, or email. Returns each user's id, name, email, phone, role, status, timezone, groups, teamIds, and leadEmailAddress; role maps to Agent, Broker, or Lender. Max 100 per page.
- **Get single Follow Up Boss user by ID** (Get). Get a single Follow Up Boss user by id. Returns the full user record including id, name, email, role, status, timezone, groups, teamIds, and leadEmailAddress; role maps to Agent, Broker, or Lender. Required: id.
- **Delete a Follow Up Boss user by ID** (Delete). Delete a Follow Up Boss user by id. Returns an empty 204 response on success. Requires administrator access. Required: id.
- **Create a Follow Up Boss note** (Create). Create a note on a person in Follow Up Boss. Returns the created note including its id, personId, subject, body, and isHtml. Required: personId.
- **Get single Follow Up Boss note by ID** (Get). Get a single Follow Up Boss note by id. Returns the note including its id, personId, subject, body, and isHtml. Required: id. Notes created by restricted systems may return 404 even for a valid id.
- **Update a Follow Up Boss note by ID** (Update). Update a note's subject, body, or HTML rendering settings by id in Follow Up Boss. Returns the updated note including its id, personId, subject, body, and isHtml. Required: id.
- **Delete a Follow Up Boss note by ID** (Delete). Delete a note by id in Follow Up Boss. Returns an empty 200 response on success.
- **List all Follow Up Boss calls** (List). List calls in Follow Up Boss, optionally filtered by person or phone number. Returns: id, created, updated, createdById, updatedById, phone, personId, userId, userName, note, outcome, isIncoming, duration, ringDuration, recordingUrl.
- **Create a Follow Up Boss call** (Create). Add a call in Follow Up Boss. Returns: id, created, updated, createdById, updatedById, phone, personId, userId, userName, note, outcome, isIncoming, duration, ringDuration, recordingUrl. Requires personId, phone, and isIncoming.
- **Get single Follow Up Boss call by ID** (Get). Get a single Follow Up Boss call by id. Returns: id, created, updated, createdById, updatedById, phone, personId, userId, userName, note, outcome, isIncoming, duration, ringDuration, recordingUrl.
- **Update a Follow Up Boss call by ID** (Update). Update a call in Follow Up Boss by id. Returns: id, created, updated, createdById, updatedById, phone, personId, userId, userName, note, outcome, isIncoming, duration, ringDuration, recordingUrl. Required: id. Only calls created by the calling account/system can be updated.
- **List all Follow Up Boss text messages** (List). List text messages for a person or phone number in Follow Up Boss. Returns: id, created, updated, createdById, updatedById, personId, name, firstName, lastName, userId, userName, status, message, fromNumber, toNumber, sent, isIncoming, archived, read, sharedInboxId, actionPlanId, isExternal, externalUrl, externalLabel, media, participants, systemName. Filter with personId, toNumber, or…
- **Create a Follow Up Boss text message** (Create). Create a record of an externally sent text message in Follow Up Boss. Returns the created record with id, personId, message, status, fromNumber, toNumber, and sent. Requires personId, message, toNumber, and fromNumber. Logs the message only — no actual SMS is sent — and the endpoint is restricted to registered external systems.
- **Get single Follow Up Boss text message by ID** (Get). Get a single text message from Follow Up Boss by id. Returns the message record including id, personId, message, status, fromNumber, toNumber, sent, and isIncoming. Some text message content is restricted and only visible within the Follow Up Boss app. Required: id.
- **List all Follow Up Boss templates** (List). List all Follow Up Boss email templates. Returns: id, created, updated, createdById, updatedById, name, imported, isMobile, isShared, body, subject, isEditable, isDeletable, isShareable, actionPlans, categories. Max 100 per page.
- **Create a Follow Up Boss template** (Create). Create a new email template in Follow Up Boss. Returns the created template with id, name, subject, body, isShared, and actionPlans. Requires name, subject, and body; only subject and body support Merge Fields.
- **Get single Follow Up Boss template by ID** (Get). Get a single Follow Up Boss email template by id, optionally with Merge Fields applied. Returns: id, created, updated, createdById, updatedById, name, imported, isMobile, isShared, body, subject, isEditable, isDeletable, isShareable, actionPlans, categories. Required: id.
- **Update a Follow Up Boss template by ID** (Update). Update a Follow Up Boss email template by id. Returns the updated template with id, name, subject, body, and isShared. Required: id. Only subject and body support Merge Fields.
- **Delete a Follow Up Boss template by ID** (Delete). Delete a Follow Up Boss email template by id. Returns an empty 204 response on success. Required: id. Deletion returns 403 Forbidden if the template is still in use by an Action Plan.
- **Follow Up Boss templates merge** (Merge). Merge a Follow Up Boss email template with multiple recipients, resolving %contact_% merge fields against the first recipient matching the person. Returns the merged template including id, name, subject, and body with merge fields substituted. The recipients cc, bcc, and from keys are accepted but currently unused.
- **List all Follow Up Boss text message templates** (List). List all text message templates in Follow Up Boss. Returns each template's id, name, message, isShared, sent/reply totals, and the Action Plans using it. Max 100 per page.
- **Create a Follow Up Boss text message template** (Create). Create a text message template in Follow Up Boss. Returns the created template with id, name, message, isShared, createdBy, and send/reply stats. The message supports merge fields. Requires name and message.
- **Get single Follow Up Boss text message template by ID** (Get). Get a text message template by id in Follow Up Boss. Returns: id, name, totalSent, totalReplies, message, isShared, createdBy, isEditable, isDeletable, isShareable, sentPeopleIds, actionPlans. Required: id.
- **Update a Follow Up Boss text message template by ID** (Update). Update a text message template by id in Follow Up Boss. Returns the updated template with id, name, message, isShared, and usage stats. Required: id.
- **Delete a Follow Up Boss text message template by ID** (Delete). Delete a text message template by id in Follow Up Boss. Returns an empty 204 response on success. Deletion fails with 403 Forbidden if the template is still in use by an Action Plan.
- **Follow Up Boss text message templates merge** (Merge). Merge a Follow Up Boss text message template with multiple group-text recipients, resolving %contact_*% merge fields (such as %contact_rels_first_name%) from the first recipient matching the person. Returns the rendered text in mergedTemplate. Required: templateId.
- **List all Follow Up Boss custom fields** (List). List all Follow Up Boss custom fields, optionally filtered by label. Returns: id, label, name, type, isRecurring, choices. Use each field's `name` value when sending custom field data on events or people. Max 100 per page.
- **Create a Follow Up Boss custom field** (Create). Create a Follow Up Boss custom field. Returns: id, label, name, type, isRecurring, choices. Requires label and type; use choices for dropdown fields and isRecurring for date fields.
- **Get single Follow Up Boss custom field by ID** (Get). Get a single Follow Up Boss custom field by id. Returns: id, label, name, type, isRecurring, choices. Required: id.
- **Update a Follow Up Boss custom field by ID** (Update). Update a Follow Up Boss custom field by id. Returns: id, label, name, type, isRecurring, choices. Required: id. The field's type cannot be changed after creation — delete and recreate the field instead.
- **Delete a Follow Up Boss custom field by ID** (Delete). Delete a Follow Up Boss custom field by id. Returns an empty 204 response on success. Required: id.
- **List all Follow Up Boss stages** (List). List Follow Up Boss stages in a pipeline-sorted collection. Returns each stage's id, name, orderWeight, isProtected, and peopleCount. Max 100 per page.
- **Create a Follow Up Boss stage** (Create). Create a new stage in Follow Up Boss. Returns the created stage including id, name, orderWeight, isProtected, and peopleCount. Required: name. The orderWeight of all stages is recalculated with gaps of 1000 after creation.
- **Get single Follow Up Boss stage by ID** (Get). Get a single Follow Up Boss stage by id. Returns: id, name, orderWeight, isProtected, peopleCount. Required: id.
- **Update a Follow Up Boss stage by ID** (Update). Update a Follow Up Boss stage by id. Returns the updated stage including id, name, orderWeight, isProtected, and peopleCount. Required: id. Protected stages (isProtected: true) cannot be renamed.
- **Delete a Follow Up Boss stage by ID** (Delete). Delete a Follow Up Boss stage by id. Returns an empty 204 response on success. Required: id. Protected stages (isProtected: true) cannot be deleted.
- **List all Follow Up Boss tasks** (List). List Follow Up Boss tasks. Returns task records including id, name, type, personId, AssignedTo, assignedUserId, dueDate, dueDateTime, and isCompleted. Supports filters: personId, assignedTo, assignedUserId, name, type, isCompleted, and due ranges (due, dueStart, dueEnd).
- **Create a Follow Up Boss task** (Create). Create a new task in Follow Up Boss for a contact. Returns the created task object including id, name, type, personId, assignedUserId, isCompleted, dueDate, and the related person. Required: personId (and either assignedTo or assignedUserId when the other is empty).
- ...and 89 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.