Salesmate MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SALESMATE_API_KEY | Yes | Your Salesmate Session Key (not the Access or Secret key). Required for authentication. | |
| SALESMATE_BASE_URL | Yes | Your Salesmate workspace base URL, e.g., https://yourcompany.salesmate.io. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_contactsB | Search for contacts in Salesmate by name, email, or company. Args: query: Free-text search term. Returns: A structured object with the matching contacts. |
| get_contactA | Retrieve a single contact's full details by its id. Args: contact_id: The numeric id of the contact. Returns: A structured object containing the contact record. |
| list_dealsA | List deals, optionally filtered to a specific contact. Args: contact_id: Optional contact id to filter deals by. Returns: A structured object with the matching deals. |
| get_dealA | Retrieve a single deal's full details by its id. Args: deal_id: The numeric id of the deal. Returns: A structured object containing the deal record. |
| update_deal_stageA | Move a deal to a new pipeline stage. Args: deal_id: The numeric id of the deal to update. stage: The name of the target stage. Returns: A structured object containing the updated deal record. |
| create_taskA | Create a task in Salesmate. Args: title: The task title. due_date: ISO-8601 due date (e.g. '2026-07-01' or '2026-07-01T09:00:00Z'). contact_id: Optional contact id to associate with the task. Returns: A structured object containing the created task. |
| create_noteB | Create a note attached to a contact. Args: contact_id: The numeric id of the contact to attach the note to. note: The note body text. Returns: A structured object containing the created note. |
| get_recent_activitiesB | Get recent activities (calls, meetings, emails) for a contact. Args: contact_id: The numeric id of the contact. Returns: A structured object with the contact's recent activities. |
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 8 tools
Each tool targets a distinct operation (create note, create task, get contact, get deal, get activities, list deals, search contacts, update deal stage) with no overlap.
All tool names follow a consistent verb_noun snake_case pattern (e.g., create_note, get_contact, update_deal_stage), making it predictable.
8 tools is well within the 3-15 range, covering core CRM entities (contacts, deals, tasks, notes) without being excessive.
Missing fundamental CRUD operations: no create or update for contacts, no create deal, no delete functionality. Users cannot create new contacts or deals, only attach notes/tasks to existing ones.