Google CalendarSAFE
A Model Context Protocol (MCP) server implementation for Google Calendar integration. Create and manage calendar events directly through Claude or other AI assistants.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
A Model Context Protocol (MCP) server implementation that enables AI assistants like Claude to create and manage Google Calendar events.
Features
- Create calendar events with title, description, start/end times
- Support for adding event attendees
- OAuth2 authentication with Google Calendar API
- Full MCP protocol implementation
- Debug logging for troubleshooting
Prerequisites
- Node.js v18 or later
- Google Cloud Console project with Calendar API enabled
- OAuth2 credentials (Client ID and Client Secret)
Setup
- Clone the repository:
git clone [https://github.com/markelaugust74/mcp-google-calendar.git] cd mcp-google-calendar
- Install dependencies:
npm install
- Set up environment variables:
- Copy .env.example to .env
- Add your Google OAuth2 credentials
- Get your refresh token:
npm run auth
- Update the refresh token in index.js
Usage
npm start
4194c37dec92OBSERVED · 2026-10-08Exposed tools (1)
0 read · 1 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
create_event | write | Create a calendar event with specified details |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4194c37dec92full audit observations/trust-audit/mcp-server/markelaugust74__google-calendar-7.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 4194c37dec92 | SAFE | B | 89 | first audit |
Questions
What is the Google Calendar MCP server?
A Model Context Protocol (MCP) server implementation for Google Calendar integration. Create and manage calendar events directly through Claude or other AI assistants.
What tools does Google Calendar expose?
1 in total: 0 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Google Calendar safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Google Calendar need?
It reads GOOGLE_CLIENT_SECRET from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Google Calendar run?
It speaks stdio, so it runs as a local process your client starts.
How current is this page?
The grade is for one exact copy of the source (4194c37dec92), read on 2026-10-08. The repository is watched and re-audited when it changes.