# Follow Up Boss [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/mindwear-capitian/followupboss-mcp-server  
**GitHub Stars:** 32  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/follow-up-boss

## Description
Follow Up Boss CRM in plain English. 160 tools; bring your own API key.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "follow-up-boss": {
    "command": "npx",
    "args": ["-y","follow-up-boss"],
    "env": {
      "FUB_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `FUB_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the Follow Up Boss MCP server does

The Follow Up Boss MCP server gives an MCP-compatible AI client access to a Follow Up Boss account. It covers the official API with 160 tools when Full Access is enabled, plus `about` and `help` metadata tools. The available operations span common CRM workflows: finding and creating contacts, changing stages and tags, checking duplicates, managing relationships, and working with deals and pipeline stages.

It also supports follow-up tasks, appointments, reminders, call logs, text-message history, email templates, smart lists, action plans, automations, custom fields, teams, groups, lead ponds, webhooks, inbox apps, reactions, threaded replies, email marketing campaigns, and timeframes. API text-message creation only records a message in Follow Up Boss; it does not send an SMS.

## How it works

The server runs locally with Node.js 18 or later and uses the FUB API key supplied for the account. An MCP client starts the process and presents its tools to the model, allowing requests such as searching contacts or updating a deal to be translated into API calls. The setup command tests the connection and writes local settings to a `.env` file.

Safe Mode is the default. It exposes 136 tools and blocks the 24 tools that send HTTP `DELETE` requests. Full Access exposes all 160 tools. Safe Mode still permits creation, updates, and bulk updates, so it is not a read-only mode.

## Setup and configuration

You need a Follow Up Boss account with API access, Node.js 18 or later, and an MCP-compatible AI client. Obtain the API key from Follow Up Boss under Admin > API, then clone or download the repository, run `npm install`, and execute `npm run setup`. The wizard asks for the key, checks connectivity, lets you select Safe Mode or Full Access, and displays the client connection settings.

Set `FUB_API_KEY` to the account key. Change `FUB_SAFE_MODE` in the `.env` file or client configuration if you need to switch access modes. The repository also provides an optional `npm test` command that checks server startup, the MCP handshake, tool listing, and a read-only API call.

## Limitations and notes

The Follow Up Boss MCP server has full read and write access in Full Access mode. It can create, update, and delete CRM records, so review model-generated actions and back up important data before use.

Some endpoints are restricted to registered Follow Up Boss systems. Webhooks, inbox apps, automations 2.0, text-message logging, and person or deal attachments require `FUB_SYSTEM` and `FUB_SYSTEM_KEY` issued to an approved third-party integration partner. Do not reuse credentials from another application or invent values. Leave these variables unset unless you have legitimate registered-system credentials; the affected tools will report that the credentials are required.

The project is licensed under Elastic License 2.0 from version 1.1.2. It permits self-hosting for your own business but does not permit offering the software as a hosted or managed service to third parties. Versions through 1.1.1 used the MIT license.

_Full upstream README: https://allmcps.com/mcp/follow-up-boss/readme_