Google Calendar MCP server

What the model can do

Read calendars, events and when people are free, and create, change or cancel an event or answer an invitation to one (uses the same Google OAuth client as Gmail).

Reads

• gcal_calendarsList the calendars the account can see.
• gcal_eventsEvents in a time window (defaults: now → 14 days ahead), optionally filtered by free text.
• gcal_eventFull details of one event by id.
• gcal_free_busyWhen this account — and anybody else whose address is given — is busy in a window, and the gaps in which every one of them is free.

Acts, when you ask

These change something in Google Calendar. 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.

• gcal_scheduleCreates an event in the connected calendar, or changes one when event_id is given (only the fields passed are changed).
• gcal_respond_eventAnswers an invitation on this calendar — accept, decline, or tentative — with an optional note shown to the organiser.
• gcal_cancel_eventCancels an event and tells the guests.

Connect it

First connect Google Calendar on Dashboard → Connections, then add Memtro to your client once. The Google Calendar tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

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 Google Calendar 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

• › What do I need to know for tomorrow's meetings?
• › When am I next meeting BigCo?

Questions

Is this an official Google Calendar MCP server?

No. It is Memtro's MCP server with Memtro's Google Calendar connector behind it: the connector reads Google Calendar through its API with the credentials you connect on Dashboard → Connections, and Google Calendar 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 Google Calendar?

Only when you ask, and only what it has been granted: create an event, or change one; cancel an event and tell the guests; accept, decline or tentatively accept an invitation. 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.

Other MCP servers · Email, calendar and chat

• AgentMail MCP server
• Gmail MCP server
• Slack MCP server
• Outlook Mail MCP server
• Outlook Calendar MCP server
• Microsoft Teams MCP server