google-calendar

google-calendar is an MCP server for Claude Code, Codex, Cursor, Gemini CLI, OpenCode from reggiechan74/cc-plugins. Its token cost is not measured, scanned A, original, MIT.

A connection that lets the coding agent use Google Calendar through an MCP server, a standard way for tools to communicate with an AI assistant.

In plain words
What is it for?
It is intended for tasks involving Google Calendar, but the provided information is too limited to name specific jobs safely.
Why use it?
The description only identifies the calendar connection and does not specify which calendar actions are available.

MCP server for Claude CodeCodexCursorGemini CLIOpenCode

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the google-workspace-mcp plugin — 1 skill, 2 MCP servers shipped together

One of 2 entries in .mcp.json — they are configured in one file and arrive together.

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add reggiechan74/cc-plugins
Claude Code
/plugin install google-workspace-mcp

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

Or install google-workspace-mcp, the plugin that ships this one along with the rest of its 1 skill, 2 MCP servers.

Wrote 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.

agentmods badge for google-calendar

README.md
[![agentmods](https://agentmods.dev/badge/mcp/reggiechan74/cc-plugins/google-calendar.svg)](https://agentmods.dev/mcp/reggiechan74/cc-plugins/google-calendar)
Your own site
<a href="https://agentmods.dev/mcp/reggiechan74/cc-plugins/google-calendar"><img src="https://agentmods.dev/badge/mcp/reggiechan74/cc-plugins/google-calendar.svg" alt="Measured on agentmods" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

google-calendar 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 3d 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.

google-workspace-mcp/.mcp.json · 8 lines

What it actually says

{
  "google-calendar": {
    "command": "node",
    "args": [
      "${CLAUDE_PLUGIN_ROOT}/servers/calendar/index.js"
    ]
  }
}
Same file

What else .mcp.json configures

This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.

Changes

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.

  1. 3d ago First seen · 8 lines scan A 2b606b75e23a

Subscribe to this mod's changes

google-calendar is an MCP server published in the GitHub repository reggiechan74/cc-plugins (6 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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-31.