google-calendar

google-calendar is an MCP server for Claude Code from WARROOM-CEO/CORE. Its token cost is not measured, scanned A, original, MIT.

A hosted connection that lets a coding agent work with Google Calendar, a service for scheduling events and appointments.

In plain words
What is it for?
Using Google Calendar through the configured remote MCP server.
Why use it?
It gives the agent a configured route to the calendar service instead of requiring a separate manual connection.

MCP server for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: listed in a Claude config.

Part of the customer-support plugin — 5 skills, 9 MCP servers shipped together

One of 9 entries in .mcp.json upstream. Installing this one merges just its entry into your config; the other 8 are separate, each on its own page.

Good fit Using Google Calendar through the configured remote MCP server.

Compare 6 mcp servers from other repositories ↓
Install with agentmods
npx agentmods add mcp/warroom-ceo/core/customer-support-google-calendar
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/WARROOM-CEO/CORE

Made for: Claude Code.

Or install customer-support, the plugin that ships this one along with the rest of its 5 skills, 9 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/warroom-ceo/core/customer-support-google-calendar.svg)](https://agentmods.dev/mcp/warroom-ceo/core/customer-support-google-calendar)
Your own site
<a href="https://agentmods.dev/mcp/warroom-ceo/core/customer-support-google-calendar"><img src="https://agentmods.dev/badge/mcp/warroom-ceo/core/customer-support-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. A grade says what 26 rules found in the file — not that it is safe.
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 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.

Origin

Copies of this mod

4 near-identical copies found in the catalogue:

plugins/customer-support/.mcp.json · 6 lines

What it actually says

{
  "google-calendar": {
    "type": "http",
    "url": "https://gcal.mcp.claude.com/mcp"
  }
}
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. 8d ago First seen · 6 lines scan A 2b7518d34819

Subscribe to this mod's changes

google-calendar is an MCP server published in the GitHub repository WARROOM-CEO/CORE (30 stars, last pushed 5mo 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-30.