Reads the connected user's profile and access control rules plus the instance's system metadata, confirming the connection is live and scoped.
2actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Retrieve current user data including token, ACL, and preferences.
Each card is one request a support team gets, and the Espocrm actions Ayro runs to close it.
After authentication, Ayro reads the current user's session profile - name, token, and preferences - so a team can verify the credentials landed on the intended account rather than a leftover service user.
Get App User returns the access control rules attached to the session, so Ayro can report the real permission ceiling of the connection before anyone assumes it can reach every record in the CRM.
Ayro reads the instance's system metadata, which only succeeds when the credentials are valid and EspoCRM is responding, so a broken connection surfaces as a clear answer rather than a silent failure later.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Espocrm actions it has and picks the ones a request needs.
Authorize the Espocrm account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Espocrm actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeEspocrm · Ayro
What can you do in Espocrm without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Espocrm.
Not with the actions this connection currently exposes. The toolkit has two - Get App User and Get Metadata - and both are account-level reads. Ayro can confirm who it is authenticated as and what that user may access, but reading or updating CRM records is not covered here.
All 2 actions your agent can call on Espocrm, straight from the live MCP connection.
Retrieve current user data including token, ACL, and preferences.
Test connectivity to the Docparser API by calling the ping endpoint.
Same connection, same setup. Pick the next one your team already uses.
Answers which lists a company or person appears on, reads their entries and field data, and returns opportunities and saved view rows.
Finds the person behind an inbound message, logs the conversation as a protocol, files email against the right deal, and merges duplicate contacts and companies.
Finds an existing contact, creates the person and company records when they are new, and writes the note that captures what a conversation revealed.
Creates leads, contacts, and companies as a conversation qualifies, files the follow-up task, and keeps the Kommo AI knowledge base stocked.
Opens deals and company records, corrects account details, and reads the booked follow-up straight from the live pipeline.
Reads order and shipment status, places repeat orders with payment, merges duplicate customer records, and escalates with a task attached.

Authorize the account and your agent has all 2 actions from the first conversation.
