add-gmail-tool

Wires the Gmail MCP server into NanoClaw agent groups using OneCLI-managed OAuth credentials.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill add-gmail-tool-rosedwayane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-gmail-tool
Source: https://github.com/roseDwayane/LocalizeAgenticSys/tree/main/nanoclaw/.claude/skills/add-gmail-tool
Command: npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill add-gmail-tool-rosedwayane

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @gongrzhe/server-gmail-autoauth-mcp, zod-to-json-schema.

What problem does it solve? NanoClaw agents run in isolated containers that must never hold raw API keys, so giving an agent Gmail access requires a credential-safe wiring path. This Skill installs the Gmail MCP server into the agent container image and registers it per agent group, with OneCLI injecting real OAuth tokens at request time so no usable credentials ever exist on disk or in the container. ## Core Features & Use Cases - Credential-safe Gmail access: Uses stub credential files with onecli-managed placeholders; the OneCLI gateway swaps in the real OAuth bearer token in flight. - Full Gmail toolset: Exposes search, read, send, draft, delete, label, filter, and attachment tools to the agent as mcp__gmail__* functions. - Per-group wiring with guard tests: Registers the MCP server and .gmail-mcp mount per agent group in the central DB, with structural tests guarding the Dockerfile install and allow-pattern derivation. - Use Case: Ask your personal agent to "search my inbox for invoices from last month" or "draft a reply to this email" and it uses the Gmail tools without ever touching a raw token. ## Quick Start Ask the agent to add the Gmail tool to your personal agent group using OneCLI-managed OAuth, then verify by having the agent list your Gmail labels.

Frequently Asked Questions about add-gmail-tool

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

FAQPage Schema
How do I add Gmail tools to a NanoClaw agent?

Install the @gongrzhe/server-gmail-autoauth-mcp package in the container Dockerfile, then register the gmail MCP server and a .gmail-mcp mount per agent group in the central DB. OneCLI injects the real OAuth token at request time, so the container only sees placeholder credentials.

How does OneCLI keep Gmail OAuth tokens out of the container?

The container mounts stub credential files containing the onecli-managed placeholder. The OneCLI gateway intercepts outbound calls to gmail.googleapis.com and rewrites the Authorization header with the real bearer token from its vault, so usable credentials never exist on disk or in the container.

What Gmail tools does the MCP server expose to the agent?

The server exposes search_emails, read_email, send_email, draft_email, delete_email, batch operations, attachment download, label management, and filter management. They surface to the agent as mcp__gmail__* tools once the gmail server is registered in the group's mcpServers map.

Why does the agent say it has no Gmail tools after setup?

The gmail MCP server is not registered in that group's mcpServers map, or the agent-runner image is stale. Re-run the ncl groups config add-mcp-server step for that group, rebuild the image with ./container/build.sh, and restart the service.

Why do I get 401 Unauthorized errors from the Gmail API?

A 401 means OneCLI is not injecting the token. Check that the Gmail app shows connected status via onecli apps get --provider gmail, and verify the agent's secret mode includes the Gmail secrets with onecli agents secrets --id <agent-id>.

Can this skill receive inbound email as an agent channel?

No, this skill is tool-only: the agent can call Gmail APIs but inbound emails do not trigger it. Inbound email requires a separate channel adapter that polls the inbox and routes messages to a group, which has not been ported to the v2 architecture.