A Model Context Protocol (MCP) server for Follow Up Boss CRM by Ed Neuhaus (Neuhaus Realty Group, Austin TX) - 160 tools covering 100% of the
Followupboss MCP server exists for a simple reason — assistants are far more useful when they can act on Followupboss directly instead of describing what you should do. A Model Context Protocol (MCP) server for Follow Up Boss CRM by Ed Neuhaus (Neuhaus Realty Group, Austin TX) - 160 tools covering 100% of the official API plus about/help meta tools.
Once Followupboss is connected, these are the calls the assistant has available:
listEvents — List events with filtering by person, type, propertycreateEvent — Create a new event (lead event, property inquiry, etc.)getEvent — Get a single event by IDlistPeople — Search and filter contacts extensivelycreatePerson — Create a new contactgetPerson — Get a contact by IDupdatePerson — Update contact details, stage, tags, etcdeletePerson — Delete (trash) a contactcheckDuplicate — Check if a contact exists by email or phonelistUnclaimed — List unclaimed leads in pondsclaimPerson — Claim an unclaimed leadcreatePersonAttachment — Attach a file to a contactYou will need 2 environment variables: FUB_API_KEY, FUB_SYSTEM_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Followupboss's toolset — listEvents, createEvent, getEvent and 11 more — is a fair guide to whether it matches your workflow. It is maintained by mindwear-capitian; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Followupboss's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| listEvents | List events with filtering by person, type, property |
| createEvent | Create a new event (lead event, property inquiry, etc.) |
| getEvent | Get a single event by ID |
| listPeople | Search and filter contacts extensively |
| createPerson | Create a new contact |
| getPerson | Get a contact by ID |
| updatePerson | Update contact details, stage, tags, etc. |
| deletePerson | Delete (trash) a contact |
| checkDuplicate | Check if a contact exists by email or phone |
| listUnclaimed | List unclaimed leads in ponds |
| claimPerson | Claim an unclaimed lead |
| createPersonAttachment | Attach a file to a contact |
| getPersonAttachment | Get an attachment by ID |
| updatePersonAttachment | Update an attachment |
{
"mcpServers": {
"followupboss": {
"command": "node",
"args": ["/full/path/to/followupboss-mcp-server/index.js"],
"env": {
"FUB_API_KEY": "your_api_key_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| FUB_API_KEY | Credential the server authenticates with. | Yes |
| FUB_SYSTEM_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.