Crm Cli MCP Server

Crm Cli MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A local-first personal CRM that lives in your terminal. Manage contacts, organizations, interactions, deals, and tasks — all from the command line. Ships with a built-in MCP server so AI agents like.

What you get

• People & Organizations — — contacts with full profiles, linked to companies
• Interaction Log — — track calls, emails, meetings, notes, and messages
• Deals & Pipeline — — sales opportunities with stages, values, and a pipeline view
• Tasks — — follow-ups with due dates, priorities, and completion tracking
• Tags — — labels on any entity for flexible organization
• Relationships — — person-to-person links (colleague, mentor, referred-by, …)

What the assistant can call

Once Crm Cli is connected, these are the calls the assistant has available:

• crm_person_search — Search people by name, email, tag, org
• crm_person_get — Get full details for a person
• crm_person_create — Create a new person
• crm_person_update — Update person fields
• crm_person_delete — Delete (archive) a person
• crm_person_relate — Create relationship between people
• crm_org_search — Search organizations
• crm_org_get — Get org details with members
• crm_interaction_log — Log a call, email, meeting, or note
• crm_interaction_list — List interactions for a person
• crm_search — Cross-entity full-text search
• crm_context — Full person briefing

Configuration and credentials

You will need one environment variable: CRM_DB. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Crm Cli's toolset — crm_person_search, crm_person_get, crm_person_create and 11 more — is a fair guide to whether it matches your workflow. It is maintained by jdanielnd; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Crm Cli.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the crm cli mcp server does with a few real requests.