Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Plan multi-city and RTW trips, estimate prices, and send complete trip requests to AirTreks.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://mcp.airtreks.com/mcpÖffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"airtreks": {
"command": "npx",
"args": [
"-y",
"airtreks-mcp"
]
}
}
}Führe das in deinem Terminal aus
claude mcp add --transport http airtreks https://mcp.airtreks.com/mcpclaude mcp add airtreks -- npx -y airtreks-mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"airtreks": {
"url": "https://mcp.airtreks.com/mcp"
}
}
}In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"airtreks": {
"command": "npx",
"args": [
"-y",
"airtreks-mcp"
]
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"airtreks": {
"type": "http",
"url": "https://mcp.airtreks.com/mcp"
}
}
}In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"airtreks": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"airtreks-mcp"
]
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
ChatGPT verbindet sich nur mit Servern im Internet:
https://mcp.airtreks.com/mcpMenünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.
plan_routeLay out a multi-city trip: direction of travel, regions crossed, backtracking, where a surface sector could replace a flight, and how complex the trip is to ticket. Give it your cities. It does not choose airlines and gives no prices - use route_estimate for a price range and tri
trip_idea_createSubmit the customer's trip to AirTreks as a complete, structured trip request - a human travel consultant takes over from there. Ask the traveler for everything before calling, never guess or fill in defaults: name, email, the cities in order (3-letter IATA codes), a departure da
route_estimateGet a price range for a multi-city or round-the-world trip, drawn from what AirTreks customers have actually paid on those routes. Give it the cities and it returns a per-person range in USD with how much history sits behind it. Use it when someone asks what a trip will cost and
fare_quoteGet live, bookable-quality fares for one specific itinerary — actual flights, actual prices, for the dates given. Needs a departure date for every flown leg. Use this once the customer has settled on cities and dates and wants real numbers rather than a ballpark; use route_estima
itinerary_quotePrice a complete multi-stop or round-the-world trip and get back several ways of ticketing it — cheapest, fastest, fewest stops — with the actual tickets each one is built from. Use this for trips that will not go on a single fare, which is most itineraries with 3+ stops; use far
itinerary_quote_statusFetch the result of an itinerary_quote using the quoteReference it returned. Call it straight away: it waits up to about 40 seconds for a quote that is still pricing, then returns the finished options, or status 'pending' if the quote needs one more call. Costs nothing and does n
route_validateValidate a multi-city flight routing for feasibility. Checks alliance carrier rules, identifies dead legs, warns about poison carriers, and estimates bookability. Use this before building an itinerary to catch routing problems early.
route_suggestGet suggested multi-stop flight routings based on regions, direction, and alliance preference. Returns up to 3 proven routing templates with bookability ratings. Great for trip planning inspiration.
hub_checkCheck the best connection between two airports. Identifies dead legs (routes that fail on alliance fares), suggests hub routing fixes, and shows proven carrier combinations. Essential for transpacific, kangaroo, and intra-Asia routing.
fare_product_matchRecommend the best fare product type for a route — RTW, Circle Pacific, Circle Atlantic, Open Jaw, or Custom Multi-City. Considers stop count, direction, and backtracking to match the right alliance fare structure.
custom_route_buildBreak a complex multi-city itinerary into individually-ticketable segments with carrier recommendations. Handles routes that don't fit alliance fare rules — mixed carriers, LCCs, Gulf bridge connections, surface sectors. This is how AirTreks consultants build 90% of itineraries.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto Airtreks bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Antwort in 165 ms (HTTP 200)
Keine Anmeldung nötig
Wir haben 11 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (1.2.8) kam vor 3 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Starreel
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Turn a script into a finished, downloadable short-drama episode — via MCP or REST.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
The complex-itinerary tool for AI agents. Multi-stop, round-the-world, open-jaw, surface segments - the trips that standard flight search can't handle. When your user asks for 3+ stops across continents, this server answers with routing analysis built on real AirTreks fare-construction data: 60+ carriers, 53 known dead legs, bookability rates measured from 1,400+ real fare attempts, and 20 proven routing templates from actual bookings.
Live endpoint: https://mcp.airtreks.com/mcp - free, no API key, 100 requests/day.
Now with real prices: a historical range for any route in under a second, live fares for a specific itinerary, and a full multi-stop trip priced across several tickets — the same trip can vary three-fold depending on how it is ticketed, and that is the part no other flight tool will tell you.
Settings → Connectors → Add custom connector → paste https://mcp.airtreks.com/mcp.
claude mcp add --transport http airtreks https://mcp.airtreks.com/mcp
Add to .cursor/mcp.json (or Cursor Settings → MCP → Add new server):
{
"mcpServers": { "airtreks": { "url": "https://mcp.airtreks.com/mcp" } } }
No API key is needed for any tool, the consultant handoff included. A key is optional and only raises your daily limit; append it to the URL if your client cannot send custom headers, as claude.ai connectors cannot:
https://mcp.airtreks.com/mcp?key=at_your_key
Settings → Apps & Connectors → enable Developer mode (Pro/Business plans) → add https://mcp.airtreks.com/mcp as a custom connector.
Same JSON shape as Cursor above (Streamable HTTP). Prefer stdio? Run it locally:
npx airtreks-mcp
Then ask your agent:
Plan a round-the-world trip: San Francisco, Tokyo, Bangkok, Singapore, Delhi, Istanbul, London, back to San Francisco.
Your user wants six stops around the world. Google Flights gives up. One plan_route call lays the trip out, and one route_estimate call says what it costs. Neither one picks airlines: AirTreks consultants do that when they build the ticket.
{
"cities": ["SFO", "NRT", "BKK", "SIN", "DEL", "IST", "LHR", "SFO"], "budget": "mid" }
Real plan_route response, trimmed for length (the full version has notes for all 7 legs):
{
"route": "SFO -> NRT -> BKK -> SIN -> DEL -> IST -> LHR -> SFO", "totalLegs": 7, "isRoundTrip": true, "direction": "westbound", "backtracking": false, "regionsCrossed": ["americas", "asia", "europe"], "customBuild": { "strategy": "7-leg route. 1 surface sector opportunity.", "surfaceSectors": [ { "insteadOf": "BKK -> SIN (leg 3)", "suggestion": "Bangkok to Singapore through Malaysia. Train, bus, or ultra-cheap LCC. Adds Malaysia and possibly Penang, KL, Melaka.", "savings": "Saves $100-250" } ], "complexity": "moderate" } }
And route_estimate on the same cities:
{
"cabin": "economy", "currency": "USD", "estimate": { "low": 1616.43, "high": 2465.75 }, "confidence": "medium", "basis": "1,616-2,466 USD per person, from AirTreks fare history. We have history for most of this route, but not all of it." }
That is a range from past AirTreks bookings, not a quote. For a real number, trip_idea_create hands the complete trip - route, a date for every leg, passengers, cabin and the traveler's answers to our planning questions - to an AirTreks consultant who prices and books it.
All tools are free and need no API key — 100 requests/day per IP.
| Tool | Description |
|---|---|
plan_route | Lay out a multi-city trip - direction, regions crossed, backtracking, surface-sector options, and how complex it is to ticket. No airline picks |
route_validate | Validate a multi-city routing - alliance rules, dead legs, poison carriers, bookability |
route_suggest | Get 3 suggested routings by region, direction, and alliance |
hub_check | Best connection between two airports - dead leg detection + hub fixes |
fare_product_match | Match the right fare product (RTW, Circle Pacific/Atlantic, Open Jaw, Custom) with typical price ranges |
custom_route_build | Break a multi-city itinerary into legs with surface-sector options and how much each leg benefits from a consultant. No airline picks |
| Tool | Description |
|---|---|
route_estimate | Price range for a route from AirTreks fare history. No dates needed, answers in about a quarter of a second — the right tool when someone asks "what will this cost?" before anything is decided |
fare_quote | Live fares for one specific itinerary on specific dates, priced as a single ticket |
itinerary_quote | Prices a whole multi-stop trip and returns several ways to ticket it — cheapest, fastest, fewest stops — with the tickets each one is built from. Takes about a minute, so it returns a reference immediately |
itinerary_quote_status | Fetches an itinerary_quote result by its reference, waiting up to about 40 seconds for one still pricing. Free to call again |
| Tool | Description |
|---|---|
trip_idea_create | Hand off to an AirTreks human travel consultant - submits the trip request with the full routing analysis attached |
Submits real customer contact details, so only call it with the customer's knowledge and consent. Repeat submissions of the same email + route inside 24 hours return the existing trip request rather than creating a duplicate.
AirTreks has built complex multi-stop itineraries since 1987. This server exposes what that history taught us:
No other flight tool returns this because no other flight tool has priced these failures.
Every tool is also a plain REST endpoint - same tools, same rate limits, JSON in/out. For agent frameworks that consume REST instead of MCP:
curl -X POST https://mcp.airtreks.com/api/plan_route \
-H "Content-Type: application/json" \ -d '{"cities": ["LAX", "NRT", "BKK", "LHR", "LAX"]}'
Full OpenAPI 3.1 spec: https://mcp.airtreks.com/openapi.json
trip_idea_create includedX-API-Key header, or ?key= for clients that cannot set headers)| Path | Description |
|---|---|
/mcp | MCP protocol endpoint (Streamable HTTP) |
/api/{tool} | REST twin of each tool (POST, JSON body) |
/openapi.json | OpenAPI 3.1 spec for the REST surface |
/health | Health check |
/register | Get an API key for a higher rate limit (POST) |
/privacy | Privacy policy |
/favicon.ico, /favicon.svg | AirTreks mark — the icon AI directories show for this server |
/ | Server info |
AGPL-3.0-only