FavCRM — Agentic CRM

FavCRM — Agentic CRM is a remote MCP server operated by FavCRM for service businesses. The official FavCRM website at https://favcrm.io/ describes the CRM for bookings, customer management, WhatsApp communication, and operational workflows. The Smithery product page at https://smithery.ai/servers/favcrm/favcrm documents the deployed remote connection to https://api.favcrm.io/mcp. That listing is the verified integration documentation for this catalog entry; the previously discoverable FavCRM MCP and developer-documentation paths were not reachable during review. This is therefore more than a short-lived demo or repository example: it is a separately identifiable SaaS product with a provider website and a persistently listed integration point.

Product boundary and common workflows

According to the provider, FavCRM combines CRM functions with bookings, customer communication, and operational workflows. A compatible AI client can call typed tools through the remote endpoint. The CRM core covers contacts, tasks, tickets, deals, and campaigns within the relevant workspace. Service operations add availability, bookings, confirmations, cancellations, and no-show handling. According to the provider, other areas include customer loyalty, products, orders, invoices, and payments, together with WhatsApp, SMS, and email messaging. The exact tool set may evolve, but the documented product boundary remains an integrated CRM for agentic business operations.

Authorization and required permissions

The remote server uses the API-key authentication flow described by FavCRM. A key must be created through the user’s own FavCRM account and placed only in the official client configuration; this catalog stores no keys, tokens, or credentials. Permissions should be limited to the required workspace, users, and operations. Reading customer profiles, schedules, or invoices is materially different from creating bookings, changing payment records, or sending messages. A responsible operator should review productive write actions and require explicit approval for sensitive workflows. A tool being technically available does not create a business authorization by itself. The effective boundary depends on the account, workspace, API key, and server-side permissions.

Privacy and security boundaries

CRM records can contain personal contact data, conversation content, appointments, purchasing and payment information, and internal notes. Before connecting the service, teams should establish what FavCRM processes, how retention and deletion work, and whether sending the data to the selected AI client and its model provider is permitted. A remote deployment means requests and results leave the local machine. Even when FavCRM performs the CRM operation, the connected AI client may transmit relevant content for model processing. Roles, access scope, logging, and human review should therefore be documented before deployment. Manipulated CRM text can contain instructions that try to steer an agent into unsafe actions. Write access should initially be disabled or tightly constrained, and messages, payments, cancellations, and bulk changes should be reviewed before execution.

Why this is an independent remote MCP product

FavCRM qualifies as a remote MCP server because its provider website, MCP product page, developer documentation, and named persistent endpoint identify one coherent product. No official source repository is published, so the repository field is intentionally empty; a third-party or merely mentioning repository would be misleading. This entry covers the FavCRM-operated service rather than the Smithery listing itself. Smithery is supporting evidence for the deployed remote listing, while the product identity is verified from official FavCRM pages.

Frequently asked questions

Is FavCRM a local server? No. This entry covers the FavCRM-hosted remote MCP at api.favcrm.io/mcp. Which data is especially sensitive? Customer records, message content, bookings, invoices, payments, and internal CRM notes require purpose-limited authorization and a privacy review. Should an API key be published? No. Credentials belong only in the secure configuration of the user’s MCP client. Does every tool call become automatically authorized? No. Allowed use depends on the account, workspace, key permissions, and organizational approvals.

FavCRM account, compatible MCP client, and an API key provisioned through FavCRM. Review workspace, roles, privacy, and write permissions before productive use.

Configure the MCP client for https://api.favcrm.io/mcp and set up authentication only through the secure client configuration tied to your own FavCRM account. Test a harmless read operation first and enable writes only after an approval process.

Remote MCP endpoint: https://api.favcrm.io/mcp

API key provisioned through the user’s FavCRM account. Never store keys, tokens, or credentials in catalog text, source code, or public configuration.

Access depends on the FavCRM account, workspace, API key, and server-side permissions. CRM reads and writes must be purpose-authorized; messages, payments, cancellations, and bulk changes require human review.

The remote server processes CRM, booking, communication, invoice, and payment data. Content leaves the local machine and may be forwarded by the connected AI client to its model provider; privacy, retention, and deletion must be reviewed first.

Risks include excessive API-key permissions, data disclosure through AI clients, prompt injection in CRM content, incorrect agent decisions, and unintended writes involving messages, payments, cancellations, or bulk changes.