Your CRM as a
Claude Connector.
Standard OAuth 2.0 with PKCE-S256, RFC 7591 dynamic client registration, family-tracked refresh rotation. 28 curated MCP tools land in Claude — customers, bookings, loyalty, invoices, comms — scoped per workspace, revocable from your dashboard.
Listing pending Anthropic Connectors Directory review · ~2 week review cycle
$ curl https://api.favcrm.io/.well-known/oauth-authorization-server
"issuer": "https://api.favcrm.io",
"authorization_endpoint": "…/oauth/authorize",
"token_endpoint": "…/oauth/token",
"registration_endpoint": "…/oauth/register",
"code_challenge_methods_supported": ["S256"]
→ Claude reads this to wire the OAuth dance.
28 curated MCP tools · OAuth 2.0 + PKCE-S256 · refresh rotation with reuse detection
https://api.favcrm.io/mcp PricingReal CRM verbs. Scoped per workspace.
Every primitive a service business needs — typed, annotated, gated by OAuth scopes you explicitly approved.
From Add Connector to first call in 90 seconds.
Standard OAuth flow — no API keys to copy, no config files to edit. The Connectors Directory listing rolls out post-Anthropic review.
Standard OAuth 2.0. No magic.
RFC 6749 + 7636 + 7591 + 7009 + 8414. Same shape Anthropic, GitHub, and Stripe use. Discovery → register → authorize → token.
28 tools approved for Claude.
Read-mostly with safe writes. Annotations on every tool — destructive ops gated behind explicit confirmation in chat.
Need full write access (campaigns, broadcasts, payments)? Use Cursor or Vercel for the full 128-tool catalog.
Built so the Anthropic reviewer doesn't have to chase us.
PKCE + scope consent + refresh rotation + DCR quarantine — built in to pass Connector review on the first submission.
Read the Privacy Policy and Terms of Use.
Free for prototypes. Paid when you ship.
Sign up free. Upgrade to Lite for a real workspace, or Starter for bundled AI agent and meeting notes — same dashboard, no re-install.
OAuth, scopes, and trust.
Anthropic's Connector review covers OAuth shape, scope clarity, callback URL, and revocation. Below answers map to those checkpoints.
- Q.01 What is the FavCRM Claude Connector?
- A custom MCP connector for Claude.com / Claude Desktop. The Claude agent calls FavCRM's 28 curated MCP tools (read-mostly + safe writes; destructive ops gated) directly from chat — customers, bookings, loyalty, invoicing — without leaving the conversation.
- Q.02 How does the OAuth flow work?
- Authorization Code with PKCE-S256 (RFC 7636). Claude initiates the dance via /.well-known/oauth-authorization-server (RFC 8414); FavCRM's authorization endpoint redirects back to claude.com/api/mcp/auth_callback with a single-use code; Claude exchanges the code for a 15-minute access JWT + 30-day refresh token. Refresh-token rotation is family-tracked — token reuse invalidates the entire family.
- Q.03 Is Dynamic Client Registration supported?
- Yes. RFC 7591. Claude (or any new agentic client) calls POST /oauth/register with client_name + redirect_uris and receives a client_id. New DCR clients are quarantined for 24 hours: read-only scopes only, write access requires explicit user re-consent after the cooldown. Per-IP rate limit: 50 registrations per day.
- Q.04 When does the Claude Connector launch?
- Pending Anthropic's connector-directory review. The OAuth backend (authorize / token / register / revoke / well-known) is live at api.favcrm.io. Submission to mcp-review@anthropic.com includes the verified callback URL, scope catalog, privacy policy, and EULA. Until approved, advanced users can wire FavCRM into Claude Desktop's claude_desktop_config.json via the same Bearer-header pattern used for Cursor (community-only path).
- Q.05 What scopes does Claude request?
- mcp.read for catalog discovery and read-only tools, mcp.write for safe writes (create_booking, attach_tags, send_whatsapp_message). Destructive scopes (cancel/refund/delete) require explicit user re-consent per session. Full scope catalog at /.well-known/oauth-authorization-server.
- Q.06 What about user revocation?
- The Connected Apps page in the merchant portal lists every authorized client. Revocation cascades: kills all refresh-token families for (user, client), invalidates active access tokens within their 15-minute TTL. RFC 7009 token revocation endpoint is also exposed at /oauth/revoke for programmatic use.
- Q.07 How is this different from Anthropic's own connectors?
- FavCRM is a third-party connector built specifically for service businesses — beauty, fitness, tutoring, retail, hospitality, professional services. Anthropic's first-party connectors (Google Drive, Slack, GitHub) target generic productivity. FavCRM provides a domain-specific tool catalog: bookings + customers + loyalty + invoicing as first-class verbs, not files-and-folders.
- Q.08 What does it cost?
- Free tier: 100 customers, 200 bookings/month, 1k MCP calls/month, no credit card. Paid plans from $19/mo (Lite — 1 seat) to $49/mo (Starter — 3 seats, WhatsApp + SMS, 1M AI credits). Same plans across all platforms.
Verified . OAuth metadata at /.well-known/oauth-authorization-server.
Add to Claude.
Authorize the verbs.
One install. OAuth handshake. Claude runs a real CRM backend from the next prompt onwards.