find_best_meeting_time — Time of Meeting MCP Tool Read-only
find_best_meeting_time
(find best meeting time) is one of 6 tools on the
Time of Meeting
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call find_best_meeting_time from your client
- Claude Code Time of Meeting find_best_meeting_time run in your project directory
- Claude Desktop Time of Meeting find_best_meeting_time ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Time of Meeting find_best_meeting_time ~/.cursor/mcp.json
- VS Code Time of Meeting find_best_meeting_time .vscode/mcp.json
- Zed Time of Meeting find_best_meeting_time ~/.config/zed/settings.json
- Windsurf Time of Meeting find_best_meeting_time ~/.codeium/windsurf/mcp_config.json
- Cline Time of Meeting find_best_meeting_time ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Time of Meeting find_best_meeting_time ~/.gemini/settings.json
- Grok Time of Meeting find_best_meeting_time .mcp.json (in your project root)
- ChatGPT Time of Meeting find_best_meeting_time Settings → Connectors → Advanced → Developer mode
- Claude.ai Time of Meeting find_best_meeting_time Settings → Connectors → Add custom connector
- LangChain Time of Meeting find_best_meeting_time pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http time-of-meeting https://timeofmeeting.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 17 October 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.