GoogleCalendarMCP
Provides tools for interacting with Google Calendar, allowing retrieval of events from public calendars and event lookups by date. For full functionality (including create, update, delete, and private calendar access), OAuth 2.0 authentication is required.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GoogleCalendarMCPlist events for next week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Server Setup
The server.js file contains the implementation of the Google Calendar MCP server.
Note: The MCP configuration may vary depending on the editor or MCP client you are using. The following instructions are for Cursor.
Prerequisites
Before configuring the MCP server, ensure you have:
Node.js installed
Cursor Editor installed and signed in
A Google Calendar API key
Your Google Calendar ID
Setup in Cursor
Open Cursor.
Go to Settings.
Navigate to Tools → MCP.
Add a new MCP server using the following configuration:
{
"mcpServers": {
"filesystem": {
"command": "node",
"args": [
"PATH_TO_SERVER_JS"
],
"env": {
"GOOGLE_PUBLIC_API_KEY": "YOUR_GOOGLE_API_KEY",
"CALENDAR_ID": "YOUR_CALENDAR_ID"
}
}
}
}Configuration
Replace the placeholders below with your own values:
PATH_TO_SERVER_JS – Absolute path to the
server.jsfile.YOUR_GOOGLE_API_KEY – Your Google Calendar API key.
YOUR_CALENDAR_ID – Your Google Calendar ID (typically your Gmail address for your primary calendar).
After saving the configuration, restart Cursor (if required). Your MCP server will then be available for use.
Related MCP server: googlecalendar-mcp
Important Note
This project currently uses a Google Calendar API Key, which can only access public Google Calendars.
If your calendar is private, the server will not be able to retrieve event details such as the title, description, or attendees. To access private calendars or support creating, updating, and deleting events, you must replace the API key authentication with OAuth 2.0.
Current Features (API Key)
Read events from public Google Calendars
Retrieve events by date
Read private calendars
Create calendar events
Update calendar events
Delete calendar events
For full Google Calendar functionality, OAuth 2.0 authentication is recommended.
Resources
For a detailed guide on building custom MCP servers with TypeScript, check out the following article:
Available Tools
1 toolgetMyCalendarDataByDateD
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.0.0- First observed
getMyCalendarDataByDate
TDQS
Only one tool exists, so there is no risk of confusing between tools.
With a single tool, naming consistency is inherently maintained.
A Google Calendar server with only one tool is too few for its apparent scope, failing to cover basic operations.
The tool has no description and likely only fetches data by date, missing essential CRUD operations for a calendar service.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
A MCP server that works with Google Calendar to manage event listing, reading, and updates.
MCP server for Cronofy — read calendars, events and free/busy, and create, update or delete events.
Streamable HTTP MCP server for Google Calendar and Sheets with OAuth login.
Hosted Google Calendar MCP server for AI agents. No self-hosting or Google Cloud setup.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides integration with Google Calendar, allowing users to list calendars and manage events. It enables searching, creating, and modifying calendar entries through tools designed for the Model Context Protocol.-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for managing Google Calendar events.-
- FlicenseNot gradedqualityCmaintenanceMCP server for Google Calendar (single-user) using Service Account authentication. Provides tools to manage events, check free/busy, and find free slots.-
- AlicenseAqualityCmaintenanceA Google Calendar MCP server built with FastMCP, providing tools for event CRUD, calendar management, and availability queries via the Google Calendar API.9MIT
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/umachandra-30/GoogleCalenderMCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server