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