Avolal Flight Search And Booking

Created By
Miguel Domínguez5 months ago
Search and book flights using natural language queries.
Overview

What is Avolal Flight Search And Booking?

Avolal is a flight search and booking service that allows users to find and book flights using natural language queries.

How to use Avolal?

To use Avolal, integrate the MCP server by adding the URL https://www.avolal.com/api/mcp to your AI assistant's configuration. You can then ask your assistant to search for flights in plain language.

Key features of Avolal?

  • Natural language flight search
  • Real-time flight data from various airlines
  • Filters for price, airline, stops, and times
  • Support for round-trip and one-way flights
  • Multi-passenger booking options
  • Direct booking links with pre-filled checkout
  • Smart ranking of flights

Use cases of Avolal?

  1. Quickly booking business travel without comparing multiple sites.
  2. Finding flights for specific meeting times.
  3. Searching for family trips with multiple passengers.
  4. Filtering flights by preferences like direct flights or specific airlines.
  5. Planning leisure travel with comparative options.

FAQ from Avolal?

  • What airlines does Avolal support?

Avolal supports major airlines worldwide through real-time data.

  • Do I need an API key?

No, Avolal does not require an API key for flight searches.

  • Can Avolal book flights directly?

Yes, Avolal provides direct booking links for quick checkout.

  • Does it support international flights?

Yes, Avolal supports both domestic and international flights.

  • Is Avolal free to use?

Yes, searching for flights is free, but booking fees may apply.

  • How current is the flight data?

Flight data is updated in real-time for accurate pricing and availability.

Server Config

{
  "mcpServers": {
    "avolal": {
      "url": "https://www.avolal.com/api/mcp"
    }
  }
}
Project Info
Created At
5 months ago
Updated At
5 months ago
Author Name
Miguel Domínguez
Star
-
Language
-
License
-

Recommend Servers

View All
GovQL
@Alex Stout

# govql-mcp-server An MCP (Model Context Protocol) server for [GovQL](https://govql.us) — gives AI clients like Claude Desktop, Claude Code, and Cursor direct access to the US Congressional GraphQL API at [api.govql.us/graphql](https://api.govql.us/graphql) without bespoke HTTP wiring. For the design rationale (why FastMCP-Python, the passthrough+curated philosophy, roadmap through v0.4), see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md). ## What you can do with it Ask an agent questions like: - *"How did Vermont's two senators vote on the most recent nomination?"* - *"Which legislators in the 118th Congress switched parties during their service?"* - *"Compare Senator Sanders' voting record to Senator Murkowski's on cloture votes in the most recent Congress."* The agent picks the right tool, writes the GraphQL query against the live schema, and parses the response — no manual API wrangling. ## Install The server runs as a per-client subprocess over stdio. Pick your client: ### Claude Desktop Edit `claude_desktop_config.json` (Settings → Developer → Edit Config): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` Restart Claude Desktop. The `govql` tools appear in the tools panel. ### Claude Code Add to `.mcp.json` in your project (or `~/.mcp.json` for global): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` ### Cursor Settings → MCP → Add Server. Use the same `command` / `args` as above. ### Other clients Any MCP-compatible client that supports stdio servers will work. The command is `uvx govql-mcp-server` with no required arguments. ## Tools | Tool | Purpose | |---|---| | `execute_graphql` | Run any GraphQL query against the GovQL endpoint. Returns the result plus an `last_ingest` timestamp so the agent can reason about data freshness. | | `list_types` | Returns the names and kinds of every type in the GovQL schema. Optional `kind` filter (`"OBJECT"`, `"INPUT_OBJECT"`, `"ENUM"`, etc.) to narrow further. Start here when you don't know what's queryable. | | `describe_type` | Returns one type's full details — fields, arg signatures, input fields, enum values. Call after `list_types` to learn the shape of a specific type before writing a query. | ## Configuration All env vars are optional — the package is zero-config for end users. | Env var | Default | Purpose | |---|---|---| | `GOVQL_ENDPOINT` | `https://api.govql.us/graphql` | Endpoint to query. Override to point at a local dev stack. | | `GOVQL_TIMEOUT_MS` | `30000` | Per-request HTTP timeout. | | `LOG_LEVEL` | `INFO` | Logging level. Logs go to stderr only (stdout is reserved for the MCP transport). | ## Limits (enforced by the upstream API) - Max query depth: 10 - Max query complexity: ~10 billion points (`first: N` multiplies child cost by N — keep page sizes reasonable on deeply nested queries) - Rate limit: 100 requests / 60 s per source IP A depth or complexity violation surfaces as a GraphQL `errors` entry in the tool response so the agent can adjust and retry. ## Data freshness Every `execute_graphql` response includes a `last_ingest` ISO timestamp. Vote data refreshes hourly; legislator data refreshes daily. ## Status Version 0.1.0 ships three foundational tools: a GraphQL passthrough (`execute_graphql`) and two narrow schema-discovery tools (`list_types`, `describe_type`). Curated higher-level tools (`find_legislator`, `get_voting_record`, `compare_voters`, etc.) are planned for subsequent releases — see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md) for the roadmap. ## Links - [GovQL project site](https://govql.us) - [GraphQL API](https://api.govql.us/graphql) - [Source / issues](https://github.com/govql/govql)

2 days ago
Thousand Api

14 hours ago