Can Lyro look up a contact, lead, or opportunity in 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. Lyro can confirm who it is authenticated as and what that user may access, but reading or updating CRM records is not covered here.

What exactly does Get App User return?

The current user's session profile: their access token, their ACL (the access control rules deciding which entities and fields they can see), and their preferences. It is designed to run after authentication succeeds, which makes it the check that the connection resolved to the right user.

Whose permissions does Lyro inherit in EspoCRM?

Those of the single user behind the credentials you connect. Get App User returns that user's ACL, so anything this connection can reach is bounded by that one account's access rather than an administrator-wide view of the CRM.

How would we tell that the EspoCRM connection has broken?

Get Metadata is the connectivity signal: it only returns when the credentials are valid and the instance is reachable. If that succeeds but Get App User does not, the problem points at the user or its permissions rather than at the network or the instance being down.

Espocrm MCP integration

Reads the connected user's profile and access control rules plus the instance's system metadata, confirming the connection is live and scoped.

Connect Espocrm See all integrations

2actions available

What your agent can do with Espocrm

Every action runs live through MCP. Nothing to build, nothing to maintain.

Retrieve current user data including token, ACL, and preferences.

See all 2 actions

How businesses use Espocrm + Lyro

Each card is one request a support team gets, and the Espocrm actions Lyro runs to close it.

Confirm which EspoCRM user the connection resolves to
After authentication, Lyro 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 UserGet Metadata
Check what that user is actually permitted to see
Get App User returns the access control rules attached to the session, so Lyro can report the real permission ceiling of the connection before anyone assumes it can reach every record in the CRM.
Get App UserGet Metadata
Verify the instance is reachable before relying on it
Lyro 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.
Get MetadataGet App User

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Espocrm actions it has and picks the ones a request needs.

01
Connect Espocrm
Authorize the Espocrm account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Espocrm actions that close it and chains as many as the request needs.
03
Watch it work
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 free

Espocrm · Lyro

Everything else about Espocrm

Setup, permissions, and the limits of what Lyro 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. Lyro can confirm who it is authenticated as and what that user may access, but reading or updating CRM records is not covered here.

Every action available in Espocrm

All 2 actions your agent can call on Espocrm, straight from the live MCP connection.

Get app user
Retrieve current user data including token, ACL, and preferences.
Get metadata
Test connectivity to the Docparser API by calling the ping endpoint.