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