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.
Agentic CRM for service businesses — bookings, customers, WhatsApp, loyalty, invoicing.
2026-11-08
स्टार
—
टूल
—
अपटाइम
—
The endpoint supports purpose-built tool profiles selected with ?profile=<name> 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:
# 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.
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:
claude.com → Connectors → Add custom connector
URL: https://api.favcrm.io/mcp
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:
ChatGPT → Tools menu → Apps → search "FavCRM"
Add → OAuth handshake → workspace selector
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:
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.
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:
favcrm tool call report_agent_issue '{"title":"Missing account creation MCP tool","severity":"high","area":"mcp_tool_missing","expectedBehavior":"Agent can create an account via MCP only.","actualBehavior":"Agent had to use SDK fallback.","stepsTried":["Listed tools","Tried create_contact"],"aiAnalysis":"Account creation exists in backend services but was not exposed in MCP."}'
Plan operations
Agents can inspect and preflight plan access without leaving MCP:
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.
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
सवाल
FavCRM कैसे इंस्टॉल करें?
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए http कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
क्या FavCRM के लिए API key चाहिए?
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
FavCRM कौन सा ट्रांसपोर्ट इस्तेमाल करता है?
FavCRM तक HTTP से पहुँचा जाता है।
FavCRM की पिछली जाँच कब हुई थी?
पिछली जाँच 2026-11-08 को हुई। Agentic CRM for service businesses — bookings, customers, WhatsApp, loyalty, invoicing.