find_times — TeamMeet MCP Tool Read-only

find_times (find times) is one of 25 tools on the TeamMeet MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call find_times from your client

Claude Code TeamMeet find_times run in your project directory
Claude Desktop TeamMeet find_times ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor TeamMeet find_times ~/.cursor/mcp.json
VS Code TeamMeet find_times .vscode/mcp.json
Zed TeamMeet find_times ~/.config/zed/settings.json
Windsurf TeamMeet find_times ~/.codeium/windsurf/mcp_config.json
Cline TeamMeet find_times ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI TeamMeet find_times ~/.gemini/settings.json
Grok TeamMeet find_times .mcp.json (in your project root)
ChatGPT TeamMeet find_times Settings → Connectors → Advanced → Developer mode
Claude.ai TeamMeet find_times Settings → Connectors → Add custom connector
LangChain TeamMeet find_times pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http teammeet https://teammeet.ai/mcp

Other tools on this server

start_meeting
invite
list_meetings
get_transcript
get_notes
get_action_items
send_message
speak
draw
list_recordings
send_feedback
submit_fix
import_transcript
send_notetaker
my_tasks
get_task
update_task
join_meeting
listen
hand_off
set_up_booking_page
booking_page_status
book_time
get_my_context

This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.

TeamMeet MCP server