license_activate — calendar ics reader events freebusy conflicts MCP Tool
license_activate
(license activate) is one of 12 tools on the
calendar ics reader events freebusy conflicts
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call license_activate from your client
- Claude Code calendar ics reader events freebusy conflicts license_activate run in your project directory
- Claude Desktop calendar ics reader events freebusy conflicts license_activate ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor calendar ics reader events freebusy conflicts license_activate ~/.cursor/mcp.json
- VS Code calendar ics reader events freebusy conflicts license_activate .vscode/mcp.json
- Zed calendar ics reader events freebusy conflicts license_activate ~/.config/zed/settings.json
- Windsurf calendar ics reader events freebusy conflicts license_activate ~/.codeium/windsurf/mcp_config.json
- Cline calendar ics reader events freebusy conflicts license_activate ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI calendar ics reader events freebusy conflicts license_activate ~/.gemini/settings.json
- Grok calendar ics reader events freebusy conflicts license_activate .mcp.json (in your project root)
- ChatGPT calendar ics reader events freebusy conflicts license_activate Settings → Connectors → Advanced → Developer mode
- Claude.ai calendar ics reader events freebusy conflicts license_activate Settings → Connectors → Add custom connector
- LangChain calendar ics reader events freebusy conflicts license_activate pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http calendar-ics-reader-events-freebusy-conflicts https://mcp.zovo.one/mcp/calendarOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.