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