add-gcal-tool

Wires Google Calendar MCP into NanoClaw agent groups with OneCLI-managed OAuth.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables NanoClaw teams to securely integrate Google Calendar MCP tools into agent groups via OneCLI-managed OAuth, allowing multi-calendar access without exposing raw credentials.

Core Features & Use Cases

  • Multi-account, multi-calendar support: Exposes MCP tools like list-calendars, list-events, create-event, etc., across groups.
  • Secure token handling: Tokens are injected by OneCLI at runtime, never reach the container.
  • Use Case: A single operator wires Google Calendar into two agent groups to manage separate calendars for different teams.

Quick Start

Wire Google Calendar MCP into a target agent group using OneCLI-managed OAuth, then verify that tokens are injected securely.

Frequently Asked Questions about add-gcal-tool

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

FAQPage Schema
How do I wire Google Calendar MCP tools into Docker containers securely?

To wire Google Calendar MCP securely, you register the tools per agent group using OneCLI-managed OAuth. This setup injects tokens at runtime so credentials never reach the Docker container.

Can I manage multiple Google Calendars across different agent groups?

Yes, you can manage multiple Google Calendars across different agent groups. The configuration supports multi-account, multi-calendar access, allowing a single operator to wire separate calendars for distinct teams.

How does OneCLI OAuth token handling work for Google Calendar integrations?

OneCLI OAuth token handling works by injecting tokens at runtime during calendar operations. Tokens are stubbed securely and never reach the container, keeping raw credentials out of the environment.

What is the best way to configure MCP dependencies for Google Calendar in Dockerfile builds?

The best way to configure MCP dependencies is to pin them explicitly in Dockerfile builds. The workflow requires group-scoped configuration and per-group MCP registration for secure calendar operations.

Do I need explicit group-scoped configuration to expose Google Calendar MCP tools?

Yes, you need explicit group-scoped configuration to expose Google Calendar MCP tools. The system enforces a development workflow requiring per-group MCP registration and environment configuration.