add-gcal-tool Skill
Add Google Calendar as an MCP tool (list calendars, list/search/create events, free/busy queries) using OneCLI-managed OAuth. Multi-calendar and multi-account supported. Mirrors /add-gmail-tool's stub pattern — no raw credentials ever reach the container; OneCLI injects real tokens at request time. Published by microsoft in amplifier-app-nanoclaw.
What is add-gcal-tool Skill?
Add Google Calendar as an MCP tool (list calendars, list/search/create events, free/busy queries) using OneCLI-managed OAuth. Multi-calendar and multi-account supported. Mirrors /add-gmail-tool's stub pattern — no raw credentials ever reach the container; OneCLI injects real tokens at request time. Published by microsoft in amplifier-app-nanoclaw. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Research
- Research use cases
Technical details
- Install or run with Copy skill directory
When to use add-gcal-tool Skill
- Use it for research.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-app-nanoclaw
- Skill file: .claude/skills/add-gcal-tool/SKILL.md
What it does
Add Google Calendar as an MCP tool (list calendars, list/search/create events, free/busy queries) using OneCLI-managed OAuth. Multi-calendar and multi-account supported. Mirrors /add-gmail-tool's stub pattern — no raw credentials ever reach the container; OneCLI injects real tokens at request time.
Skill instructions
Add Google Calendar Tool (OneCLI-native) This skill wires @cocal/google-calendar-mcp into selected agent groups. The MCP server reads stub credentials containing the onecli-managed placeholder; the OneCLI gateway intercepts outbound calls to calendar.googleapis.com / oauth2.googleapis.com and swaps the bearer for the real OAuth token from its vault. Why this package (and not gongrzhe's): @gongrzhe/server-calendar-autoauth-mcp only supports the primary calendar and exposes 5 tools (no listcalendars). @cocal/google-calendar-mcp explicitly supports multi-calendar and multi-account, and is actively maintained. Tools exposed (surfaced as mcpcalendar<name, exact set depends on version — run tools/list against the MCP server to enumerate): list-calendars, list-events, search-events, create-event, update-event, delete-event, get-event, list-colors, get-freebusy, get-current-time, plus multi-account management tools. Why this pattern: v2's invariant is that containers never receive raw API keys
Explore related resources
Frequently asked questions
What is add-gcal-tool?
add-gcal-tool is a open-source AI agent skill with Copy skill directory. Add Google Calendar as an MCP tool (list calendars, list/search/create events, free/busy queries) using OneCLI-managed OAuth. Multi-calendar and multi-account supported.
Who is add-gcal-tool best for?
add-gcal-tool is best for reusing agent instructions, scripts, and references, research workflows.
How do I install add-gcal-tool?
Install or run add-gcal-tool using Copy skill directory. Check add-gcal-tool for the latest setup command.
Is add-gcal-tool actively maintained?
add-gcal-tool may need a closer maintenance check before production use.
Auto-fetched from GitHub.
