freshsales-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRESHSALES_DOMAIN | Yes | The Freshsales bundle domain, e.g. aevytv.myfreshworks.com | |
| FRESHSALES_API_KEY | Yes | Your Freshsales API key (Admin Settings > API Settings) |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| freshsales_searchA | Global search across Freshsales CRM (leads, contacts, deals, accounts) by name, email, phone, or company. Use this first when the user asks about a specific person or company. |
| freshsales_list_viewsA | List the saved views (filters) available for a Freshsales module, e.g. 'My Leads', 'Open Deals'. Use this to discover a view_id before calling freshsales_list_records. |
| freshsales_list_recordsA | List records (leads, contacts, deals, accounts, tasks, appointments) belonging to a saved view, with pagination. Get view_id from freshsales_list_views first. |
| freshsales_get_recordB | Fetch full details of a single lead, contact, deal, or account by its id. |
| freshsales_raw_requestA | Escape hatch for any GET endpoint under https:///crm/sales/api not covered by the other tools (e.g. '/leads/filters', '/selector/owners'). Only use when the other tools can't answer the question. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: global search, listing saved views, listing records from a view, fetching a single record by ID, and an escape hatch for arbitrary GET endpoints. No two tools overlap in functionality.
All tool names consistently follow the 'freshsales_' prefix with a verb_noun pattern (search, list_views, list_records, get_record, raw_request). The naming is uniform and predictable.
With five tools, the server is well-scoped for a read-only CRM access layer. It covers search, view discovery, record listing, and detail retrieval without unnecessary bloat.
The main read workflow (search, discover views, list records, get record details) is well covered, and raw_request provides a fallback for any missing endpoints. However, get_record does not support tasks/appointments even though list_records can return them, leaving a minor gap.