Google Flights MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Google Flights MCP Server?

Google Flights MCP Server is a tool that allows users to interact with Google Flights data using the fast_flights library, enabling the fetching of flight information.

how to use Google Flights MCP Server?

To use the server, clone the repository, set up a virtual environment, install dependencies, and run the server using Python. Integrate it with MCP clients by configuring the client settings with the server's path.

key features of Google Flights MCP Server?

  • Fetch one-way flights for specific dates between two airports.
  • Retrieve round-trip flights for specified departure and return dates.
  • Find all available flights within a date range, with options for minimum and maximum stay.

use cases of Google Flights MCP Server?

  1. Finding the cheapest flights for a specific date.
  2. Planning round trips with flexible dates.
  3. Analyzing flight availability over a range of dates for better travel planning.

FAQ from Google Flights MCP Server?

  • Can I use this server for any flight route?

Yes! You can fetch flights between any two airports.

  • Is there a limit to the number of requests I can make?

The server's performance may vary based on Google Flights' response times and network conditions.

  • What if I encounter errors while fetching data?

The server includes basic error handling to manage common issues.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago