Bookings, CRM, payments and customer messaging — decoupled from any UI and exposed over MCP, a CLI and a REST API. Your agent-built app calls real, persisted business logic instead of mocking tables. Start free; pay only when you scale.
Point any MCP client — Cursor, Claude Code, the favcrm CLI, or a raw API call — at the FavCRM endpoint. Two calls register the workspace, you paste one 6-digit email code, and a fav_mcp_ key is yours. No form, no portal, no sales call.
{
"mcpServers": {
"favcrm": {
"url": "https://api.favcrm.io/mcp"
}
}
}Works with any AI agent.
Three fields — we write the prompt. Paste it to any AI agent and you're in.
Sign me up for FavCRM. <your business> — a beauty salon in <your city>. Connect through the MCP server at https://api.favcrm.io/mcp.
Paste it into your AI agent — Claude, Cursor, ChatGPT, anything — and ask it to set you up. It calls the signup, you paste the 6-digit code from your inbox, and your workspace is live.
Creates a free FavCRM workspace with the full 190+ tool surface. Starter, Growth, and Enterprise lift call and record limits — upgrade in-product when you scale.
Your AI-built app or agent calls FavCRM over MCP or REST. It runs the actual business logic — bookings, records, payments — and returns typed data, never stubs.
A full, typed tool surface — bookings, contacts, products, payments, messaging. Your agent discovers and calls them. No glue code, no guesswork.
Live slots, capacity, clash detection and confirmations behind one call. Stop reimplementing a calendar in every app you ship.
Every call upserts contacts, history, tags and spend — persistent records your app reads back, not mock tables that vanish on reload.
Stripe checkout, invoices and customer messaging (incl. WhatsApp) ship as part of the backend — wired, compliant, ready to call.
Claude, Cursor, ChatGPT, Codex, Windsurf, Cline — or your own. MCP is an open standard; FavCRM speaks it natively, with no SDK lock-in.
190+ tools with typed inputs and outputs. Calls return persisted records — never stubbed data your app has to pretend is real.
Prefer plain HTTP? The same operations are a documented REST API and a CLI. One backend, three ways in.
Free to start; paid plans lift the limits — see /pricing. No credit card to start, no lock-in — cancel anytime.
Connect your agent Create a free workspaceHigher call limits, more records, multiple workspaces, team seats, priority support and SLA live on Starter, Growth, and Enterprise plans.
See all plansReal slots, clash-checks and confirmations — no calendar to build.
Products, checkout and orders your agent can actually transact.
Ship a niche CRM on a backend that already persists every record.
Stand up booking + CRM + payments per client in an afternoon.
Give an assistant typed tools so it books, logs and charges for real.
Wire ops dashboards straight onto the REST API — skip the schema.
A CRM whose data and business logic are decoupled from any fixed user interface and exposed entirely through APIs. FavCRM exposes everything over an MCP server, a CLI and a REST API — so your AI agent, your AI-built app, or your own front-end drives it. Bookings, contacts, payments and messaging all run through the API layer; you bring the UI, or skip it entirely.
You skip months of work. Scheduling with clash detection, a CRM data model, payments, invoicing and customer messaging are already built, typed and persisted. Your agent calls 190+ tools instead of you designing tables, writing migrations and reconciling Stripe webhooks — and calls return real, stored records, not mock data.
MCP (the Model Context Protocol) is an open standard for exposing tools to AI agents. FavCRM is MCP-native, so any MCP client discovers and calls its 190+ tools with no glue code. You do not have to use it — the same operations are available as a documented REST API and a CLI.
The full 190+ tool surface, MCP + REST + CLI access, 100 customer records, 200 bookings/month, 10,000 AI credits/month, Stripe payments and customer messaging, on one workspace. No credit card, no time limit. Starter, Growth, and Enterprise lift the limits.
Any MCP-compatible client — Claude, Cursor, ChatGPT, OpenAI Codex, VS Code, Windsurf, Gemini CLI, Cline, Zed — plus the favcrm CLI and any raw HTTP/JSON-RPC caller. MCP is an open protocol: no vendor lock-in, bring whatever stack you already use.
No. MCP and REST are open interfaces, and your data is yours — export contacts, bookings and history at any time. There is no contract and no proprietary SDK you are forced to depend on.
Yes. Point an MCP client at the FavCRM endpoint and ask it to sign you up. It makes two calls (register_organisation_request then register_organisation_verify), you paste the 6-digit code emailed to you, and a fav_mcp_ API key lands back in the session. The favcrm CLI does the same from a terminal.
Yes. Stripe checkout and invoicing are built in (test and live modes), and customer messaging — including the official WhatsApp Business API — is part of the backend. Your app calls them; it does not reimplement them.
Connect over MCP and ship on a headless CRM that returns real records — free to start.