Ask EspoCRM for the latest on an account, its open opportunities and cases.
Connect EspoCRM with your host and an API user's key and Memtro reads accounts, contacts, leads, opportunities, cases, tasks, meetings and custom entities, a record's related records and its stream. Address fields are never read, and phone numbers only when asked. The key does exactly what its role allows. The hourly sync writes records into memory. When you ask, and once an administrator has granted them by name, it can create, update or delete a record, link or unlink related records, and post a note to its stream, which notifies followers. A deleted record disappears for every user.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right EspoCRM tool, reads what it needs, and answers with the source cited.
These tools change something in EspoCRM. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once EspoCRM is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
EspoCRM + MemtroWhat's the latest on the Acme opportunity?
Which open opportunities are past their close date?
What cases has Brightwave Ltd raised this quarter?
Post a note on the BigCo account that the renewal call moved to Thursday
Create a task for Dan Fletcher to send the Northwind quote by Friday
Ahead of a renewal call the account manager asks what has happened with Northwind. Memtro reads the account's stream and its open opportunity and cases: a pricing email last Tuesday, the stage moved to Negotiation, and one support case still open.
After the meeting Priya Sharma asks Memtro to note on the Acme opportunity that legal review starts next week and move its stage to Proposal. With the actions granted, Memtro posts the note to the record's stream, where followers are notified inside EspoCRM, and updates the stage. Nothing goes to the customer.
The teams that lean on EspoCRM most, a question each of them asks, and what they connect beside it.
A record in EspoCRM is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Capsule CRM
Copper
Freshsales
Dialpad
folk
Insightly
Nutshell
Vitally
Nimble
OnePageCRM
Salesflare
CloudTalk
Hunter
Lusha
Ontraport
Reply
Streak
Planhat
Bloomerang
Givebutter
Raisely
People Data Labs
Planning Center
ChurchSuite
Affinity
Kommo
Pipeline CRM
KeapAs an EspoCRM administrator open Administration → Roles → Create Role, allowing reads on the entities Memtro should see, and create, edit or delete only where you want it
Open Administration → API Users → Create API User, choose API Key, give it the role, save and copy the key from its detail view
In Connections → EspoCRM in Memtro type the Host name of your Site URL only, public with a trusted certificate, plus the subdirectory if any, and paste the API key
Ask what the latest is on the Acme opportunity
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The EspoCRM tools are the same everywhere.
Only when you ask, and only what it has been granted: create a record of any entity the API user's role allows (not users, roles, settings or emails); update a record's fields (the values sent replace the old ones); delete a record; post a note to a record's stream; relate a record to others through a link; remove the relationship between records. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed EspoCRM records into memory as entities.
Host and API key. As an EspoCRM administrator open Administration → Roles → Create Role, allowing reads on the entities Memtro should see, and create, edit or delete only where you want it.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time