find_then_book — Appointment Booking MCP Prompt
find_then_book
is one of 4 prompts on the
Appointment Booking
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke find_then_book from your client
- Claude Code Appointment Booking Prompt/find_then_book run in your project directory
- Claude Desktop Appointment Booking Prompt/find_then_book ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Appointment Booking Prompt/find_then_book ~/.cursor/mcp.json
- VS Code Appointment Booking Prompt/find_then_book .vscode/mcp.json
- Zed Appointment Booking Prompt/find_then_book ~/.config/zed/settings.json
- Windsurf Appointment Booking Prompt/find_then_book ~/.codeium/windsurf/mcp_config.json
- Cline Appointment Booking Prompt/find_then_book ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Appointment Booking Prompt/find_then_book ~/.gemini/settings.json
- Grok Appointment Booking Prompt/find_then_book .mcp.json (in your project root)
- ChatGPT Appointment Booking Prompt/find_then_book Settings → Connectors → Advanced → Developer mode
- Claude.ai Appointment Booking Prompt/find_then_book Settings → Connectors → Add custom connector
- LangChain Appointment Booking Prompt/find_then_book pip install langchain-mcp-adapters
Other prompts on this server
Appointment Booking also offers 5 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.