Skip to main content
Glama
Sign In
deenesjakoruzh
flight

flight

by nihalpatel99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

mcp-flight-map

Demo Recording:- https://drive.google.com/file/d/1qRNfk_p79G89ST9OaEnpr1A2N-u7doKy/view?usp=sharing

An MCP server that exposes flight search and Google Maps directions as tools, powered by SerpApi.

Tools

search_flights (flight.py)

Search for flights via Google Flights.

Argument

Type

Description

departure_id

str

3-letter departure airport code (e.g. AUS)

arrival_id

str

3-letter arrival airport code (e.g. JFK)

outbound_date

str

Departure date, YYYY-MM-DD

return_date

str | None

Return date, YYYY-MM-DD (omit for one-way)

currency

str

Currency code, defaults to USD

get_directions (map.py)

Get directions and route info between two locations via Google Maps.

Argument

Type

Description

start_addr

str

Starting address or place name

end_addr

str

Destination address or place name

travel_mode

str

One of best, driving, two-wheeler, transit, walking, cycling, flight. Defaults to driving

Related MCP server: Flight Search MCP Server

Setup

Requires Python 3.13+ and a SerpApi API key.

uv sync

Add your API key to .env:

SERPAPI_API_KEY="your-key-here"

Running

Each tool is its own MCP server, run over stdio:

uv run flight.py
uv run map.py

Point an MCP-compatible client (e.g. Claude Desktop) at these scripts to use the tools.

Available Tools

1 tool
search_flightsA

Search for flights using Google Flights via SerpApi.

Args: departure_id: 3-letter departure airport code (e.g. AUS) arrival_id: 3-letter arrival airport code (e.g. JFK) outbound_date: departure date in YYYY-MM-DD format return_date: return date in YYYY-MM-DD format (omit for one-way) currency: currency code, defaults to USD

Inputs: arrival_id (required), departure_id (required), outbound_date (required), currency, +1 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool, there is no ambiguity whatsoever. The tool's purpose is clearly distinct by virtue of being the only one.

    Naming Consistency5/5

    The single tool name 'search_flights' follows a clear verb_noun convention, and consistency is trivially satisfied with just one name.

    Tool Count2/5

    Having only one tool for a flight-related server is too few. While the search functionality is useful, a typical flight service would expect additional operations like booking, cancellation, or flight status, making this feel extremely minimal for the apparent domain.

    Completeness2/5

    The tool surface is severely incomplete for the flight domain—it only covers searching. There are no tools for selecting, booking, modifying, or canceling flights, which are obvious core operations, leading to significant gaps that would cause agent failures in real workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers