Gmail Mcp

What is Gmail Mcp?

Gmail Mcp reads, searches, sends, drafts, labels, filters, and threads Gmail from any MCP-enabled AI assistant. It wraps the Gmail API with scope-gated tools and in-process safeguards.

How to use Gmail Mcp?

Install globally via npm install -g @klodr/gmail-mcp or invoke directly with npx -y @klodr/gmail-mcp. Authenticate using the auth subcommand with a chosen OAuth scope. Add the server to your MCP client configuration as shown in the README. Requires Node.js 22+.

Key features of Gmail Mcp

• Scope-gated tools filtered by granted OAuth scopes.
• Path jails restrict attachment and download directories.
• Hardened OAuth with file mode 0o600 and TOCTOU defense.
• Per-bucket daily and monthly rate limits for sensitive actions.
• Opt-in append-only JSONL audit log of tool calls.
• Sigstore-signed releases with SLSA attestation and SBOM.

Use cases of Gmail Mcp

• Read and search Gmail messages without send permissions.
• Send emails using a read-only agent after re-authentication.
• Manage labels and filters programmatically.
• Draft messages and thread replies via AI assistants.
• Log all Gmail tool usage for compliance or debugging.

FAQ from Gmail Mcp

What OAuth scopes are supported?

gmail.readonly, gmail.send, and gmail.modify are supported; tool lists are filtered at startup based on the granted scope.

What are the runtime requirements?

Node.js 22 or higher is required.

Does Gmail Mcp impose rate limits?

Yes, per-bucket daily and monthly caps apply to send, delete, modify, drafts, labels, and filters.

How are attachments secured?

Path jails restrict where the agent can read and write, blocking exfiltration of sensitive files like ~/.ssh/id_rsa.

Is an audit log available?

Yes, an opt-in append-only JSONL log records every tool call (redacted) for auditing purposes.