Context7
Up-to-date docs for AI agents
제작자가 쓴 설명(영어 원문)
Real-time Google Flights: one-way and round-trip fares over date ranges, with price verdicts.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
x-rapidapi-key비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.
터미널에서 이 명령어를 실행하세요
claude mcp add --transport http google-flights https://flights.flightpowers.com/mcp --header 'x-rapidapi-key: your-value'실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"google-flights": {
"url": "https://flights.flightpowers.com/mcp",
"headers": {
"x-rapidapi-key": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"google-flights": {
"type": "http",
"url": "https://flights.flightpowers.com/mcp",
"headers": {
"x-rapidapi-key": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
x-rapidapi-key 비밀 HTTP header이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
게시자(flightpowers.com)가 저장소 소유자(mtnrabi)가 아니에요. 다른 사람이 등록했을 수 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 0개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: x-rapidapi-key
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.2.0)은 2개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Context7, Codebase Memory, Exa
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
An MCP server for live flight prices and hotel rates: Claude, Claude Code, Cursor, Cline and any other MCP client get real-time Google Flights fares and Booking.com room rates as tools. One call searches a date range and a list of destination airports, every fare carries Google's own low / typical / high verdict and price range, and a round trip is priced as one request (both legs, one total, one booking link). Hosted at https://flights.flightpowers.com/mcp (hotels at https://hotels.flightpowers.com/mcp), nothing to install. It finds and prices, it does not book.
Built by FlightPowers, a travel data API for developers and AI agents: REST, MCP servers and an n8n node on one RapidAPI key. Sign in with Google and your first 10 searches each day are free.
Where to get a key: Google Flights Live API and Booking Live API on RapidAPI. A free pack of 10 searches a month, then PRO is $10 for 2,500 flight searches, about a sixth of SerpApi's price per search (their cheapest plan is $25 for 1,000).
One URL, either way in:
claude mcp add --transport http google-flights https://flights.flightpowers.com/mcp
In a client that supports MCP authorization, a Sign in button appears: you sign in with Google, and your first 10 searches each day are free on our key, with nothing to paste. Paste your own RapidAPI key once on the /connect page when you want that cap gone, and nothing goes in your client config either way. In a client that shows no Sign in button, bring the key yourself:
claude mcp add --transport http google-flights https://flights.flightpowers.com/mcp --header "x-rapidapi-key: YOUR_RAPIDAPI_KEY"
Same URL, both times. A request carrying a credential of any kind is served; a request carrying nothing at all is answered 401 with the OAuth metadata, which is what makes the Sign in button appear. https://flights.flightpowers.com/mcp/oauth is still live and demands the sign-in on the first request, for clients whose auth mode is fixed when a server is added.
Hosted. Nothing to clone, nothing to build. Listed in the official MCP Registry as com.flightpowers/google-flights-mcp. Health check: /health.
No key yet? You do not need one to start. Add the URL above, sign in with Google, and the first 10 searches each UTC day run on our key, with nothing to paste. The exact unit counted is in Try it with no key.
Need a key? Subscribe to the Google Flights Live API on RapidAPI, free tier available, and copy your x-rapidapi-key: https://rapidapi.com/mtnrabi/api/google-flights-live-api
Want more free searches than that, and do not mind ads? There is a separate free, ad-supported server: claude mcp add --transport http google-flights-free https://free-trial.flightpowers.com/mcp (50 searches a day and 250 a month per signed-in account, one disclosed sponsored card per result, fan-out capped at 15, and clients that cannot render the sponsored card may be capped further.) Come back here when the ads, the 15-search cap, or those client restrictions get in your way.
Two tools that answer a *fare question*, not a *date lookup*.
nights value instead of a fixed return date, and expand them internally.price_insights_low, price_insights_high, and a price_range_in_relation_to_other_periods verdict of low / typical / high. That is what lets an agent answer "$209 is typical here, don't rush" instead of just quoting a number.buy_link to Google Flights.api_usage: requests used by this call, and what is left on the caller's plan. See Spend reporting.search_coverage, so the model can say honestly which dates and destinations the answer is based on.Results are live fares. They go stale within minutes: when you need a current price, search again rather than reusing an earlier result, and state when the data was fetched.
A signed-in account gets 10 free searches per UTC day on our key, with nothing to paste into your client. Sign in the way your client offers it, or at https://flights.flightpowers.com/connect, and ask for a fare. Ten is what the hosted deployment runs today; /health reports the live values as trial_enabled and trial_day_cap and is the number to trust. (The allowance is off by default in this code and needs both PAID_TRIAL_DAY_CAP and PAID_TRIAL_RAPIDAPI_KEY set on purpose, so a deployment you run yourself has none until you configure one.)
A search is one date x destination combination, so one call with a three-day range spends three. The allowance is held for the whole plan before the first request goes out and whatever the fan-out did not send is given straight back, so two calls at once cannot both spend it. Every result carries a trial block with the count and the cap. Past the cap the tools answer with search_status: "trial_exhausted" and no results -- never an error, and retrying does not help; the allowance renews at 00:00 UTC.
A free search is capped by what is left of the day: a range or grid larger than that (a whole month at three trip lengths is 93 searches) is refused before anything runs, with the counts and a smaller question to ask instead. With your own key the cap rises by itself to cover a month-sized request. Comparing several sources in one call (compare_hotel_rates, on a deployment that enables it) is not part of the allowance and asks for your own key.
Connecting your own RapidAPI key removes the cap entirely. That is the next section.
The server holds no upstream credential of its own. Every search beyond the free allowance is billed to *your* RapidAPI subscription, which is why the key travels with the request.
x-rapidapi-key.If a key is missing and the allowance is not available to you, the tools do not fail silently and do not spend anything. They return needs_api_key: true with the signup URL and these instructions, phrased for the model to read back to you.
| Way | How | When to use it |
|---|---|---|
| Header (preferred) | --header "x-rapidapi-key: YOUR_RAPIDAPI_KEY" | Anything that lets you set headers. Keys stay out of URLs, and therefore out of proxy and access logs. |
| Query parameter | https://google-flights-mcp.flightpowers.com/mcp?rapidapi_key=YOUR_RAPIDAPI_KEY | Hosts that only let you paste a URL: claude.ai's custom-connector dialog is the case that matters. |
| Client API-key field | Paste the key into the client's own "API key" box | Hosts that send authorization: Bearer or x-api-key. Smithery's saved-config form (config.rapidApiKey=) is also accepted. |
First non-empty source wins, in that order. The key is never logged, never echoed into an error message, and never returned in a tool response.
/connectThis is the page the sign-in URL at the top of this README sends you to. A client that speaks MCP authorization walks you through it on its own; the steps below are the same thing done by hand.
Where a deployment has it enabled (check connect_enabled on /health), there is a page at /connect that replaces all of the above with a sign-in:
…/mcp?fp_token=fpk_…, and use that as the server URL in your MCP client. Clients that let you set headers can send the same token as Authorization: Bearer fpk_… instead. (It is hidden until you ask for it: that URL is a 90-day bearer credential for your plan, and a page that prints one by default puts it in every screenshot and screen share.)If your client signed you in itself -- Claude, Cursor, ChatGPT and anything else that speaks MCP authorization -- there is no URL to copy. /connect says so: it shows the key you connected and tells you to go back to your assistant. There is a link on it for the case where a second client cannot sign in and does need a connect URL.
What that buys you: your RapidAPI key is not in your client config, not in a URL, and not in whatever logs that URL passes through. What it costs: the server stores your key, encrypted, and knows your Google account id and email address. Disconnect on the same page deletes the record and kills every connect token for your account, immediately. The full description is section 2a of the privacy policy.
Some details worth knowing:
x-rapidapi-key header (or any of the other channels above) *and* carry a connect token, the request's own key is used. Nothing you already have set up changes behaviour because you signed in.needs_api_key reply telling you to reconnect. It never falls back to somebody else's subscription and never spends anything./connect on your own deploymentOff unless all four of these are set. A half-configured deployment registers none of the routes and serves keyed callers exactly as before; /health reports connect_enabled so that is visible rather than guessed.
| Variable | What it is |
|---|---|
GOOGLE_OAUTH_CLIENT_ID | Google Cloud Console → Credentials → OAuth client ID, type Web application. Ends .apps.googleusercontent.com. |
GOOGLE_OAUTH_CLIENT_SECRET | The same client's secret (GOCSPX-…). |
MCP_KEY_MASTER | 32 bytes, base64: openssl rand -base64 32. Encrypts stored keys (AES-256-GCM) and derives the cookie and token signing keys. |
DATABASE_URL | Neon Postgres, pooled endpoint (…-pooler…). Schema: migrations/001_mcp_user_keys.sql. |
Optional: MCP_CONNECT_VALIDATE=0 stores a pasted key without checking it first.
Authorised redirect URIs to register on the Google client, one per product origin, exactly:
https://google-flights앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요