Calendly MCP server
Calendly in any MCP client, through Memtro: Calendly does not publish this server. Memtro's Calendly connector reads Calendly through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Read-only Calendly: scheduled and cancelled bookings with invitees and their form answers, event types and organisation members.
Reads
calendly_eventsScheduled Calendly bookings in a time window (default: last 30 days to 30 days ahead), newest first by start.calendly_eventOne booking by uuid with its invitees: names, emails, status, booking-form answers, reschedule/no-show flags…calendly_event_typesEvent types (booking pages) in the organisation or for the token owner: name, duration, kind (solo/group), owner, scheduling URL and whether active.calendly_membersMembers of the Calendly organisation (name, email, role, timezone, scheduling URL); needs an owner/admin token…
Connect it
First connect Calendly on Dashboard → Connections, then add Memtro to your client once. The Calendly tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
One command registers the server; the tools are then available in every session.
claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
--header "Authorization: Bearer sk-memtro-..."Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Calendly connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Who has booked a demo with us this week?
- › Why did the Acme discovery call get cancelled?
- › What did Jordan say they wanted to discuss on the booking form?
- › Which event types does the sales team offer?
Questions
- Is this an official Calendly MCP server?
- No. It is Memtro's MCP server with Memtro's Calendly connector behind it: the connector reads Calendly through its API with the credentials you connect on Dashboard → Connections, and Calendly publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Calendly?
- Not yet. Today every Calendly tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.