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