Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldMapbox MCPShortlist candidateFli - Flight Search MCP Server and LibraryMCP100 Recommended
Task fit
Best for
  • Geocoding, distance, directions, map and location workflows
  • Use for geospatial planning or spatial reasoning.
  • Searching flight options conversationally during early travel planning
Not ideal for
  • Some tools use paid Mapbox APIs and forward coordinates or queries to Mapbox.
  • Booking, guaranteed live inventory, or final price confirmation
Avoid when
  • Some tools use paid Mapbox APIs and forward coordinates or queries to Mapbox.
  • The workflow would make purchase decisions without verifying itinerary, baggage rules, fare terms, and current price at the provider
Provenance
Provenance details

First-party MCP

Mapbox · Publisher source ↗

Community implementation

github:punitarani · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Sep 20, 2026

Package: Not documented

Popularity evidence
GitHub stars

362

GitHub stars · checked 2026-10-20

3,186

GitHub stars · checked 2026-09-24T04:14:16.266000Z

Package downloads / 30 days

8,331

package downloads / 30 days · checked 2026-10-20

No reliable download data
Client coverage
Client coverage detailsNot documented
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationA Mapbox access token is required. The repository documents creating a token in the Mapbox account and also offers a hosted MCP endpoint.No MCP or Google API key or OAuth requirement is documented. The guide notes that some vendor fares may require a browser-minted session token.
CostUnderlying Mapbox APIs are usage-priced with free tiers for many products; directions, static images, map loads, search and other API calls can become billable after free allowances.No project or API price is documented. Provider, booking-vendor, client, and model charges remain separate or unknown.
PermissionsCapabilities depend on the Mapbox token and tool. Some operations require additional token scopes, such as feedback write/read scopes.Searches Google Flights by route, dates, passengers, filters, and locale, and returns itineraries, fares, and airline, OTA, or direct booking links. No purchase action is documented.
Data handlingFor the local/self-hosted execution documented in the repository, Mapbox states that the MCP server does not store, log, or collect user data or API requests and that API calls go directly from the user's environment to Mapbox APIs. The reviewed README does not separately document retention behavior for the hosted endpoint.Search parameters are sent to the publisher-described reverse-engineered Google Flights API. Results include itinerary, price, and booking-link data; storage, telemetry, and retention are not documented.
Limitations
Tradeoffs
  • Use documented @mapbox/mcp-server and access token; tool list runtime-dependent
  • Conversational search is convenient, but flight inventory changes quickly and upstream data coverage may not include every carrier or fare condition.
Risk contextMost tools are read/calculation oriented, but networked tools send coordinates/queries to Mapbox and may create billable API usage. Token scope and location-data sensitivity are the main access risks.The publisher describes a reverse-engineered API and vendor-fare limitations, so independently verify prices and availability before purchase. Keep configurable HTTP mode local because MCP authentication is not documented.
Evidence date
Editorial review2026-10-192026-08-11
Candidate evidence2026-10-192026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →