add-gcal-tool

Integrates Google Calendar as an MCP tool into NanoClaw agent groups via OneCLI-managed OAuth.

2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/RADHA0-max/selfhealbackend --skill add-gcal-tool-radha0-max
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-gcal-tool
Source: https://github.com/RADHA0-max/selfhealbackend/tree/main/nanoclaw/.claude/skills/add-gcal-tool
Command: npx skills add https://github.com/RADHA0-max/selfhealbackend --skill add-gcal-tool-radha0-max

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @cocal/google-calendar-mcp.

What problem does it solve? NanoClaw agent containers cannot access Google Calendar without exposing raw OAuth credentials, and wiring a calendar MCP server requires coordinated Dockerfile edits, database updates, and container rebuilds that are easy to get wrong. ## Core Features & Use Cases - OneCLI-managed OAuth: Uses stub credentials with a onecli-managed placeholder so containers never receive raw tokens; the OneCLI gateway injects real tokens at request time. - Multi-calendar and multi-account support: Installs @cocal/google-calendar-mcp, exposing tools like list-calendars, list-events, search-events, create-event, and get-freebusy. - Per-group wiring with guard test: Registers the MCP server and .calendar-mcp mount per agent group in the central DB, plus a vitest dependency-guard test that keeps the Dockerfile install pinned. - Use Case: An operator wants an agent to answer "what's on my work calendar next Monday?" — this skill installs the calendar MCP server, wires it into the group's config, rebuilds the image, and verifies the tool works. ## Quick Start Ask the agent to add the Google Calendar tool to a specific NanoClaw agent group using OneCLI-managed OAuth and then verify by asking it to list your calendars.

Frequently Asked Questions about add-gcal-tool

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

FAQPage Schema
How do I add Google Calendar as an MCP tool to an agent?

Install @cocal/google-calendar-mcp in the container Dockerfile with a pinned CALENDAR_MCP_VERSION ARG, then register it per agent group with `ncl groups config add-mcp-server --name calendar` and add the `.calendar-mcp` mount in the central DB. Rebuild the image and restart the service so agents respawn with the new config.

Which Google Calendar MCP server supports multiple calendars and accounts?

@cocal/google-calendar-mcp supports multi-calendar and multi-account usage with tools like list-calendars, search-events, and get-freebusy. The gongrzhe server-calendar-autoauth-mcp only supports the primary calendar and exposes five event-level tools without list_calendars.

Can agents access Google Calendar without raw OAuth credentials in the container?

Yes, by using stub credential files containing the `onecli-managed` placeholder at ~/.calendar-mcp. The OneCLI gateway intercepts outbound calls to calendar.googleapis.com and oauth2.googleapis.com and swaps in the real OAuth token from its vault at request time.

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

The `calendar` 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 with ./container/build.sh, and restart the service.

Why do hand edits to a group's container.json get overwritten?

After migration 014-container-configs, materializeContainerJson regenerates groups/<folder>/container.json from the central DB on every spawn. Persist changes by updating data/v2.db via the ncl CLI or the scripts/q.ts wrapper instead.