Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Flexible multi-leg, multi-airport flight search - cheapest valid combination across an itinerary.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
TRAVELPAYOUTS_TOKEN, SERPAPI_KEY, RIHLA_PROFILE标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"rihla": {
"command": "uvx",
"args": [
"rihla-mcp"
],
"env": {
"TRAVELPAYOUTS_TOKEN": "your-value",
"SERPAPI_KEY": "your-value",
"RIHLA_PROFILE": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add rihla --env TRAVELPAYOUTS_TOKEN=your-value --env SERPAPI_KEY=your-value --env RIHLA_PROFILE=your-value -- uvx rihla-mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"rihla": {
"command": "uvx",
"args": [
"rihla-mcp"
],
"env": {
"TRAVELPAYOUTS_TOKEN": "your-value",
"SERPAPI_KEY": "your-value",
"RIHLA_PROFILE": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"rihla": {
"type": "stdio",
"command": "uvx",
"args": [
"rihla-mcp"
],
"env": {
"TRAVELPAYOUTS_TOKEN": "your-value",
"SERPAPI_KEY": "your-value",
"RIHLA_PROFILE": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
RIHLA_PROFILE env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 leojg 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:TRAVELPAYOUTS_TOKEN, SERPAPI_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有: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、图片和脚本已被移除。链接会离开本站。
Rihla (رحلة), *"the journey."* Named for Ibn Battuta's 14th-century travelogue —
the record of history's farthest-traveling explorer, who left Tangier for Mecca and
kept going for 29 years and 75,000 miles.
Flexible multi-leg, multi-airport flight search that finds the cheapest route across an entire itinerary — available as a CLI and as an MCP server for AI agents.
Consumer flight sites price one leg at a time. Rihla treats the whole trip as a single optimization problem:
*"Leave Montevideo — or Buenos Aires, it's a ferry ride away — around September 15
for Europe. Stay 20–30 days, then Japan for 15, then home. What's the cheapest
combination?"*
That query has three legs, flexible airports on both ends of each, a flexible departure window, and stay-duration constraints linking the legs. Rihla prices each leg's date×airport grid once, then finds the cheapest valid combinations in pure local compute — so even a 3–4 leg flexible query costs only a handful of API calls.
1. 1,297 USD (44 days door-to-door)
MVD -> AMS 2026-09-08 $ 383 [mock, cached] AA AA127 FRA -> NRT 2026-10-07 $ 481 [mock, cached] KL KL411 HND -> EZE 2026-10-22 $ 433 [mock, cached] AZ AZ933
Note the airport substitution at work: it enters Europe through Amsterdam, leaves from Frankfurt, and flies home into Buenos Aires — each leg independently picks the cheapest airport pair from its sets.
Requires Python ≥ 3.10.
pip install rihla # CLI
pip install "rihla[mcp]" # CLI + MCP server
Runs offline out of the box (no keys needed — a deterministic mock data source):
RIHLA_PROFILE=mock rihla # the canonical demo trip above
rihla examples/queries/canonical.json # same trip, from a query file rihla -i # build a query interactively
For live prices, copy .env.example to .env and add at least a Travelpayouts token (free). See Data sources.
A query is a small JSON file: your origin airports, the ordered stops, a departure window for the first leg, and how long to stay at each stop. Downstream date windows are derived — you never hand-compute "if I leave Sep 15 and stay 20–30 days, when do I fly to Tokyo?"
{
"origins": ["MVD", "EZE", "AEP"], "stops": ["EUROPE", ["NRT", "HND"], "MVD_AREA"], "earliest": "2026-09-08", "latest": "2026-09-22", "stays": [[20, 30], [15, 15]], "date_step": 3, "top": 5 }
EUROPE (MAD, BCN, LIS, CDG, FCO, AMS, FRA), TOKYO (NRT, HND), MVD_AREA (MVD, EZE, AEP). Make the last stop your origin set to fly home.[min, max] nights at each intermediate stop (len(stays) == len(stops) - 1).USD).rihla -i walks you through these questions and prints the resulting JSON to save for reuse. Add --links to any run to show booking URLs.
Rihla is honest about data quality rather than pretending everything is bookable:
cached when the price is indicative (Travelpayouts data is aggregated search history, not a live fare) versus a real, bookable fare (SerpApi / Google Flights).Ranking is price-only in v0.1. Open-jaw within a region is allowed by default (enter Europe at one city, leave from another); the cost of repositioning inside the region is not modeled.
| Source | Role | Cost | Notes |
|---|---|---|---|
| Travelpayouts / Aviasales | Primary | Free | Cached, redistribution-licensed. A month of prices per call, so the call budget stays tiny. Prices indicative; coverage follows route popularity. |
| SerpApi (Google Flights) | Fill | 250 free searches/mo (BYO key) | Real bookable fares; fills routes Travelpayouts misses. Only spent on uncovered routes. |
| Mock | Offline | — | Deterministic fake prices for development and demos. |
Configure via .env (see .env.example) or environment variables: TRAVELPAYOUTS_TOKEN, SERPAPI_KEY, and RIHLA_PROFILE:
local (default) — every source whose key is set, including SerpApi.hosted — redistribution-licensed sources only (SerpApi disabled: it scrapes Google, so do not serve it from a public hosted instance).mock — force the offline fetcher, no network.With no keys set, Rihla falls back to the mock source and says so.
Rihla ships an MCP server (stdio) so agents like Claude can run trip searches:
pip install "rihla[mcp]"
claude mcp add rihla -- rihla-mcp # Claude Code
or in any MCP client config:
{
"mcpServers": { "rihla": { "command": "rihla-mcp", "env": { "TRAVELPAYOUTS_TOKEN": "your-token", "SERPAPI_KEY": "your-key" } } } }
(The server also loads a .env from its working directory, so env is optional if you run it from a checkout.)
It exposes two read-only tools with an enforced etiquette:
mcp-name: io.github.leojg/rihla
Leg prices are independent — the MVD→Europe fare doesn't depend on the Tokyo dates. So Rihla fetches each leg's date×airport grid once, then enumerates valid date combinations (respecting the stay constraints) entirely in memory. The combinatorial explosion lives in local compute, not in API calls.
core.py data model + the pure optimizer (no I/O)
fetchers/ PriceFetcher protocol: Mock / Travelpayouts / SerpApi + merge places.py airport sets / regions api.py search_trip: serializable query in, result dict out cli.py thin CLI over search_trip mcp_server.py thin MCP wrapper over the same seam
Adding a data source (Duffel, Kiwi, …) is one more class implementing a one-method protocol: quote(origin, dest, day) -> Quote.
Scope (v0.1): flight search only — no lodging, no booking or payments, single adult, one cabin. Search returns booking links, never handles the transaction.
git clone https://github.com/leojg/rihla && cd rihla
pip install -e ".[dev,mcp]" pytest # offline, no keys needed ruff check .
Licensed under the Apache License 2.0 — see LICENSE.