google-calendar-mcp is an MCP server that lets AI assistants connect to Google Calendar and manage calendar information. It supports tasks such as searching, creating, updating, and deleting events, checking availability, handling recurring events, and detecting conflicts across calendars. The catalogue skills, instructions, commands, and agents provide workflows for operating this integration.
Borrowing it
Nothing to install: this file belongs to nspady/google-calendar-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nspady/google-calendar-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/nspady/google-calendar-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/nspady/google-calendar-mcp/agents-md)<a href="https://agentmods.dev/instructions/nspady/google-calendar-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/nspady/google-calendar-mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/nspady/google-calendar-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/nspady/google-calendar-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.02631 | $0.02631 |
| Opus 5.5 | $0.01052 | $0.01052 |
| Sonnet 5.5 | $0.00526 | $0.00526 |
| Haiku 4.5 | $0.00263 | $0.00263 |
Grade A, and why
google-calendar-mcp AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 20d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
2 near-identical copies found in the catalogue:
- google-calendar-mcp-app AGENTS.md — 100% identical, 283 lines differ
- google-calendar-mcp AGENTS.md — 100% identical, 283 lines differ
How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI coding agents working on this repository. This is the canonical instructions file per the agents.md convention; Claude Code reads it natively (v2.1.277+), and CLAUDE.md is a one-line @AGENTS.md import kept so older Claude Code versions load it too. Guidance for agents using the running MCP server (multi-account behavior, the account parameter) lives in docs/agent-tool-usage.md.
Overview
Google Calendar MCP Server - A Model Context Protocol (MCP) server providing Google Calendar integration for AI assistants. Built with TypeScript, supports both stdio and HTTP transports, with OAuth 2.0 authentication.
Development Commands
npm install # Install dependencies
npm run build # Build with esbuild (outputs to build/)
npm run dev # Show interactive development menu with all commands
npm run lint # TypeScript type checking (no emit)
# Testing - Quick Start
npm test # Unit tests only (no auth required)
npm run test:watch # Unit tests in watch mode
npm run dev test:integration:direct # Direct integration tests (recommended for dev)
npm run dev coverage # Generate test coverage report
# Testing - Full Suite (rarely needed, incurs LLM usage costs)
npm run dev test:integration:claude # Claude + MCP integration (requires CLAUDE_API_KEY)
npm run dev test:integration:openai # OpenAI + MCP integration (requires OPENAI_API_KEY)
npm run dev test:integration:all # All integration tests (requires all API keys)
# Authentication
npm run auth # Authenticate main account
npm run dev auth:test # Authenticate test account (for integration tests)
npm run dev account:status # Check authentication status
# Running the server
npm start # Start with stdio transport
npm run dev http # Start HTTP server on localhost:3000
npm run dev http:public # HTTP server accessible from any host
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 20d ago Changed · +211 lines · +2,275 tokens per session 3affbafffc47
- 2mo ago First seen · 49 lines · 356 tokens per session scan A b576ac34f13c
google-calendar-mcp AGENTS.md is an instructions file published in the GitHub repository nspady/google-calendar-mcp (1,206 stars, last pushed yesterday), licensed MIT. It adds 2,631 tokens to every session, about $0.0105 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.