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/skills/mcp-research/SKILL.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/skills/nspady/google-calendar-mcp/mcp-research)<a href="https://agentmods.dev/skills/nspady/google-calendar-mcp/mcp-research"><img src="https://agentmods.dev/badge/skills/nspady/google-calendar-mcp/mcp-research/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/skills/nspady/google-calendar-mcp/mcp-research"><img src="https://agentmods.dev/badge/skills/nspady/google-calendar-mcp/mcp-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.00923 |
| Opus 5.5 | $0.00000 | $0.00369 |
| Sonnet 5.5 | $0.00000 | $0.00185 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
mcp-research 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 2mo 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:
- mcp-research — 100% identical, 0 lines differ
- mcp-research — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Implementation Research
Quick Start
What are you doing?
- 📝 Reviewing MCP server →
references/implementation-checklist.md - 🚀 Planning MCP feature →
references/protocol-patterns.md - 🐛 Protocol issue →
references/common-pitfalls.md - ✅ Architecture validation → All references + latest spec
Research Workflow
- Understand implementation - What MCP capabilities? Which transport? What security requirements?
- Consult references - Load relevant reference files progressively
- Check latest spec - WebFetch
https://modelcontextprotocol.io/specification/2025-06-18 - Search community - WebSearch for "MCP [specific-issue] 2025"
- Validate compliance - Protocol compliance, security, best practices
- Report findings - Structured format (see examples/)
Critical MCP Requirements
Protocol Compliance (JSON-RPC 2.0)
- All messages MUST include
jsonrpc: "2.0" - Responses include
resultORerror, never both - Initialization:
initialize→ response →initializednotification - Use standard error codes (-32xxx)
Security & Consent
- User consent MUST be obtained before data access
- Tool execution requires explicit approval
- No hardcoded credentials
- Input/output sanitization required
Capability Advertisement
- Declare all capabilities in
initializeresponse - Types:
tools,resources,prompts,logging,experimental - Protocol version:
"2025-06-18"(latest)
Transport Layers
stdio:
- Newline-delimited JSON-RPC messages
- Use stderr for logging (not stdout)
- Flush after each message
HTTP/SSE:
- POST
/mcpfor JSON-RPC requests - GET
/mcp/ssefor server-sent events - CORS configured for browser clients
Key Reference Files
implementation-checklist.md - Protocol compliance, capabilities, security, production readiness
protocol-patterns.md - Tool/resource/prompt patterns, best practices, code examples
common-pitfalls.md - Known issues, edge cases, gotchas
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 117 lines · 0 tokens per session scan A d96ff92ef735
mcp-research is a skill published in the GitHub repository nspady/google-calendar-mcp (1,206 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 923 tokens. 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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…