add-gmail

Integrate Gmail via MCP for reading and sending emails.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill adds Gmail integration to NanoClaw, enabling access to reading and sending emails via MCP in two modes: a tool mode for WhatsApp-triggered email actions and a channel mode for email-driven automation and replies, all guided by a Google Cloud OAuth workflow.

Core Features & Use Cases

  • Tool Mode: Agent can read and send emails when triggered from WhatsApp.
  • Channel Mode: Emails can trigger the agent, schedule tasks, and receive email replies.
  • OAuth & MCP Setup: Step-by-step guidance to configure Gmail OAuth credentials and the Gmail MCP, enabling secure access without exposing credentials.

Quick Start

Configure Gmail MCP following the prerequisites and test by sending a message in WhatsApp like "@Andy check my recent emails" or "@Andy list Gmail labels".

Frequently Asked Questions about add-gmail

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

FAQPage Schema
How do I integrate Gmail with a WhatsApp agent for email automation?

Gmail integration with a WhatsApp agent is configured using the Gmail MCP and Google Cloud OAuth credentials, enabling both WhatsApp-triggered email actions and email-driven automated replies through Tool Mode and Channel Mode.

What is the difference between Tool Mode and Channel Mode for Gmail automation?

Tool Mode allows an agent to read and send emails when triggered from WhatsApp, while Channel Mode uses incoming emails to trigger the agent, schedule tasks, and send automated email replies.

How do I set up OAuth credentials for Gmail API access in an agent runner?

Setting up OAuth credentials for Gmail API access involves a guided Google Cloud OAuth workflow to configure secure access, mount credentials into the container, and integrate them into the agent runner and group memory.

Do I need container access to mount Gmail OAuth credentials securely?

Yes, container access is required to mount Gmail OAuth credentials securely, ensuring the agent runner can access the Gmail MCP tools without directly exposing sensitive authentication data.

Can I trigger automated email replies from incoming Gmail messages?

Yes, Channel Mode enables incoming Gmail messages to trigger the agent, schedule tasks, and automatically generate email replies through the configured Gmail MCP integration.

What are the limitations of using Gmail MCP for email automation?

Gmail MCP email automation requires completing a Google Cloud OAuth setup and depends on container access for mounting credentials, making it unsuitable for environments without containerized agent runner support.