Agentic CRM for service businesses — bookings, customers, WhatsApp, loyalty, invoicing.
Agentic CRM for service businesses — bookings, customers, WhatsApp, loyalty, invoicing. The favcrm mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
229 typed tools — customers, bookings, loyalty, invoices, payments, WhatsApp / SMS / email — exposed via MCP. Works with any agentic client that speaks Streamable HTTP transport.
Everything the assistant can do here goes through one of these:
title — human-readable labelreadOnlyHint — true for list_* / get_* / search_* / etcdestructiveHint — true for delete_* / cancel_* / void_* / refund_*openWorldHint — true for tools that hit external services (WhatsApp, Stripe, email)idempotentHint — true for set_* / update_* / upsert_* and read-onlyClient — StatusCursor — ✅ LiveSmithery — ✅ LiveScope — Sample toolscontacts — search_members, get_member_profile, create_account, attach_tagscustomer_segments — list_segments, preview_segment_count, set_segment_memberscustom_fields — list_custom_fields, create_custom_field, set_custom_field_valuesBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need one environment variable: FAVCRM_API_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.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. FavCRM's toolset — title, readOnlyHint, destructiveHint and 11 more — is a fair guide to whether it matches your workflow. It is maintained by io.favcrm; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| title | human-readable label |
| readOnlyHint | true for list_* / get_* / search_* / etc. |
| destructiveHint | true for delete_* / cancel_* / void_* / refund_* |
| openWorldHint | true for tools that hit external services (WhatsApp, Stripe, email) |
| idempotentHint | true for set_* / update_* / upsert_* and read-only |
| Client | Status |
| Cursor | ✅ Live |
| Smithery | ✅ Live |
| Scope | Sample tools |
| contacts | search_members, get_member_profile, create_account, attach_tags |
| customer_segments | list_segments, preview_segment_count, set_segment_members |
| custom_fields | list_custom_fields, create_custom_field, set_custom_field_values |
| bookings | list_services, get_available_slots, create_booking |
| membership | list_tiers, enrol_membership, earn_loyalty_points |
{
"mcpServers": {
"favcrm": {
"command": "npx",
"args": ["-y", "skills"],
"env": {
"FAVCRM_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| FAVCRM_API_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.