Calendar MCP Server
Enables AI assistants to manage Google Calendar events, including reading, searching, creating, updating, and deleting events, as well as checking availability and listing calendars.
README
@franciscpd/calendar-mcp-server
A Model Context Protocol (MCP) server for Google Calendar. Read, search, create, update, and delete calendar events, check availability, and list calendars — powered by 3 environment variables.
Quick Start
npx -y @franciscpd/calendar-mcp-server
Set these environment variables:
| Variable | Description |
|---|---|
GOOGLE_CALENDAR_CLIENT_ID |
OAuth2 client ID from Google Cloud Console |
GOOGLE_CALENDAR_CLIENT_SECRET |
OAuth2 client secret |
GOOGLE_CALENDAR_REFRESH_TOKEN |
OAuth2 refresh token (see Setup Guide) |
Setup Guide
1. Create a Google Cloud Project
- Go to Google Cloud Console
- Create a new project (or select an existing one)
- Note your project name for the next steps
2. Enable the Google Calendar API
- Navigate to APIs & Services → Library
- Search for "Google Calendar API"
- Click Enable
3. Create OAuth2 Credentials
- Navigate to APIs & Services → Credentials
- Click Create Credentials → OAuth client ID
- If prompted, configure the OAuth consent screen:
- User type: External (or Internal for Workspace)
- Add the scopes:
https://www.googleapis.com/auth/calendar.readonlyhttps://www.googleapis.com/auth/calendar.events
- Add your email as a test user
- Application type: Web application
- Add
https://developers.google.com/oauthplaygroundas an authorized redirect URI - Save your Client ID and Client Secret
4. Get a Refresh Token
- Go to Google OAuth2 Playground
- Click the gear icon (top right) and check Use your own OAuth credentials
- Enter your Client ID and Client Secret
- In the left panel, find Google Calendar API v3 and select:
https://www.googleapis.com/auth/calendar.readonlyhttps://www.googleapis.com/auth/calendar.events
- Click Authorize APIs and grant access
- Click Exchange authorization code for tokens
- Copy the Refresh token
Important: OAuth Consent Screen
If your OAuth consent screen is in Testing mode, refresh tokens expire after 7 days. To avoid this:
- Option A: Publish your app (set status to "In production" in the OAuth consent screen settings). No Google review is needed for apps used only by you.
- Option B: Add specific Google accounts as test users in the OAuth consent screen settings. Tokens for test users still expire after 7 days, but you can re-authorize.
For personal use, Option A is recommended — publish the app so tokens don't expire.
See Google's OAuth consent screen documentation for details.
Configuration
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"google-calendar": {
"command": "npx",
"args": ["-y", "@franciscpd/calendar-mcp-server"],
"env": {
"GOOGLE_CALENDAR_CLIENT_ID": "your-client-id",
"GOOGLE_CALENDAR_CLIENT_SECRET": "your-client-secret",
"GOOGLE_CALENDAR_REFRESH_TOKEN": "your-refresh-token"
}
}
}
}
Cursor
Add to your Cursor MCP settings:
{
"mcpServers": {
"google-calendar": {
"command": "npx",
"args": ["-y", "@franciscpd/calendar-mcp-server"],
"env": {
"GOOGLE_CALENDAR_CLIENT_ID": "your-client-id",
"GOOGLE_CALENDAR_CLIENT_SECRET": "your-client-secret",
"GOOGLE_CALENDAR_REFRESH_TOKEN": "your-refresh-token"
}
}
}
}
Generic MCP Client
GOOGLE_CALENDAR_CLIENT_ID=your-client-id \
GOOGLE_CALENDAR_CLIENT_SECRET=your-client-secret \
GOOGLE_CALENDAR_REFRESH_TOKEN=your-refresh-token \
npx -y @franciscpd/calendar-mcp-server
The server communicates over stdio using the MCP protocol.
Tools
| Tool | Description |
|---|---|
calendar_list_calendars |
List all calendars with id, name, timezone, color, and access role |
calendar_list_events |
List events from a calendar within a date range (default: next 7 days) |
calendar_get_event |
Get full event details including attendees, recurrence, and reminders |
calendar_search_events |
Search events by text across summaries, descriptions, and locations |
calendar_get_freebusy |
Check free/busy availability for one or more calendars |
calendar_create_event |
Create a new calendar event (timed or all-day) |
calendar_update_event |
Update an existing event (partial update — only specified fields change) |
calendar_delete_event |
Delete a calendar event |
Development
# Install dependencies
npm install
# Build
npm run build
# Run tests
npm test
# Run tests with coverage
npm run test:coverage
# Start the server
npm start
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.