Flights MCP Server

Created By
maratsarbasova year ago
MCP server searching flights with granular filtering, sorting options, and purchase integration.
Overview

what is Flights MCP Server?

Flights MCP Server is a platform designed to search for flights with advanced filtering and sorting options, along with purchase integration for a seamless booking experience.

how to use Flights MCP Server?

To use the Flights MCP Server, access the API through the provided GitHub repository, where you can implement the search functionality in your application.

key features of Flights MCP Server?

  • Granular filtering options for flights based on various criteria.
  • Sorting options to arrange flights by price, duration, and other factors.
  • Integration with purchase systems for direct booking.

use cases of Flights MCP Server?

  1. Building a travel booking application that allows users to find and book flights.
  2. Creating a travel comparison tool that helps users find the best flight deals.
  3. Integrating flight search capabilities into existing travel platforms.

FAQ from Flights MCP Server?

  • What kind of filtering options are available?

Users can filter flights by price, duration, layovers, and airlines.

  • Is there a limit to the number of searches?

The API does not impose a strict limit, but usage may be subject to fair use policies.

  • Can I integrate this server with my existing application?

Yes! The server is designed to be easily integrated into various applications.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
maratsarbasov
Star
0
Language
Python
License
GPL-3.0 license
Tags

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

13 hours ago