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