FavCRM

MCP办公协作

提供方 favcrm

办公协作 未标注 OAuth 授权 社区 / 第三方 Claude DesktopClaudeCursorCline

FavCRM is an agentic CRM for service businesses. Its public MCP server exposes 190+ typed tools — bookings, customers, loyalty, WhatsApp/SMS/email, invoicing — at 100% annotation coverage (read-only / destructive / open-world labelled; outbound sends approval-gated). Any

一句话选型结论

按资料字段整理

FavCRM 属于办公协作类 MCP 服务器,传输方式未标注,OAuth 授权,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类办公协作 传输方式未标注 鉴权OAuth 授权 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

办公协作
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

mcp server crm scheduling whatsapp invoicing small business sales

支持客户端

适用场景

mcp servercrmscheduling

安装与配置

未标注 OAuth 授权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
日程与消息

查日程、发消息、约会议。

表单与审批

填表单、走审批流。

团队协作

同步任务、汇总进展。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在办公协作场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
FavCRM当前 未标注 未标注 未标注 无 未标注
CowAgent 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Karakeep MCP 未标注 未标注 未标注 无 2026-05-17
agentscope 未标注 stdio · 本地进程 本地部署 有 2026-04-11
note-gen 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Everywhere 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

办公协作
字段来自项目仓库与公开索引,中文说明由本站标注
提供方favcrm上游标注的维护方 favcrm
分类办公协作本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

13.0 KB
来自项目仓库与上游目录的原文,未做删改

FavCRM MCP

> Install snippets, examples, and docs for the FavCRM Model Context Protocol server. The server itself is hosted at https://api.favcrm.io/mcp — this repo is for client setup and community examples.

231 typed tools — customers, bookings, events, loyalty, invoices, payments, WhatsApp / SMS / email — exposed via MCP. Works with any agentic client that speaks Streamable HTTP transport.

The endpoint supports purpose-built tool profiles selected with ?profile= or X-FavCRM-MCP-Profile:

  • compact exposes a small search_tools + execute_tool discovery/router surface for large-agent runtimes.
  • platform exposes only superadmin customer-workspace and company-setup operations, works without an active merchant company, and never exposes raw SQL.
  • full remains the default for clients and scanners.

Platform operators can start from the dedicated Cursor or Claude Desktop configuration. Ordinary merchant API keys cannot access platform tools.

🤖 AI Agent Skills

Building against the FavCRM headless backend with an AI Agent? Teach your AI our best practices, standard operating procedures, and MCP tool shapes by installing our official skills:```bash

Example: Install the Booking Operator skill

npx skills add https://github.com/favcrm/mcp/tree/main/skills/favcrm-booking-operator

Or install all skills at once

npx skills add favcrm/mcp


See the `skills/` directory for the full list of available agent skills.

Public agent skills live in `skills/`: portable workflow packages for agentic registration, team onboarding, channel setup, booking operations, customer lifecycle, comms approval, billing/commerce, content, sales ops, knowledge training, and reporting. They are source-readable for agents and marketing, while FavCRM runtimes install vetted versions through the platform skill registry.

| Client | Status | Setup |
|---|---|---|
| **Vercel v0** | ✅ Live | Marketplace install — auto-provisions a workspace + injects env vars |
| **Cursor** | ✅ Live | `mcp.json` snippet |
| **Smithery** | ✅ Live | `smithery mcp add favcrm/favcrm` |
| **Claude Desktop / Connector** | 🚧 Pending | OAuth provider (Phase 3, ~3 weeks) |
| **ChatGPT Apps Directory** | 🚧 Pending | Listing under review |
| **Windsurf / Continue.dev / Zed** | ✅ Works | Same `mcp.json` shape as Cursor |

---

## Get a key

Two ways:

**Option A — your agent signs you up (no form, no portal click)**

Connect FavCRM to your client first (see Cursor section below) using a placeholder env var. Then ask your agent:

> "Sign me up for FavCRM. Yoga studio called Stretch + Breathe in Hong Kong."

The agent will:

1. Call `register_organisation_request` — server emails a 6-digit code to you
2. You paste the code back in chat
3. Agent calls `register_organisation_verify` — server returns a fresh `fav_mcp_*` key
4. Agent stores the key and starts working immediately

See `skills/favcrm-agentic-registration` for the portable SKILL.md workflow.

Behind the scenes: 10-min OTP, real email-ownership check, per-IP rate limit (3/hour, 20/day). No phishing surface, no fake demos.

**Option B — sign up the traditional way**

favcrm.io/signup → portal → `Settings → MCP Keys` → copy the `fav_mcp_*` value.

Existing FavCRM merchants: same place, no plan upgrade needed for MCP access.

**Free tier (both options):** 100 customers, 200 bookings/month, 1k MCP calls/month, 30-day trial of higher limits.

### Bootstrap from the CLI

The `favcrm` CLI can also run the zero-state flow:```bash
favcrm signup request --email owner@example.com --organisation-name "Ada Studio"
favcrm signup verify --request-id <request-id> --code <code>
favcrm doctor
favcrm team invite create --email teammate@example.com --role staff
favcrm whatsapp status
favcrm whatsapp connect --mode cloud-api

