CalendarMCP
Give Claude Code, Cursor, or other MCP clients read/write Google Calendar access without hosting OAuth, Docker, or credentials.json yourself.
Overview
CalendarMCP is a MCP server for the Build phase that provides hosted Google Calendar read/write access for AI agents over HTTP with minimal OAuth setup.
What is this MCP server?
- One-click Google OAuth plus API key—no Google Cloud Console project or credentials.json
- Streamable HTTP MCP endpoint works with Claude.ai, Claude Code, Cursor, Windsurf, Continue, Cline, n8n, and similar clie
- Batch calendar operations via batch_update-style tools for multi-event edits in one agent turn
- Public docs, manifest, and client examples in-repo; production service is hosted at calendarmcp.ai
- Clear OSS alternative called out (nspady/google-calendar-mcp) when tokens must stay on your machine
- Connect flow advertised as about two minutes after OAuth
- HTTP/streamable transport for hosted MCP clients
- Documents batch_update batch calendar operations
What problem does it solve?
Self-hosted Google Calendar MCP setups demand Google Cloud Console work, credential files, and often stdio-only clients, which blocks fast calendar automation in Claude Code and Cursor.
Who is it for?
Indie builders who want reliable Google Calendar tools in Claude Code, Cursor, or Claude.ai without maintaining MCP infrastructure.
Skip if: Builders or orgs that must keep Google OAuth tokens entirely on-device and self-managed.
What do I get? / Deliverables
After OAuth and an API key, your agent can query and mutate calendar events—including batch updates—from any streamable HTTP MCP client in roughly two minutes.
- Agent tools to read and write Google Calendar events
- Batch calendar updates from agent sessions
- Repeatable MCP client configuration from public manifest examples
Recommended MCP Servers
Journey fit
Calendar wiring is an integration task you add while building agent-assisted workflows and shipping automation around your product and personal ops. The server is a hosted MCP bridge to Google Calendar APIs, which fits the integrations shelf rather than frontend or backend app code.
How it compares
Hosted HTTP calendar MCP integration, not a local-only stdio skill or generic scheduling prompt.
Common Questions / FAQ
Who is ai.calendarmcp/server for?
Solo builders and small teams using MCP agents who need Google Calendar access without Docker, credentials.json, or self-hosted OAuth plumbing.
When should I use ai.calendarmcp/server?
Use it during Build when you are wiring agent workflows that create, list, or batch-update calendar events from Claude Code, Cursor, or other HTTP MCP clients.
How do I add ai.calendarmcp/server to my agent?
Complete Google OAuth on calendarmcp.ai, copy your API key, and register the remote MCP URL from the manifest in your client’s MCP settings per calendarmcp.ai/docs.