gcal
Server Details
A MCP server that works with Google Calendar to manage event listing, reading, and updates.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- mintmcp/servers
- GitHub Stars
- 6
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
6 toolscreate_eventInspect
Create a new calendar event. Use this to schedule meetings, appointments, or all-day events. For all-day events, only provide dates (end date is EXCLUSIVE - use '2024-01-16' for a single day event on Jan 15). For timed events, both start and end times are required. Can optionally invite attendees with email notifications. The created event ID can be used for future updates or deletion.
| Name | Required | Description | Default |
|---|---|---|---|
| endDate | Yes | End date YYYY-MM-DD. For all-day: next day. For timed: same or later day | |
| endTime | No | End time HH:MM:SS (e.g., "15:00:00"). Required if startTime provided | |
| summary | Yes | Event title | |
| location | No | Event location (address or meeting room) | |
| timeZone | Yes | Timezone (e.g., "America/Los_Angeles", "UTC", "Europe/London") | |
| attendees | No | Email addresses of attendees to invite | |
| startDate | Yes | Start date YYYY-MM-DD (e.g., "2024-01-15") | |
| startTime | No | Start time HH:MM:SS (e.g., "14:00:00"). Omit for all-day events | |
| calendarId | Yes | Calendar ID from list_calendars (required - get ID first using list_calendars) | |
| description | No | Event description. Supports markdown formatting | |
| sendUpdates | No | all: notify everyone, externalOnly: only external users, none: no notifications | all |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | Yes | |
| end | Yes | |
| start | Yes | |
| status | No | |
| summary | Yes | |
| htmlLink | No | |
| location | No | |
| attendees | No | |
| description | No |
delete_eventDestructiveInspect
Permanently delete an event by eventId (no undo). Sends cancellation notifications to attendees by default (control with sendUpdates). Returns {success: true, eventId, message} on success.
| Name | Required | Description | Default |
|---|---|---|---|
| eventId | Yes | Event ID to delete | |
| calendarId | Yes | Calendar ID from list_calendars | |
| sendUpdates | No | Whether to send cancellation notifications (all: notify all attendees, externalOnly: only non-Google Calendar users, none: no notifications) | all |
Output Schema
| Name | Required | Description |
|---|---|---|
| eventId | Yes | |
| message | Yes | |
| success | Yes |
get_calendar_eventsRead-onlyInspect
Retrieve events from a specific calendar within a time range. Use this to view scheduled events, check availability, or find specific appointments. Times are interpreted in the provided timezone. Without dateMax, returns all future events from dateMin. IMPORTANT: For single day events, use next day as dateMax (e.g., dateMin='2024-01-15' and dateMax='2024-01-16'). Event IDs from this tool are required for update/delete operations.
| Name | Required | Description | Default |
|---|---|---|---|
| dateMax | No | End date YYYY-MM-DD. Events BEFORE this date. For single day, use next day | |
| dateMin | Yes | Start date YYYY-MM-DD (e.g., "2024-01-15"). Required | |
| timeMax | No | End time HH:MM:SS. Only valid with dateMax | |
| timeMin | Yes | Start time HH:MM:SS (e.g., "09:00:00"). Required | |
| timeZone | Yes | Timezone for interpreting dates/times (e.g., "America/Los_Angeles", "UTC") | |
| pageToken | No | Pagination token from previous response | |
| calendarId | Yes | Calendar ID from list_calendars (required - get ID first using list_calendars) | |
| maxResults | No | Number of events to return (1-2500). Default: 10 |
Output Schema
| Name | Required | Description |
|---|---|---|
| events | Yes | |
| message | No | |
| calendarId | Yes | |
| nextPageToken | Yes |
get_next_availabilityRead-onlyInspect
Find next 10 available time slots in a calendar. Searches up to 30 days ahead. Returns {availableSlots: [{start, end}...], searchedUntil} with times in the specified timezone. Use searchedUntil with new startFromDate/Time to paginate. Can restrict to specific hours/days. Slots align to startTimeIncrement boundaries.
| Name | Required | Description | Default |
|---|---|---|---|
| duration | Yes | Duration of the meeting in minutes (e.g., 30, 60, 90) | |
| timezone | Yes | Time zone for all operations (IANA format, e.g., "America/New_York") | |
| calendarId | Yes | Calendar ID from list_calendars | |
| includeDays | No | Days of the week to include in search (default: weekdays only) | |
| startFromDate | Yes | Start searching from this date in YYYY-MM-DD format (e.g., "2024-01-15") | |
| startFromTime | Yes | Start searching from this time in HH:MM:SS format (e.g., "09:00:00") | |
| searchHoursEnd | No | Daily search window end time in HH:MM:SS format (e.g., "17:00:00"). If not provided, searches all hours | |
| searchHoursStart | No | Daily search window start time in HH:MM:SS format (e.g., "09:00:00"). If not provided, searches all hours | |
| startTimeIncrement | No | Increment between possible start times in minutes (e.g., 15 for every 15 minutes, 30 for every half-hour) |
Output Schema
| Name | Required | Description |
|---|---|---|
| searchedUntil | Yes | |
| availableSlots | Yes |
list_calendarsRead-onlyInspect
List all calendars the user has access to. Use this to discover available calendars before performing calendar operations. The primary calendar (primary:true) is the user's main calendar. Other calendars may be shared, subscribed, or secondary calendars. The calendar ID is required for all other calendar operations.
| Name | Required | Description | Default |
|---|---|---|---|
| pageToken | No | Pagination token from previous response to get next page | |
| maxResults | No | Number of calendars to return (1-250). Default: 100 |
Output Schema
| Name | Required | Description |
|---|---|---|
| message | No | |
| calendars | Yes | |
| nextPageToken | Yes |
update_eventInspect
Update an existing event by eventId. Dates/times are interpreted in the provided timezone. Can update individual fields (summary, description, location) OR update times (must provide all: startDate, endDate, and optionally startTime, endTime). WARNING: Empty strings/arrays CLEAR fields. Cannot move between calendars. Returns updated event {id, summary, start, end, updated, ...}.
| Name | Required | Description | Default |
|---|---|---|---|
| endDate | No | End date in YYYY-MM-DD format (e.g., "2024-01-16" for all-day or "2024-01-15" for timed). Required if updating time | |
| endTime | No | End time in HH:MM:SS format (e.g., "15:00:00"). Omit for all-day events | |
| eventId | Yes | Event ID to update | |
| summary | No | Event title/summary | |
| location | No | Event location | |
| timeZone | Yes | Timezone for interpreting dates and times (e.g., "America/Los_Angeles", "UTC", "Europe/London") | |
| attendees | No | Array of attendee email addresses (replaces existing attendees) | |
| startDate | No | Start date in YYYY-MM-DD format (e.g., "2024-01-15"). Required if updating time | |
| startTime | No | Start time in HH:MM:SS format (e.g., "14:00:00"). Omit for all-day events | |
| calendarId | Yes | Calendar ID from list_calendars | |
| description | No | Event description | |
| sendUpdates | No | Whether to send update notifications (all: notify all attendees, externalOnly: only non-Google Calendar users, none: no notifications) | all |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | Yes | |
| end | Yes | |
| start | Yes | |
| status | No | |
| summary | Yes | |
| updated | No | |
| htmlLink | No | |
| location | No | |
| attendees | No | |
| description | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail — every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control — enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management — store and rotate API keys and OAuth tokens in one place
Change alerts — get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption — public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics — see which tools are being used most, helping you prioritize development and documentation
Direct user feedback — users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!