add-gcal-tool

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? NanoClaw agents run in isolated containers that never receive raw API credentials, so wiring Google Calendar access requires a careful multi-phase setup: stub credentials, Dockerfile changes, DB-level MCP registration, and container rebuilds. This Skill automates that entire workflow so agents can list calendars, search and create events, and query free/busy availability without any real tokens reaching the container. ## Core Features & Use Cases - OneCLI-managed OAuth: Stub credentials with the onecli-managed placeholder are mounted into containers; the OneCLI gateway swaps in real Google OAuth tokens at request time. - Multi-calendar and multi-account support: Uses @cocal/google-calendar-mcp, which exposes list-calendars, list/search/create/update/delete events, free/busy queries, and multi-account management tools. - Per-group wiring with guard tests: Registers the calendar 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: After running this Skill, a user can message their agent "what's on my work calendar next Monday?" and the agent answers via the mcp__calendar__* tools, with credentials never leaving the OneCLI vault. ## Quick Start Ask the agent to add the Google Calendar tool to a chosen NanoClaw agent group, then restart the service and message the agent "list my calendars" to verify.

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 tools to a NanoClaw agent?

Run the add-gcal-tool skill: it writes OneCLI stub credentials, installs @cocal/google-calendar-mcp in the container Dockerfile, registers the calendar MCP server per agent group via ncl groups config add-mcp-server, and rebuilds the image. Verify by messaging the agent "list my calendars".

Which Google Calendar MCP server supports multiple calendars and accounts?

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

Does the calendar MCP server expose raw Google credentials to the container?

No. The container only receives stub credential files containing the onecli-managed placeholder. The OneCLI gateway intercepts outbound calls to calendar.googleapis.com and injects 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 ncl groups config add-mcp-server for the group, rebuild with ./container/build.sh, and restart the service.

How do I remove the Google Calendar tool from NanoClaw?

Follow REMOVE.md: unregister the MCP server per group, drop the .calendar-mcp mount from the DB via scripts/q.ts, delete the copied guard test, revert the Dockerfile edits, rebuild, and restart. Optionally remove ~/.calendar-mcp and disconnect OneCLI.