Google Calendar▌

by am2rican5
Integrate with Google Calendar API for seamless time management. Manage calendars and events efficiently without repeate
Integrates with Google Calendar API for managing calendars and events with persistent OAuth token storage, enabling seamless scheduling, retrieval, and modification operations without repeated authentication.
best for
- / Personal scheduling and time management
- / Automating meeting creation and updates
- / Calendar-aware AI assistants
- / Workflow automation with calendar integration
capabilities
- / View upcoming events and schedules
- / Create new calendar events with details
- / Update existing event times and information
- / Delete calendar events
- / Check availability for specific time slots
- / Search events by date range or keywords
what it does
Connects to your Google Calendar account to read, create, modify, and delete calendar events directly from your AI assistant.
about
Google Calendar is a community-built MCP server published by am2rican5 that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate with Google Calendar API for seamless time management. Manage calendars and events efficiently without repeate It is categorized under productivity.
how to install
You can install Google Calendar in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Google Calendar is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
Google Calendar MCP Server
A Model Context Protocol (MCP) server that integrates with Google Calendar, built with TypeScript.
Features
- Seamless Google Calendar integration with OAuth 2.0 authentication
- Persistent token storage for automatic authentication
- List and manage calendars with comprehensive event operations
- Create, read, update, and delete calendar events
- Fetch calendar events between specified dates
- Server-Sent Events (SSE) transport option for real-time updates
- Simple integration with Claude and other MCP-compatible AI assistants
Installation
npm install -g mcp-google-calendar
Or run directly with:
npx -y mcp-google-calendar
Prerequisites
- Node.js (v16 or higher)
- Google Cloud Platform account
- Google Calendar API enabled
- OAuth 2.0 credentials
Setup
1. Google Cloud Configuration
- Go to Google Cloud Console
- Create a new project or select an existing one
- Enable the Google Calendar API:
- Navigate to "APIs & Services" > "Library"
- Search for "Google Calendar API"
- Click "Enable"
- Configure OAuth consent screen:
- Go to "APIs & Services" > "OAuth consent screen"
- Choose "External" user type (or "Internal" for Google Workspace)
- Fill in required information:
- App name: mcp-calendar
- User support email: (your email)
- Developer contact information: (your email)
- Add scopes:
- Click "Add or Remove Scopes"
- Find and select "https://www.googleapis.com/auth/calendar.events"
- Add your email as a test user
- Complete the setup
- Create OAuth credentials:
- Go to "Credentials"
- Click "Create Credentials" > "OAuth Client ID"
- Choose "Desktop app" as application type
- Name it (e.g., "MCP Calendar Desktop Client")
- Download the JSON file and save as
credentials.jsonin your project directory
2. Environment Configuration
Create a .env file in your project root:
# Server configuration
PORT=3420
# Google Calendar API configuration
CREDENTIALS_PATH=./credentials.json
Usage
Starting the Server
Start with standard WebSockets:
npx -y mcp-google-calendar
Start with Server-Sent Events (SSE):
npx -y mcp-google-calendar --sse
With Claude Desktop
Add this to your claude_desktop_config.json:
{
"mcpServers": {
"mcp-google-calendar": {
"command": "npx",
"args": ["-y", "mcp-google-calendar"],
"env": {
"CREDENTIALS_PATH": "/path/to/your/credentials.json"
}
}
}
}
Authentication Process
The first time you run the server:
- A browser window will open automatically
- Sign in with your Google account
- Grant the requested calendar permissions
- The authentication token is saved to
token.json
On subsequent launches:
- The server uses the saved token automatically
- No browser interaction is required unless the token expires
Available Tools
| Tool | Description |
|---|---|
list_calendars | Get all available calendars |
list_calendar_events | Retrieve events between specified dates |
create_calendar_event | Add a new event to your calendar |
get_calendar_event | Fetch details for a specific event |
edit_calendar_event | Modify an existing calendar event |
delete_calendar_event | Remove an event from your calendar |
Development
Clone and set up the project:
git clone https://github.com/am2rican5/mcp-google-calendar.git
cd mcp-google-calendar
npm install
Build the project:
npm run build
Run in development mode:
npm start
Security Considerations
⚠️ Important Security Warning ⚠️
credentials.jsonandtoken.jsoncontain sensitive authentication information- Never commit these files to version control or share them publicly
- Each user should create their own OAuth credentials
- If you suspect credential compromise, revoke them immediately in Google Cloud Console
- The token grants access to your Google Calendar data
License
This project is licensed under the MIT License - see the LICENSE file for details.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add some amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
FAQ
- What is the Google Calendar MCP server?
- Google Calendar is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Google Calendar?
- This profile displays 10 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
Ratings
4.5★★★★★10 reviews- ★★★★★Shikha Mishra· Oct 10, 2024
Google Calendar is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Piyush G· Sep 9, 2024
We evaluated Google Calendar against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Chaitanya Patil· Aug 8, 2024
Useful MCP listing: Google Calendar is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Sakshi Patil· Jul 7, 2024
Google Calendar reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Ganesh Mohane· Jun 6, 2024
I recommend Google Calendar for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Oshnikdeep· May 5, 2024
Strong directory entry: Google Calendar surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Dhruvi Jain· Apr 4, 2024
Google Calendar has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Rahul Santra· Mar 3, 2024
According to our notes, Google Calendar benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Pratham Ware· Feb 2, 2024
We wired Google Calendar into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Yash Thakker· Jan 1, 2024
Google Calendar is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.