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