Flightclaw vs MAQAMI Travel
A side-by-side look at the Flightclaw and MAQAMI Travel MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MAQAMI TravelTravel & Transportation · Local subprocess (stdio)Official MCP server for MAQAMI, a hotel and flight booking platform with 3M+ hotels.43FairAuth: no auth requiredVerdict: choose Flightclaw for travel & transportation work over a hosted endpoint; choose MAQAMI Travel for travel & transportation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Flightclaw when
- You need dedicated capabilities in the Travel & Transportation domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
search_flights, search_dates, track_flight.
MChoose MAQAMI Travel when
- You need dedicated capabilities in the Travel & Transportation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M MAQAMI Travel | |
|---|---|---|
| Category | Travel & Transportation | Travel & Transportation |
| Quality signal | 56/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner |
Tools & capabilities
Flightclaw tools 6
search_flightsSearch Google Flights for prices on a routesearch_datesFind cheapest dates to fly across a date range (calendar view)track_flightAdd a route to price tracking with optional target pricecheck_pricesCheck all tracked flights for price changes and alertslist_trackedList all tracked flights with price historyremove_trackedRemove a route from tracking
MAQAMI Travel tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Flightclaw
{
"mcpServers": {
"flightclaw": {
"url": "https://mcp.flightclaw.com/mcp"
}
}
}
MAQAMI Travel
{
"mcpServers": {
"maqami-travel-2": {
"command": "npx",
"args": [
"-y",
"maqami-travel"
]
}
}
}
Frequently asked questions
Flightclaw is categorized under Travel & Transportation and uses a remote HTTP/SSE transport. MAQAMI Travel belongs to Travel & Transportation and uses a local stdio subprocess. Pick Flightclaw for travel & transportation work and MAQAMI Travel for travel & transportation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Flightclaw has no declared pricing — check the project's own site. MAQAMI Travel is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add flightclaw and maqami-travel-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Flightclaw has a quality signal of 56/100 (Good) with 1 views, 0 installs and 75 GitHub stars. MAQAMI Travel has 43/100 (Fair) with 0 views, 0 installs and 2 GitHub stars.