FavCRM MCP — install snippets, examples, docs for the Model Context Protocol server at api.favcrm.io/mcp
This repository also configures its own agents. See what mcp tells them →
Skill Codex
Use when a new user wants to register for FavCRM from inside an MCP client, create a FavCRM workspace, request or verify signup OTP, receive a favmcp API key, or continue setup after agentic registration.
Skill Codex
Use for invoices, payments, products, orders, promotions, subscriptions, overdue follow-up, and commerce operations in FavCRM.
Skill Codex
Use for service setup, availability, booking lifecycle, cancellations, no-shows, reminders, and daily booking operations in FavCRM.
Skill Codex
Use for FavCRM dashboards, weekly snapshots, KPI summaries, revenue, bookings, invoices, subscriptions, customer growth, and operational risk reports.
Skill Claude CodeCodex
Use when checking or connecting FavCRM communication channels, especially WhatsApp Business Embedded Signup from an MCP client or the favcrm CLI.
Skill Codex
Use for FavCRM marketing campaigns, customer reactivation, broadcasts, WhatsApp, SMS, email, inbox replies, and approval-gated customer communications.
Skill Codex
Use for FavCRM blog posts, CMS content blocks, landing-page content, AI-generated images, post publishing, post updates, and content workflows.
Skill Codex
Use for customer search, member profiles, tags, tiers, loyalty, segments, onboarding, retention, and customer 360 summaries in FavCRM.
Skill Codex
Use for training the FavCRM AI agent with URLs or pasted text, listing knowledge documents, checking ingestion status, and pruning outdated knowledge.
Skill Codex
Use for FavCRM deals, pipeline stages, internal tasks, follow-ups, owners, workspace switching, and operational handoffs.
Skill Claude CodeCodex
Use when inviting a teammate to FavCRM, generating a one-time team invite token, accepting an invite, verifying an emailed invite OTP, or issuing an MCP API key for an invited team member.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: