MCP Flight Search

Created By
KVSSettya year ago
MCP Server for flight search using serpAPI service
Overview

MCP Flight Search is a flight search service built using the Model Context Protocol (MCP). It demonstrates how to implement MCP tools for flight search capabilities.

To use MCP Flight Search, integrate the service with your application by utilizing the MCP tools defined in the project. You can access the service through the provided API endpoints.

  • Utilizes the Model Context Protocol for structured flight search.
  • Integrates with serpAPI for real-time flight data.
  • Supports various flight search queries and parameters.
  1. Searching for flights based on user-defined criteria.
  2. Integrating flight search capabilities into travel applications.
  3. Providing real-time flight information to users.
  • What is the Model Context Protocol (MCP)?

The Model Context Protocol (MCP) is a standard developed by Anthropic that allows AI models to use tools by defining a structured format for tool descriptions, calls, and responses.

  • How can I access the flight search service?

You can access the service through the API provided in the project documentation on GitHub.

  • Is there a cost associated with using MCP Flight Search?

The project does not specify any costs, but usage of the underlying serpAPI may have associated fees.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
KVSSetty
Star
0
Language
Python
License
-
Tags

Recommend Servers

View All
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