Team invitees can accept without an existing API key:```bash
favcrm team invite accept-request --token <invite-token>
favcrm team invite accept-verify --token <invite-token> --code <code>


---

## Cursor

Verified shape, cursor.com/docs/mcp.

**`~/.cursor/mcp.json`** (or `.cursor/mcp.json` in your project):```json
{
  &quot;mcpServers&quot;: {
    &quot;favcrm&quot;: {
      &quot;url&quot;: &quot;https://api.favcrm.io/mcp&quot;,
      &quot;headers&quot;: {
        &quot;Authorization&quot;: &quot;Bearer ${env:FAVCRM_API_KEY}&quot;
      }
    }
  }
}

Then export the key — anywhere your Cursor process reads env vars:```bash

shell rc

echo 'export FAVCRM_API_KEY=fav_mcp_...' >> ~/.zshrc

or per-project (direnv)

echo 'export FAVCRM_API_KEY=fav_mcp_...' >> .envrc


Restart Cursor → `Settings → MCP → favcrm` connects → 231 tools land in chat.

&gt; Why `${env:VAR}` instead of inline? Cursor interpolates env vars at request time so the key never lands in your repo or shared config.

---

## Smithery

`favcrm.io` on Smithery — install via CLI:```bash
npm i -g @smithery/cli
smithery login
smithery mcp add favcrm/favcrm

For a project-scoped install, smithery mcp add favcrm/favcrm --client cursor writes the right mcp.json block.


Claude Desktop

🚧 OAuth-based connector pending Phase 3. Once live:

  1. claude.com → Connectors → Add custom connector
  2. URL: https://api.favcrm.io/mcp
  3. Authorize via OAuth → workspace selector → tool list

Until then, advanced users can wire FavCRM into Claude Desktop's claude_desktop_config.json via the same Bearer-header pattern as Cursor (community-only path; not currently in Anthropic's connector directory).


ChatGPT

🚧 Apps Directory listing under review. Once approved:

  1. ChatGPT → Tools menu → Apps → search "FavCRM"
  2. Add → OAuth handshake → workspace selector
  3. 26 curated tools land in chat (read-mostly + safe writes; destructive ops gated behind confirmation)

Test it

Once your config is live, ChatGPT/Cursor/Claude will list tools automatically. To smoke-test from the command line:```bash

Discovery (no auth needed — public-scan endpoint)

curl https://api.favcrm.io/.well-known/mcp/server-card.json | jq '.tools | length'

→ 231

Auth + initialize

curl -s https://api.favcrm.io/mcp \
-X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "Authorization: Bearer $FAVCRM_API_KEY" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}' \
| jq

Call a read-only tool

curl -s https://api.favcrm.io/mcp \
-X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "Authorization: Bearer $FAVCRM_API_KEY" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"list_membership_tiers","arguments":{}}}' \
| jq


See `examples/` for more.

---

## Tool surface

231 tools across 28 scopes. Every tool ships with annotations:

- `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

Clients can use these to gate destructive calls or estimate cost. The full catalog at `https://api.favcrm.io/.well-known/mcp/server-card.json` is the source of truth — listings here are summaries only.

Agents working from a compact or context-sensitive tool set should use `search_tools` to discover operations, then `execute_tool` to run the selected tool. Use `query_favcrm_platform` for platform docs before guessing behavior or argument shapes. For merchant-specific facts, policies, pricing notes, FAQs, or brand guidance, use `query_company_knowledge`; it returns snippets with source document IDs rather than full documents.

| Scope | Sample tools | Read-only | Write |
|---|---|---|---|
| `contacts` | `search_members`, `get_member_profile`, `create_account`, `attach_tags` | 5 | 6 |
| `customer_segments` | `list_segments`, `preview_segment_count`, `set_segment_members` | 4 | 4 |
| `custom_fields` | `list_custom_fields`, `create_custom_field`, `set_custom_field_values` | 3 | 4 |
| `bookings` | `list_services`, `get_available_slots`, `create_booking` | 12 | 15 |
| `events` | `list_event_registrations`, `get_event_campaign_exclusions` | 2 | 0 |
| `membership` | `list_tiers`, `enrol_membership`, `earn_loyalty_points` | 4 | 3 |
| `shop` | `list_products`, `get_order`, `create_order` | 8 | 6 |
| `invoices` | `list_invoices`, `mark_invoice_paid` | 4 | 4 |
| `campaigns` | `list_campaigns`, `send_campaign` (gated) | 5 | 3 |
| `blog` | `list_posts`, `publish_post` | 14 | 13 |

Superadmin platform tools use a separate scope family:

| Scope | Capability |
|---|---|
| `platform:customer_setup` | Search/create customer workspaces and configure company setup |
| `platform:catalog` | Manage global plan, module, and AI-media catalogs in the full profile |
| `platform:sql_read` | Break-glass `SELECT`/`EXPLAIN` access in the full profile |
| `platform:sql_write` | Break-glass DML access in the full profile |
| `platform:*` | All platform capabilities; reserve for controlled internal operators |

