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.svg" alt="Measured on agentmods" 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.00356 | $0.00356 |
| Opus 5 | $0.00178 | $0.00178 |
| Sonnet 5 | $0.00071 | $0.00071 |
| Haiku 4.5 | $0.00036 | $0.00036 |
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 8d 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, 0 lines differ
- google-calendar-mcp AGENTS.md — 100% identical, 0 lines differ
What it actually says
Agent Guidelines
This document provides instructions for AI agents interacting with the Google Calendar MCP server.
Multi-Account Handling
This server supports connecting to multiple Google accounts simultaneously (e.g., "work", "personal").
Detecting Accounts
You can list available accounts using the list-calendars tool. The tool will return calendars from all connected accounts.
Using the account Parameter
Most tools accept an optional account parameter.
-
If
accountis OMITTED:- Read operations (like
list-events) will query all accounts and merge results. - Write operations (like
create-event) will try to intelligently select the best account based on permissions.
- Read operations (like
-
If
accountis SPECIFIED:- The operation is restricted to that specific account (or list of accounts).
- Use this when the user explicitly asks to "check my work calendar" or "add this to my personal schedule".
Example: Listing Events
{
"name": "list-events",
"arguments": {
"timeMin": "2023-10-27T00:00:00Z",
"account": ["work"]
}
}
Example: Creating Events
{
"name": "create-event",
"arguments": {
"summary": "Meeting",
"start": "...",
"end": "...",
"account": "work"
}
}
Calendar Deduplication
The server automatically handles shared calendars. If a calendar is shared between "work" and "personal", it will appear as a single unified calendar in list-calendars. You generally don't need to worry about duplicates.
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.
- 8d 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,183 stars, last pushed 4d ago), licensed MIT. It adds 356 tokens to every session, about $0.0018 per session on Opus 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.