Demo CRM MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRM_MCP_DB | No | Path to the SQLite file, created and seeded if missing. | demo_crm.db |
| CRM_MCP_READ_ONLY | No | Set to 1 to block all write tools. | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_leadsB | Search leads by text, status, state or owner. Newest first. |
| get_leadB | Get one lead with its owner and notes. |
| find_duplicatesA | Check an existing lead against every other lead and explain any likely duplicates. |
| recommend_salespersonB | Rank salespeople for a lead by territory coverage and current workload. |
| pipeline_summaryB | Lead counts by status and source, unassigned open leads, and win rate. |
| create_leadA | Create a lead. Runs duplicate detection first and refuses high-confidence duplicates unless allow_duplicate is true. |
| update_lead_statusC | Move a lead to a new pipeline status. |
| add_noteC | Add a note to a lead. |
| assign_leadA | Assign a lead to a salesperson (use recommend_salesperson first). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| daily_triage | Walk through new and unassigned leads and suggest next actions. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| CRM schema | Field names, allowed statuses and how duplicate detection works. |
| Recent changes | The 20 most recent changes made through this server. |
TDQS
Scored across 9 tools
Most tools have clearly distinct resource+action targets (search, get, create, add_note, assign, summarize). Minor overlap exists: find_duplicates partially duplicates the duplicate check built into create_lead, and assign_lead vs update_lead_status both mutate a lead's fields, though descriptions clarify intent.
The set is overwhelmingly consistent snake_case verb_noun (search_leads, get_lead, create_lead, assign_lead, add_note). The only deviation is pipeline_summary, which is a bare noun phrase without a verb, but it remains readable and predictable.
Nine tools is well-scoped for a CRM server, covering discovery, reading, mutation, and analytics without redundancy. Each tool earns its place and none feels like padding.
Core lead lifecycle is covered: create, search, get, status update, note, assignment, duplicate check, plus a pipeline analytics view. Gaps include no delete/archive lead, no general field-edit tool beyond status, and no way to list or manage salespeople outside recommend_salesperson.