EspoCRM Assistant
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ESPOCRM_URL | Yes | Existing EspoCRM base URL. HTTPS is required unless ESPOCRM_ALLOW_HTTP=1. | |
| ESPOCRM_MCP_HOST | No | Streamable HTTP MCP bind host. | 127.0.0.1 |
| ESPOCRM_MCP_PATH | No | Streamable HTTP MCP path. | /mcp |
| ESPOCRM_MCP_PORT | No | Streamable HTTP MCP port. | 8080 |
| ESPOCRM_ALLOW_HTTP | No | Set to '1' only for disposable local testing against HTTP EspoCRM. | |
| ESPOCRM_READ_API_KEY | Yes | Read-only EspoCRM API key used by assistant-visible tools. | |
| ESPOCRM_READ_SECRET_KEY | No | HMAC secret for the read API user (required if READ_AUTH_METHOD is hmac). | |
| ESPOCRM_READ_AUTH_METHOD | No | Authentication method: 'apikey' or 'hmac'. | apikey |
| ESPOCRM_MCP_STATELESS_HTTP | No | Stateless HTTP mode. | 1 |
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 |
|---|---|
| crm_searchC | Search allowlisted CRM records without mutation. |
| crm_getC | Read one allowlisted CRM record. |
| crm_metadataA | Read allowlisted field metadata for one entity. |
| crm_duplicate_candidatesC | Find possible duplicates from identifying fields. |
| crm_prepare_changeC | Prepare and hash a non-mutating create or update change set. |
| crm_export_csvC | Export validated change sets as CSV for manual import. |
| crm_prepare_lead_conversionC | Prepare linked Lead-to-Opportunity change sets for human approval. |
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 7 tools
Each tool targets a distinct CRM operation: duplicate detection, CSV export, single record retrieval, metadata, change preparation, lead conversion preparation, and search. No overlap in functionality; an agent can easily distinguish them.
All tools use the 'crm_' prefix with a verb-based name, e.g., 'crm_search', 'crm_get'. However, 'crm_get' lacks a noun (like 'record'), and 'crm_metadata' uses a noun as a verb, which is slightly inconsistent but still clear.
Seven tools is well-scoped for a CRM assistant focused on read, search, duplicate detection, and preparation of change sets for human approval. No unnecessary tools, and the count supports a focused workflow.
The toolset covers core read, search, metadata, duplicate checking, change preparation, lead conversion preparation, and export. Missing direct mutation (create/update/delete) is intentional for a non-mutating, human-approval workflow. A minor gap is the lack of a list-all-entities tool, but search can compensate.