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 fieldFli - Flight Search MCP Server and LibraryMCP100 RecommendedGoogle Search Console MCP Server for SEOsMCP100 Recommended
Task fit
Best for
  • Searching flight options conversationally during early travel planning
  • SEO analysis across Search Console properties, queries, pages, indexing status, and sitemaps
Not ideal for
  • Booking, guaranteed live inventory, or final price confirmation
  • General web analytics or SEO work that does not use Google Search Console data
Avoid when
  • The workflow would make purchase decisions without verifying itinerary, baggage rules, fare terms, and current price at the provider
  • You cannot grant the configured OAuth user or service account access to the relevant Search Console property
Provenance
Provenance details

Community implementation

github:punitarani · Publisher source ↗

Community implementation

github:aminforou · Publisher source ↗

Maintenance
Maintenance details

Repo: Sep 20, 2026

Package: Not documented

Repo: Sep 15, 2026

Package: Not documented

Popularity evidence
GitHub stars

3,186

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

1,712

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

Client coverage
Client coverage details
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
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
AuthenticationNo MCP or Google API key or OAuth requirement is documented. The guide notes that some vendor fares may require a browser-minted session token.Uses Google OAuth client-secrets JSON and browser login, or a Google service-account JSON whose email has access to the Search Console property.
CostNo project or API price is documented. Provider, booking-vendor, client, and model charges remain separate or unknown.The MIT-licensed server lists no MCP fee. Google Cloud or Search Console quota and billing implications are not documented.
PermissionsSearches 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.Lists Google Search Console properties and reads analytics, URL inspection, and sitemap data. Site and sitemap add/delete tools are disabled unless GSC_ALLOW_DESTRUCTIVE=true.
Data handlingSearch 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.Search Console properties, queries, pages, crawl and indexing results, and sitemap data are returned to the connected client. OAuth tokens are saved for reuse; service-account JSON is read from a configured path. Further retention is not documented.
Limitations
Tradeoffs
  • Conversational search is convenient, but flight inventory changes quickly and upstream data coverage may not include every carrier or fare condition.
  • It reduces manual reporting work, but the assistant can see sensitive search-performance data and optional destructive site or sitemap operations require an explicit flag.
Risk contextThe 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.Can expose private Search Console data and, when explicitly enabled, modify sites or sitemaps. Protect credential files, leave destructive tools disabled unless required, and restrict remote SSE deployments.
Evidence date
Editorial review2026-08-112026-08-11
Candidate evidence2026-09-24T04:25:05.554391Z2026-09-24T04:25:05.554391Z

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

Read the evidence method →