Enables creating and managing Google Calendar events with support for titles, descriptions, start/end times, alerts, and attendees through OAuth2 authentication.
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., "@Google Calendar MCP Server schedule a team meeting tomorrow at 2pm for 1 hour about the Q2 roadmap"
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.
A Model Context Protocol (MCP) server implementation that enables AI assistants like Claude to create and manage Google Calendar events.
Create calendar events with title, description, start/end times, and alert
Support for adding event attendees
OAuth2 authentication with Google Calendar API
Full MCP protocol implementation
Debug logging for troubleshooting
Related MCP server: Google Calendar MCP Server
Node.js v18 or later
Google Cloud Console project with Calendar API enabled
OAuth2 credentials (Client ID and Client Secret)
Paste Claude "claude_desktop_config.json"
{
"mcpServers": {
"zmes-calendar": {
"command": "npx",
"args": [
"-y",
"@tobedoit/google-calendar-mcp"
],
"env": {
"GOOGLE_CLIENT_ID": "your_google_client_id",
"GOOGLE_CLIENT_SECRET": "your_google_client_secret",
"GOOGLE_REFRESH_TOKEN": "your_google_refresh_token"
}
}
}
}Create a calendar event with specified details
| Name | Required | Description | Default |
|---|---|---|---|
| summary | Yes | Event title | |
| start_time | Yes | Start time (ISO format) | |
| end_time | Yes | End time (ISO format) | |
| description | No | Event description | |
| location | No | Event location | |
| attendees | No | List of attendee emails | |
| reminders | No | Reminder settings for the event |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'create' implies a write/mutation operation, the description doesn't disclose important behavioral aspects like required permissions, whether the event is immediately published, what happens with duplicate events, error conditions, or what the response contains. For a mutation tool with zero annotation coverage, this represents a significant gap in behavioral transparency.
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?
The description is a single, efficient sentence that gets straight to the point without any wasted words. It's appropriately sized for the tool's complexity and front-loads the essential information. Every word earns its place in this concise formulation.
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?
For a mutation tool with 7 parameters (including complex nested objects) and no annotations or output schema, the description is inadequate. It doesn't explain what happens after creation, error handling, authentication requirements, or the scope of the operation (personal vs shared calendar). The 100% schema coverage helps with parameters, but the overall context for using this tool remains incomplete.
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?
The description mentions 'specified details' which implies parameters exist, but doesn't elaborate on what those details are. With 100% schema description coverage, the schema already documents all 7 parameters thoroughly. The description adds no meaningful parameter semantics beyond what's already in the schema, so it meets the baseline of 3 when schema coverage is complete.
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?
The description clearly states the verb ('create') and resource ('calendar event'), making the purpose immediately understandable. However, it lacks differentiation from sibling tools, but since there are no sibling tools on this server, this limitation is less critical. The phrase 'with specified details' adds some specificity about what can be configured.
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?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or constraints. It simply states what the tool does without any context about appropriate usage scenarios, timing considerations, or limitations. With no sibling tools, the need for differentiation is reduced, but still lacks basic usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.2.1create_eventWith only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is singular and clear.
The single tool follows a clear verb_noun pattern (create_event), and with no other tools to compare, consistency is inherently perfect.
One tool is too few for a Google Calendar server, as it lacks essential operations like listing, updating, or deleting events, making it severely limited for typical calendar management tasks.
The tool set is severely incomplete; it only allows event creation without any way to view, modify, or manage existing events, leaving major gaps in calendar functionality.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.
GDPR-compliant calendar access for AI assistants. Google, Microsoft 365, Apple & more. EU-hosted.
Hosted Google Calendar MCP server for AI agents. No self-hosting or Google Cloud setup.
Schedule and manage Google Calendar events directly from your workspace. Check availability, view…
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tobedoit/gCalendar-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
