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