What is mcp-gmail-calendar AGENTS.md?

Repository instructions for a Gmail and Google Calendar project whose canonical rules are kept in CLAUDE.md. They cover credentials, testing, command-line design, MCP adapters, dry runs, and OAuth permissions.

Implementing or reviewing Gmail, Calendar, Drive, Docs, Sheets, Tasks, and Contacts changes while following the project’s validation requirements.

They help coding agents avoid exposing account credentials, calling Google during tests, or changing the project in ways that break its safety rules.

How ftaricano/mcp-gmail-calendar configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to ftaricano/mcp-gmail-calendar. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ftaricano/mcp-gmail-calendar/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/ftaricano/mcp-gmail-calendar

Made for: Codex, OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/ftaricano/mcp-gmail-calendar/agents-md/github.svg)](https://agentmods.dev/instructions/ftaricano/mcp-gmail-calendar/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/ftaricano/mcp-gmail-calendar/agents-md"><img src="https://agentmods.dev/badge/instructions/ftaricano/mcp-gmail-calendar/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/ftaricano/mcp-gmail-calendar/agents-md"><img src="https://agentmods.dev/badge/instructions/ftaricano/mcp-gmail-calendar/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,124 This file is loaded in full into every session.

When invoked 1,124 The same file — it is already loaded in full.

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.

Token cost

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.01124	$0.01124
Opus 5.5	$0.00450	$0.00450
Sonnet 5.5	$0.00225	$0.00225
Haiku 4.5	$0.00112	$0.00112

Measured 1mo ago against content hash eb2cb2f6047c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mcp-gmail-calendar AGENTS.md 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 1mo 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.

AGENTS.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md -- mcp-gmail-calendar

CLI-first Google Workspace tool (gws) com servidor MCP de compatibilidade (gws-mcp) para Gmail, Calendar, Drive, Docs, Sheets, Tasks e Contacts. Usado por Ferd e pelos agentes do hub como surface primaria de acesso ao Google Workspace.

O que e

gws expoe operacoes completas de Gmail, Calendar, Drive, Docs, Sheets, Tasks e Contacts via CLI e via MCP (protocolo Model Context Protocol). O CLI e o produto principal; o servidor MCP e um adapter de compatibilidade para clientes de IA (Claude, etc.). Publicado como @mcp/gmail-calendar v1.1.0, binarios gws e gws-mcp. Multi-conta via ~/.config/gws/state.json.

Stack & estrutura

Node.js 20+ + TypeScript 5.7 strict + Commander (CLI) + googleapis + @modelcontextprotocol/sdk + zod + winston + handlebars; build: tsc; testes: tsx --test (Node test runner nativo).

mcp-gmail-calendar/
  bin/
    gws.js          # entrypoint CLI
    gws-mcp.js      # entrypoint MCP server
  src/
    index.ts        # MCP server (gws-mcp)
    auth/           # OAuth2 flow e multi-account manager
    cli/            # comandos CLI (Commander)
    services/       # Gmail, Calendar, Drive, Docs, Sheets, Tasks, People
    tools/          # MCP tool definitions
    utils/          # formatters, parsers, cache, logger
  tests/            # ~30 arquivos .test.ts (Node test runner)
  templates/        # templates Handlebars para email
  docs/             # documentacao adicional
  .env.example      # variaveis de ambiente necessarias
  tokens/           # tokens OAuth (gitignored)

Como rodar / validar

# Setup inicial (uma vez)
cp .env.example .env
# Editar .env: GOOGLE_CREDENTIALS_PATH obrigatorio

# Build
npm run build

# Dev CLI sem build
npm run cli -- --help
npm run cli -- mail list --query "is:unread" --limit 5

# Rodar MCP server (stdio)
gws-mcp
# ou: node dist/index.js

# Testes (nao requerem credenciais reais -- usam fakes injetados)
npm test

# Lint
npm run lint

Validar tudo: npm test && npm run lint

Read the full file on GitHub · 80 lines

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.

1mo ago Changed · +67 lines · +914 tokens per session eb2cb2f6047c
2mo ago First seen · 13 lines · 210 tokens per session scan A c7584ad99d1f

Subscribe to this mod's changes

mcp-gmail-calendar AGENTS.md is an instructions file published in the GitHub repository ftaricano/mcp-gmail-calendar (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,124 tokens to every session, about $0.0045 per session on Opus 5.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-31.

automation gmail google-calendar google-workspace mcp model-context-protocol

mcp-gmail-calendar AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
mcp-gmail-calendar AGENTS.mdftaricano/mcp-gmail-calendar	Instructions file	0	1mo ago	MIT	A	1,124	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

mcp-gmail-calendar: Instructions file for Codex