SavvyCal MCP server
SavvyCal in any MCP client, through Memtro: SavvyCal does not publish this server. Memtro's SavvyCal connector reads SavvyCal 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
SavvyCal scheduling: meetings booked in a date window with who is attending, their state (confirmed, canceled, awaiting approval) and the link they came through, the user's scheduling links with durations, and a link's open slots. Can book a meeting on a link, cancel a meeting, and create, edit, duplicate, enable or disable, or delete a link, each only when asked.
Reads
savvycal_eventsSavvyCal meetings whose start falls in a date window, earliest first: title, state, start and end, the link booked through, organizer, attendees…savvycal_linksSavvyCal scheduling links: name, private name, slug, state (active, pending, disabled, archived), default and offered durations…savvycal_link_slotsOpen time slots on a SavvyCal scheduling link between two times: start, end, duration and rank (1 is the organiser's preferred…
Acts, when you ask
These change something in SavvyCal. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
savvycal_create_eventBook a meeting on a SavvyCal scheduling link for a guest.savvycal_cancel_eventCancel a booked SavvyCal meeting.savvycal_create_linkCreate a SavvyCal scheduling link, in the user's personal scope or, with team_slug, in a team.savvycal_update_linkChange a SavvyCal scheduling link's public name, private name, description, slug (which changes its public URL, breaking the old one) or type.savvycal_duplicate_linkMake a copy of a SavvyCal scheduling link with the same settings.savvycal_toggle_linkSwitch a SavvyCal scheduling link on or off: an active or pending link is disabled (it stops taking bookings)…savvycal_delete_linkDelete a SavvyCal scheduling link.
Connect it
First connect SavvyCal on Dashboard → Connections, then add Memtro to your client once. The SavvyCal tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=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-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
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 SavvyCal 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 is booked on my SavvyCal next week?
- › Which meetings are awaiting approval?
- › How many meetings were cancelled or rescheduled this month?
- › What durations does my intro call link offer?
- › Switch off my intro call link until I am back
Questions
- Is this an official SavvyCal MCP server?
- No. It is Memtro's MCP server with Memtro's SavvyCal connector behind it: the connector reads SavvyCal through its API with the credentials you connect on Dashboard → Connections, and SavvyCal 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 SavvyCal?
- Only when you ask, and only what it has been granted: book a meeting on a scheduling link for a guest (the guest is likely to be emailed an invitation); cancel a booked meeting (attendees are likely to be told); create a personal or team scheduling link; rename a scheduling link or change its slug, description or type; duplicate a scheduling link; disable or re-enable a scheduling link; delete a scheduling link (its booking page stops working). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- 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.