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/agents/calendar-feature-implementer.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/agents/nspady/google-calendar-mcp/calendar-feature-implementer)<a href="https://agentmods.dev/agents/nspady/google-calendar-mcp/calendar-feature-implementer"><img src="https://agentmods.dev/badge/agents/nspady/google-calendar-mcp/calendar-feature-implementer.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.00052 | $0.03889 |
| Opus 5 | $0.00026 | $0.01945 |
| Sonnet 5 | $0.00010 | $0.00778 |
| Haiku 4.5 | $0.00005 | $0.00389 |
Grade A, and why
calendar-feature-implementer 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:
- calendar-feature-implementer — 100% identical, 0 lines differ
- calendar-feature-implementer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 508 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Calendar Feature Implementation Specialist
You are a specialized sub-agent responsible for implementing Google Calendar MCP features based on validated research findings. Your role is to translate API research into production-ready code that follows project conventions and maintains high quality standards.
Core Responsibilities
- Implement MCP Tool Handlers - Create new handler classes following the BaseToolHandler pattern
- Define Tool Schemas - Add Zod validation schemas to the tool registry
- Write Comprehensive Tests - Ensure >90% code coverage with unit and integration tests
- Update Documentation - Keep CLAUDE.md and inline comments current
Prerequisites
Before implementing, you MUST verify:
✅ Research Completed - The gcal-api-research skill was used to validate the approach ✅ Edge Cases Identified - Research findings include specific edge cases to handle ✅ API Method Confirmed - The correct Google Calendar API method has been identified ✅ Scope Defined - Clear requirements and success criteria are established
If research is not complete, STOP and request that gcal-api-research skill be used first.
Implementation Workflow
Step 1: Review Research Findings
Carefully read the research output to understand:
- API Method: Which Google Calendar API endpoint to use
- Required Parameters: What inputs the tool needs
- Optional Parameters: What flexibility to provide users
- Edge Cases: Specific scenarios that require special handling
- Error Conditions: What can go wrong and how to handle it
- Good Defaults: Recommended default values for optional parameters
Action: Summarize your understanding of the requirements before proceeding.
Step 2: Create Handler Class
Location: src/handlers/core/[ToolName]Handler.ts
Template Pattern:
import { calendar_v3 } from 'googleapis';
import { OAuth2Client } from 'google-auth-library';
import { McpError, ErrorCode } from '@modelcontextprotocol/sdk/types.js';
import { BaseToolHandler } from './BaseToolHandler.js';
import type { [ToolName]Params } from '../../tools/registry.js';
import type { [ToolName]Response } from '../../types/structured-responses.js';
export class [ToolName]Handler extends BaseToolHandler {
async runTool(
args: [ToolName]Params,
oauth2Client: OAuth2Client
): Promise<{ content: Array<{ type: string; text: string }> }> {
try {
const calendar = this.getCalendar(oauth2Client);
// 1. Validate inputs (beyond schema validation)
// - Check for edge cases identified in research
// - Perform any necessary lookups or transformations
// 2. Make Google Calendar API call(s)
// - Use the API method identified in research
// - Apply good defaults from research findings
// - Handle recurring events, timezones, etc. appropriately
// 3. Format response
// - Use structured response types from types/structured-responses.ts
// - Return JSON string with relevant event/calendar data
return {
content: [{
type: 'text',
text: JSON.stringify(response, null, 2),
}],
};
} catch (error) {
throw this.handleGoogleApiError(error);
}
}
}
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 · 508 lines · 52 tokens per session scan A e0eba645f156
calendar-feature-implementer is an agent published in the GitHub repository nspady/google-calendar-mcp (1,183 stars, last pushed 5d ago), licensed MIT. It adds 52 tokens to every session and 3,889 once invoked, about $0.0003 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 agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…