SQL scopes must be explicit, and SQL tools remain unavailable in the `platform` profile even with `platform:*`.

---

## Agent Issue Reports

Agents should call `report_agent_issue` when an MCP-native path is missing, a tool schema is confusing, a tool fails unexpectedly, or they had to fall back to REST/SDK behavior. Include expected behavior, actual behavior, steps tried, relevant tool calls/logs, AI analysis, and clarification questions. FavCRM routes these reports to the platform support queue for triage.

Example:```bash
favcrm tool call report_agent_issue &#x27;{&quot;title&quot;:&quot;Missing account creation MCP tool&quot;,&quot;severity&quot;:&quot;high&quot;,&quot;area&quot;:&quot;mcp_tool_missing&quot;,&quot;expectedBehavior&quot;:&quot;Agent can create an account via MCP only.&quot;,&quot;actualBehavior&quot;:&quot;Agent had to use SDK fallback.&quot;,&quot;stepsTried&quot;:[&quot;Listed tools&quot;,&quot;Tried create_contact&quot;],&quot;aiAnalysis&quot;:&quot;Account creation exists in backend services but was not exposed in MCP.&quot;}&#x27;

Plan operations

Agents can inspect and preflight plan access without leaving MCP:bash favcrm tool call get_plan_status &#x27;{}&#x27; favcrm tool call check_plan_operation &#x27;{&quot;toolName&quot;:&quot;create_account&quot;}&#x27; favcrm tool call list_plan_options &#x27;{}&#x27; favcrm tool call create_plan_upgrade_link &#x27;{&quot;planCode&quot;:&quot;favcrm-lite&quot;,&quot;billingCycle&quot;:&quot;monthly&quot;,&quot;confirm&quot;:true}&#x27;

Use check_plan_operation before writes that may hit module, scope, subscription, or quota gates. If the result includes upgradeAction, show the user the returned action. Stripe links are only created by create_plan_upgrade_link with confirm=true.


Auth modes

Token kind Lifetime Use case
fav_mcp_* API key Long-lived, revocable Cursor, Windsurf, Zed, Continue.dev, scripts
fav_v0_* partner token Per-Vercel-project, scoped v0 / Vercel install only
OAuth bearer (15-min JWT + 30-day refresh) Short-lived Claude Connectors (Phase 3), ChatGPT Apps
OTP-issued JWT (60 min) Short-lived Interactive humans (merchant portal exchange)

Marketplace tokens (fav_v0_*, OAuth-issued) are hard-blocked from superadmin tools (raw SQL, plan management) regardless of underlying scopes — defence in depth at the request layer, not just per-token RBAC.


Pricing

Tier Price Limits
Free $0 100 customers · 200 bookings/mo · 1k MCP calls/mo
Lite $19 / mo 1 seat · email comms · BYO-AI via your agent
Starter $49 / mo 3 seats · 1M AI credits · WhatsApp + SMS · meeting notes
Enterprise Custom Unlimited seats · multi-location · custom routing

Full table: favcrm.io/pricing.


Issues / contributions

  • Bugs in tool behaviour or MCP transport: open an issue here.
  • Examples for a new client (Cline, Replit Agent, Roo, etc.): PRs welcome under examples/.
  • Agent workflow skills: PRs welcome under skills/.
  • Contribution guidelines: CONTRIBUTING.md.
  • Security reports: please follow SECURITY.md; do not open public vulnerability issues.
  • Server bugs / new tool requests / commercial questions: dev@favcrm.io.

Links

  • favcrm.io — landing page
  • favcrm.io/integrations/vercel · /cursor · /chatgpt — per-platform install guides
  • favcrm.io/developers — full developer docs
  • favcrm.io/pricing — pricing matrix
  • favcrm.io/privacy-policy · /terms-of-use

Brand assets

Marketplace-ready 1:1 icons with background plate, in assets/:

File Use
assets/icon.png 512×512 PNG — Cursor / Smithery / mcp.so listing
assets/favcrm-icon-256-dark.svg 1:1 SVG, ink plate, light glyph — most marketplaces
assets/favcrm-icon-256-light.svg 1:1 SVG, canvas plate, ink glyph — light-themed UIs
assets/favcrm-icon-256-dark.png 256×256 PNG fallback

All icons are 1:1 aspect ratio with rounded-square plate (48px corner radius on 256-unit grid) and centered "fav." wordmark glyph.

License

This repo (docs + examples) is MIT — see LICENSE. The hosted MCP server is proprietary FavCRM SaaS; install requires a FavCRM account.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
FavCRM 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

FavCRM 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

FavCRM 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

FavCRM 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

FavCRM 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、Cline、Gemini CLI、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

FavCRM 能提供哪些能力?

资料显示能力标签包括 mcp server、crm、scheduling、whatsapp、invoicing、small business。具体工具清单以官方文档为准。

FavCRM 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。