The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Navifare MCP listing page.
Version: 0.1.5
Navifare finds a better price for a specific flight the user already found. Users should provide flight details conversationally, which will be structured into the required format.
This MCP server wraps the Navifare REST API as MCP tools for flight price comparison. It enables AI assistants like Claude to help users find better prices for flights they've already discovered.
https://mcp.navifare.com/mcphttps://www.navifare.com/mcp (Auto-updates from the MCP endpoint)format_flight_pricecheck_requestTitle: Format Flight Request
Parse and format flight details from natural language text or transcribed image content. Extracts flight information (airlines, flight numbers, dates, airports, prices) and structures it for price comparison. Returns formatted flight data ready for flight_pricecheck, or requests missing information if incomplete.
Annotations:
readOnlyHint: true - Tool only formats/parses data, no external callsdestructiveHint: false - Tool does not modify or delete dataInput Schema:
user_request (required): Flight details in natural language text. Include all available information: flight numbers, airlines, departure/arrival airports and times, dates, prices, passenger counts, and travel class.Example Request:
flight_pricecheckTitle: Flight Price Check
Search multiple booking sources to find better prices for a specific flight the user has already found. Compares prices across different booking platforms to find cheaper alternatives for the exact same flight details.
Annotations:
readOnlyHint: false - Tool performs searches and may trigger external API callsdestructiveHint: false - Tool does not modify or delete dataInput Schema:
trip (required): Flight trip details including segments, passengers, and travel class
legs (required): Array of flight legs (one for outbound, one for return in round trips)travelClass (required): ECONOMY, PREMIUM_ECONOMY, BUSINESS, or FIRSTadults (required): Number of adult passengers (minimum: 1)children (required): Number of child passengers (minimum: 0)infantsInSeat (required): Number of infants requiring a seat (minimum: 0)infantsOnLap (required): Number of infants on lap (minimum: 0)source (required): Source identifier for the query (e.g., "Claude", "MCP", "ChatGPT")price (required): Reference price found by the user (e.g., "84.00", "200.50")currency (required): Three-letter ISO currency code (e.g., "EUR", "USD", "GBP")location (required): Two-letter ISO country code for user location (e.g., "ES", "IT", "US"). If unsure, default to "ZZ"Example Request:
Revenue share available for qualified partners!
Earn commission on flight bookings made through your integration. Revenue share available for qualified partners.
This server complies with Anthropic's MCP Directory Policy. See docs/COMPLIANCE.md for details.
Privacy Policy and Terms of Service: https://navifare.com/terms
Contact: contact@navifare.com
Privacy Inquiries: privacy@navifare.com
The only environment variable you typically need to document for this MCP server is:
GEMINI_API_KEY (required): Google Gemini API key for natural language parsing (used when your integration relies on Gemini for text/image understanding).See docs/USAGE_EXAMPLES.md for complete usage examples with detailed workflows.
Most documentation is in the docs/ directory (and a few files like this README.md and REPOSITORY_STRUCTURE.md live at the repo root):
Test files are located in the test/ directory. See test/README.md for details about available tests.
Helper scripts are in the scripts/ directory:
scripts/start-local.sh - Start local development serverscripts/deploy-to-render.sh - Prepare for Render deploymentscripts/start-servers.sh - Start multiple serversscripts/stop-servers.sh - Stop running serversSee REPOSITORY_STRUCTURE.md for detailed structure.