Google Calendar MCP Server
# gcal-mcp
[](https://pypi.org/project/gcal-mcp/)
[](https://github.com/alDuncanson/gcal-mcp/actions/workflows/ci.yml)
[](https://github.com/alDuncanson/gcal-mcp/actions/workflows/release.yml)
A [Model Context Protocol](https://modelcontextprotocol.io/) (MCP) server for
Google Calendar that uses OAuth 2.0 with PKCE for secure authentication.
### Bring your own Oauth client
To use your own OAuth client credentials:
```bash
gcal-mcp --credentials /path/to/credentials.json
```
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: retrieving events for a specific date, listing upcoming events, and searching by keyword. Some overlap exists (e.g., upcoming events could be retrieved by date), but the descriptions differentiate them well.
All tool names follow a consistent verb_noun pattern with snake_case: get_events_for_date, get_upcoming_events, search_events. The pattern is predictable and easy to understand.
With only 3 tools, the server feels under-scoped for a calendar service. Most calendar servers provide create, update, delete, and calendar management operations, which are missing here.
The server only covers read/query operations (get, list, search). It lacks any write operations (create, update, delete events) or calendar management, leaving significant gaps for common workflows.