license_status — timezone world clock meeting slots overlap ics MCP Tool
license_status
(license status) is one of 11 tools on the
timezone world clock meeting slots overlap ics
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call license_status from your client
- Claude Code timezone world clock meeting slots overlap ics license_status run in your project directory
- Claude Desktop timezone world clock meeting slots overlap ics license_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor timezone world clock meeting slots overlap ics license_status ~/.cursor/mcp.json
- VS Code timezone world clock meeting slots overlap ics license_status .vscode/mcp.json
- Zed timezone world clock meeting slots overlap ics license_status ~/.config/zed/settings.json
- Windsurf timezone world clock meeting slots overlap ics license_status ~/.codeium/windsurf/mcp_config.json
- Cline timezone world clock meeting slots overlap ics license_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI timezone world clock meeting slots overlap ics license_status ~/.gemini/settings.json
- Grok timezone world clock meeting slots overlap ics license_status .mcp.json (in your project root)
- ChatGPT timezone world clock meeting slots overlap ics license_status Settings → Connectors → Advanced → Developer mode
- Claude.ai timezone world clock meeting slots overlap ics license_status Settings → Connectors → Add custom connector
- LangChain timezone world clock meeting slots overlap ics license_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http timezone-world-clock-meeting-slots-overlap-ics https://mcp.zovo.one/mcp/timezoneOther 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.