Before the call
Five minutes before a discovery call the founder asks what the prospect said when booking. Memtro reads the booking's form answers: company size, the problem they want solved and the meeting link, so the call starts informed.
Your Cal.com bookings, who is coming and when, remembered as they are made.
Connect Cal.com with an API key and Memtro reads your event types, your bookings past and upcoming with attendees and cancellation reasons, one booking's form answers, and your availability schedules. Every hour the sync writes each new booking into memory as an event. When you ask, and once an administrator has granted each action by name, it can book, move, confirm, decline or cancel bookings and add guests, and Cal.com emails the attendees, who may be outside the company, in your name. It can also record no-shows and create, change or permanently delete event types and schedules.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Cal.com tool, reads what it needs, and answers with the source cited.
These tools change something in Cal.com. 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.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Cal.com for you. Each event can start a job, with the event as its input. Cal.com signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Cal.com 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.
Who have I got booked for tomorrow, and where are the meetings?
What did Jonas Weber answer on the booking form for Thursday's demo?
Which bookings were cancelled in October, and why?
Move my Thursday demo with Dana Kowalski to Friday at 10:00
Cancel the 15:00 intro call with Mia Chen on 12 November and say I am unwell
Five minutes before a discovery call the founder asks what the prospect said when booking. Memtro reads the booking's form answers: company size, the problem they want solved and the meeting link, so the call starts informed.
Sam Okafor asks Memtro to move Thursday's demo with Dana Kowalski to Friday at 10:00. Memtro reads the booking, confirms the time with Sam and reschedules it. Cal.com makes a new booking at 10:00, marks the old one rescheduled and emails Dana and Sam the change.
The teams that lean on Cal.com most, a question each of them asks, and what they connect beside it.
A record in Cal.com 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.
In Cal.com go to Settings → Developer → API keys → Add, give the key a name and an expiry (or never), and copy it: it is shown once
In Memtro open Connections → Cal.com, paste the API key and connect. The key acts as you, so bookings it changes are changed in your name, and Cal.com allows it 120 requests a minute
Self-hosted Cal.diy? Add the API URL its API v2 is served at (usually your site plus /api/v2)
Ask who you are meeting tomorrow
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Cal.com tools are the same everywhere.
Only when you ask, and only what it has been granted: cancel a booking, with a reason sent to its attendees; book a slot on an event type for an attendee (Cal.com emails them and the host); move a booking to a new time (attendees are emailed); confirm a booking waiting for approval (the attendee is emailed); decline a booking waiting for approval, with a reason the attendee is sent; cancel a booking and email the attendee a link to rebook; record the host or attendees as absent from a booking; add guests to a booking (each is emailed an invite); create an event type; change an event type's title, link, length, notice, buffers, schedule or visibility; delete an event type, permanently; create an availability schedule; change an availability schedule's hours, overrides, timezone or default; delete an availability schedule, permanently. 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 Cal.com records into memory as entities.
API key. In Cal.com go to Settings → Developer → API keys → Add, give the key a name and an expiry (or never), and copy it: it is shown once.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Cal.com for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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