Prep before a call
Ask what you know about tomorrow's 10:00 booking and Memtro brings the invitee's details and their form answers together with what the rest of the graph knows about them.
Every booking, who made it and why
Connect Calendly with a personal access token and Memtro can read scheduled and cancelled bookings across your organisation, the invitees behind them, the answers they gave on the booking form and the event types your team offers. Read-only: nothing is booked, moved or cancelled.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Calendly tool, reads what it needs, and answers with the source cited.
Ask what you know about tomorrow's 10:00 booking and Memtro brings the invitee's details and their form answers together with what the rest of the graph knows about them.
Each hour new cancellations become memories with the reason given, so asking why bookings fell through last month has an answer.
Questions people ask once Calendly is connected. In agent mode each one also checks the other systems that know about the same people, companies or identifiers.
Teams that get the most from Calendly in Memtro, with the rest of their stack attached.
A record in Calendly is rarely the whole story. Connect the systems that hold the rest and the agent cross-references them by default, 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.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Calendly tools are the same everywhere.
Set it up as an MCP server →Clients and agents →Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.