add-gmail

Automate Gmail integration setup with OAuth credentials and MCP servers.

1|2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/jboothomas/nauggieclaw --skill add-gmail-jboothomas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-gmail
Source: https://github.com/jboothomas/nauggieclaw/tree/main/.claude/skills/add-gmail
Command: npx skills add https://github.com/jboothomas/nauggieclaw --skill add-gmail-jboothomas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

NauggieClaw lacks built-in Gmail automation and monitoring, so this skill provision ensures the agent can securely read, respond, and act on emails via tools or channel mode while guiding OAuth and container configuration.

Core Features & Use Cases

  • Dual modes: installs Gmail tools for manual triggers or a full channel that polls unread messages and reacts as WhatsApp prompts arrive.
  • Secure setup: merges Gmail channel code, mounts ~/.gmail-mcp, adds MCP servers, and adjusts container and agent runner configs with npm builds and tests.
  • Guided operations: leads the user through OAuth credential creation, authorization flows, verification steps, filtering options, and removal procedures for both modes.

Quick Start

Ask Auggie to enable the Gmail skill and follow the OAuth prompts to link your account.

Frequently Asked Questions about add-gmail

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Gmail integration setup with OAuth for an AI agent?

The Gmail integration operates in dual modes: installing Gmail tools for manual triggers or configuring a full channel that polls unread messages and reacts when WhatsApp prompts arrive.

Can I use WhatsApp messages to trigger Gmail actions through an automated channel?

Yes, you can configure a full email channel where the agent polls unread Gmail messages and reacts automatically as WhatsApp prompts arrive, enabling cross-platform notification workflows.

What's the best way to securely mount OAuth credentials for a Gmail MCP server in a container?

The most secure method mounts the ~/.gmail-mcp directory into your container, adds the MCP servers, and adjusts agent runner configurations to handle OAuth credentials without exposing sensitive data.

Does configuring Gmail automation require manual npm builds and test validations?

Yes, the secure setup process merges Gmail channel code, adjusts container configurations, and runs npm builds and test validations to satisfy security and notification requirements before activation.

Why do I need to adjust container and agent runner configs for Gmail tooling?

Adjusting container and agent runner configs is required to properly mount OAuth credentials, merge Gmail channel code, and ensure the MCP server operates securely within the isolated environment.