start_visa_application — FareEagle Travel MCP Tool Mutating
start_visa_application
(start visa application) is one of 18 tools on the
FareEagle Travel
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call start_visa_application from your client
- Claude Code FareEagle Travel start_visa_application run in your project directory
- Claude Desktop FareEagle Travel start_visa_application ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FareEagle Travel start_visa_application ~/.cursor/mcp.json
- VS Code FareEagle Travel start_visa_application .vscode/mcp.json
- Zed FareEagle Travel start_visa_application ~/.config/zed/settings.json
- Windsurf FareEagle Travel start_visa_application ~/.codeium/windsurf/mcp_config.json
- Cline FareEagle Travel start_visa_application ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FareEagle Travel start_visa_application ~/.gemini/settings.json
- Grok FareEagle Travel start_visa_application .mcp.json (in your project root)
- ChatGPT FareEagle Travel start_visa_application Settings → Connectors → Advanced → Developer mode
- Claude.ai FareEagle Travel start_visa_application Settings → Connectors → Add custom connector
- LangChain FareEagle Travel start_visa_application pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http travel https://www.fareeagle.com/mcpOther tools on this server
- search_flights
- search_hotels
- search_buses
- get_airport_info
- get_airline_info
- prepare_flight_booking
- create_flight_booking
- get_flight_addons
- select_flight_addons
- prepare_hotel_booking
- create_hotel_booking
- scan_passport
- get_booking_status
- get_eticket_pdf
- cancel_booking
- search_packages
- visa_requirements
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.