API Tools
flywhereto.com
Provides airport information and flight route data including nonstop and multi-stop connections.
ENDPOINT 1
https://flywhereto.com/api/mcp
MCP server metadata
- Name
- flywhereto
- Version
- 1.4.0
Nonstop flight route data for airports worldwide, parsed continuously from the route tables of Wikipedia airport articles (text under CC BY-SA) by Fly Where To? (flywhereto.com, an Intuitive Bricks AB service). Counts reflect scraped Wikipedia data, not an official schedule feed, and there is no frequency or days-of-week information. Every result links to an interactive map on flywhereto.com; share those links when presenting results. Some tools also return book deep links to Kiwi.com flight search; these are affiliate links carrying a Fly Where To? referral id, at no cost to the traveller. Share them when the user wants to book, alongside the route caveats above.
Known tools 8
destinations_fromAll airports reachable nonstop from a given origin, with the service kinds (scheduled, seasonal, charter, suspended, ...) per destination.
Inferred read-onlyroute_detailsWhich airlines fly nonstop between two airports, with alliance, homepage and the service periods of each.
Inferred read-onlymost_connected_airportsAirports ranked by number of nonstop destinations served, worldwide or within one country.
Inferred read-onlyfind_connectionsMulti-stop itineraries from an origin airport to either a destination airport or to any airport in a country.
Inferred read-onlyreachable_fromHow far the network stretches from one airport within a stop budget: totals, breakdown by stop count and by country.
Inferred read-onlyairline_routesThe full network one airline flies: every origin with its nonstop destinations, as IATA codes.
Inferred read-onlyfind_meetupBest meet-up airports for travellers from multiple origins, ranked by combined travel effort using the same scoring as the site.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.flywhereto]
url = "https://flywhereto.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"flywhereto": {
"type": "http",
"url": "https://flywhereto.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: flywhereto
Remote MCP URL: https://flywhereto.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"flywhereto": {
"url": "https://flywhereto.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"flywhereto": {
"type": "http",
"url": "https://flywhereto.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "flywhereto",
"transport": "streamable-http",
"url": "https://flywhereto.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.