Creativity · MCP — server

MCP Notion Calendar Server

The MCP Notion Calendar Server integrates Notion Calendar via connected Google and Microsoft calendars, plus Notion's own event sources. It exposes read/write tools for events, availability, and scheduling links, letting an LLM automate time-blocking, meeting prep, and polite reschedules.

MCP facts

Kind: server
Ecosystem: anthropic-mcp
Language: TypeScript
Transports: stdio

Capabilities

Tools: list_events, find_availability, create_event, cancel_event, send_scheduling_link
Resources: notion-cal://event/{id}
Auth: OAuth to the underlying Google/Microsoft calendar source

Install

npx -y @community/mcp-server-notion-calendar

Configuration

{
  "mcpServers": {
    "notion-calendar": {
      "command": "npx",
      "args": ["-y", "@community/mcp-server-notion-calendar"],
      "env": {
        "GOOGLE_CREDENTIALS_JSON": "/Users/you/.config/gcal-creds.json"
      }
    }
  }
}

Frequently asked questions

Does Notion Calendar have its own API?

Notion Calendar surfaces events from connected Google/Microsoft accounts. The MCP server typically talks to those underlying APIs rather than a dedicated Notion Calendar API.

Can it create scheduling links?

Scheduling links (like Notion Calendar's pages) are generated via the Notion Calendar web UI. Some MCP variants integrate the link-creation flow where supported.

How is it safer than raw Google Calendar MCP?

Comparable — safety depends on scoping OAuth to calendar.events only. Notion Calendar framing is a UX convenience, not a security boundary.

Sources

Notion Calendar — accessed 2026-04-20
Google Calendar API — accessed 2026-04-20
Model Context Protocol — accessed 2026-04-20