EspoCRM

Getting a key

1. In EspoCRM go to Administration → API Users and create an API user. Choose API Key authentication (not HMAC — this adapter sends the plain key).
2. Assign a role that grants read access to the entities the agent should see. EspoCRM enforces roles per entity and per field, so a restricted role produces fewer rows and fewer columns rather than an error.
3. Copy the generated key into ESPOCRM_API_KEY and set ESPOCRM_URL to your instance root (no trailing slash, no /api/v1).

The header is X-Api-Key.

One route shape for every entity. /api/v1/{entityType} lists, /api/v1/{entityType}/{id} reads one. That covers Account, Contact, Lead, Opportunity, Case, Call, Meeting, Task and any custom entity your instance defines — which is why espocrm_list_entities takes the entity type as a parameter.

where is an indexed array, which is awkward and worth reading once. EspoCRM expects where[0][type]=equals&where[0][attribute]=status&where[0][value]=New. Types include equals, notEquals, contains, startsWith, greaterThan, lessThan, between, isNull, isNotNull, linkedWith, today, lastXDays. The list tools below expose the first where clause directly, which covers most questions; for anything compound, EspoCRM's own documentation has the full grammar.

select keeps responses small. Without it EspoCRM returns every readable attribute, which for an Account with custom fields is a lot.

Order is orderBy plus order (asc/desc), not a single expression.

Self-hosted, which is the thing to plan for.

• On AnythingMCP Cloud the instance must be reachable from the public internet on a real hostname with a valid TLS certificate. A self-signed certificate will fail: the connector offers no trust-anything switch.
• On an internal host (crm.intern, 10.0.0.x), self-host AnythingMCP on the same network and add that host to SSRF_ALLOWED_HOSTS, or the outbound guard refuses the call before it is made.