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/.claude/commands/research-calendar-api.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/commands/nspady/google-calendar-mcp/research-calendar-api)<a href="https://agentmods.dev/commands/nspady/google-calendar-mcp/research-calendar-api"><img src="https://agentmods.dev/badge/commands/nspady/google-calendar-mcp/research-calendar-api/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/commands/nspady/google-calendar-mcp/research-calendar-api"><img src="https://agentmods.dev/badge/commands/nspady/google-calendar-mcp/research-calendar-api.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.00017 | $0.00330 |
| Opus 5 | $0.00009 | $0.00165 |
| Sonnet 5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
research-calendar-api 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 10d 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:
- research-calendar-api — 100% identical, 0 lines differ
- research-calendar-api — 100% identical, 0 lines differ
What it actually says
Use the gcal-api-research skill to conduct thorough research on: $ARGUMENTS
Research Focus Areas
Investigate the following aspects:
- Best API Approach - Identify the correct Google Calendar API method(s) to use
- Edge Cases - Uncover potential pitfalls and gotchas specific to this feature
- Community Issues - Find real-world problems others have encountered
- Best Practices - Validate the approach against Google's recommendations
- Implementation Complexity - Assess the effort required and any API limitations
Expected Output
Provide actionable research findings that include:
- ✅ Recommended API method and implementation approach
- ⚠️ Critical edge cases that must be handled
- 📋 Specific code patterns and parameter recommendations
- 🧪 Testing scenarios to validate the implementation
- 📚 References to official documentation and community resources
Research Workflow
Follow the gcal-api-research skill's structured workflow:
- Understand the feature requirements
- Consult reference materials (research-checklist.md, api-patterns.md, edge-cases.md)
- Fetch official Google Calendar API documentation
- Search for community-reported issues (Stack Overflow, GitHub)
- Validate implementation approach
- Provide clear, actionable findings
Focus on recurring events, timezone handling, batch operations, and multi-calendar support where applicable.
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.
- 10d ago First seen · 41 lines · 17 tokens per session scan A 2cf2fe919db0
research-calendar-api is a command published in the GitHub repository nspady/google-calendar-mcp (1,185 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 330 once invoked, about $0.0001 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 commands, from other repositories
init
Initialize configurations for Supabase local development.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
api-contract-review
Review an API contract (endpoints, request/response shapes, error codes, auth model) BEFORE implementation for naming consistency, versioning, pagination, idempotency, and alignment with existing endpoints. Distinct from review-hard (post-implementation risk) and repo-consistency-sweep (pattern matching on written…
build
Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…