Mu
News, web search, mail, markets, weather, places, files, calendar, contacts. 67 tools, one endpoint.
Search and compare flights, hotels and rental cars, with each seller's price and booking link.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 19/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 39/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 25 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Ktemia。按照 https://mcp.popnx.com/i/ktemiaa-ktemia-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.ktemia.com) · ✓ 命令已检查 2026年11月19日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 5 分钟
需要 Ktemia 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Ktemiahttps://mcp.ktemia.com/mcp在 Request headers 下添加这个名称和值
X-API-Key<在这里粘贴你的密钥>只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsKtemia
用 Ktemia 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Ktemia,或回答中出现 Ktemia 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Ktemia
Ktemia 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式
A · 使用能连接 Ktemia 的应用
B · 旅行、地图与天气 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code · 约 5 分钟
需要 Ktemia 的密钥(在开发者网站创建)
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user ktemia https://mcp.ktemia.com/mcp --header 'X-API-Key: your-value'按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 Ktemia 在列表中并显示已连接
用 Ktemia 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Ktemia,或回答中出现 Ktemia 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 5 分钟
需要 Ktemia 的密钥(在开发者网站创建)
在 Ktemia 的设置中,X-API-Key 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Ktemia 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Ktemia,或回答中出现 Ktemia 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 5 分钟
需要 Ktemia 的密钥(在开发者网站创建)
在 Ktemia 的设置中,X-API-Key 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Ktemia 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Ktemia,或回答中出现 Ktemia 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --transport http --scope user ktemia https://mcp.ktemia.com/mcp --header 'X-API-Key: your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"ktemia": {
"url": "https://mcp.ktemia.com/mcp",
"headers": {
"X-API-Key": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"ktemia": {
"type": "http",
"url": "https://mcp.ktemia.com/mcp",
"headers": {
"X-API-Key": "your-value"
}
}
}
}Claude Code
claude mcp add --scope user ktemia --env KTEMIA_API_KEY=your-value -- npx -y @ktemia/mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"ktemia": {
"command": "npx",
"args": [
"-y",
"@ktemia/mcp"
],
"env": {
"KTEMIA_API_KEY": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"ktemia": {
"command": "npx",
"args": [
"-y",
"@ktemia/mcp"
],
"env": {
"KTEMIA_API_KEY": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"ktemia": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ktemia/mcp"
],
"env": {
"KTEMIA_API_KEY": "your-value"
}
}
}
}KTEMIA_API_KEY 机密 必填 env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 Ktemiaa 验证,该账户拥有此仓库
代码最后更新于昨天
使用 MIT
在 253 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
尚未检查
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/ktemiaa-ktemia-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:X-API-Key, KTEMIA_API_KEY
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于昨天,最新版本(0.1.5)于昨天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:Mu, Award Travel Finder, Killbottleneck, Gondola Award Travel Search, Whimsical
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
News, web search, mail, markets, weather, places, files, calendar, contacts. 67 tools, one endpoint.
Search award flight availability and points pricing across 27 airlines and 23 loyalty programs.
Free-to-self-host goal and process maps for humans and AI agents, with REST API and MCP.
Compare cash vs points on hotels, flights, and cars. Checkout supported hotels and rental cars.
Create and edit flowcharts, mind maps, wireframes, and docs in Whimsical, or search your workspace.
| 本项 Ktemia | Mu | Award Travel Finder | Killbottleneck | Gondola Award Travel Search | Whimsical | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 是 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 是 |
| 基础检查 | 5/5 | 4/4 | 3/3 | 3/3 | 4/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | MIT | MIT | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A Model Context Protocol server that searches and compares flights, hotels, and rental cars with the Ktemia API. Point Cursor, Claude Code, Claude Desktop, Codex, or any MCP client at it, ask in plain language, and the agent looks up the place, runs the search, and returns each seller's price with a booking link.
Available for both Node (npx -y @ktemia/mcp) and Python (uvx ktemia-mcp).
[Get a free API key](https://app.ktemia.com/api-keys) · API reference · Getting started · Pricing · Guide: flights in Cursor and Claude · Changelog
Ktemia compares prices. It does not book the ticket, the car, or the room. The traveller books on the seller's site.
| Tool | Use it for |
|---|---|
ktemia_key_status | Plan, rate limits, and requests left this month. Costs no quota. |
ktemia_lookup | Airport, airline, hotel, and car rental location codes |
ktemia_search_flights | One-way, round trip, and multi-city fares |
ktemia_search_hotels | Stays, with stars, ratings, and amenity filters |
ktemia_search_cars | A hire at a city or airport |
ktemia_get_details | Every price and booking link for one chosen result |
ktemia_get_hotel_reviews | Guest reviews for one hotel |
Every plan can use the MCP server, including the Free plan with its 100 requests a month. A paid plan buys request volume and rate, not access.
The server ships in both languages, so you can run it with whichever runtime your machine already has:
| Package | Command | Needs | |
|---|---|---|---|
| Node | @ktemia/mcp | npx -y @ktemia/mcp | Node 20+ |
| Python | ktemia-mcp | uvx ktemia-mcp | Python 3.10+ and uv |
They are not two codebases that happen to agree. Both read one shared contract, spec/tools.json, for every tool name, description, enum, and limit, and CI fails if they drift. Same seven tools, same wording, same errors — pick either.
npx and uvx both fetch the package on first run and cache it, so there is nothing to install or upgrade by hand.
You need an API key from app.ktemia.com/api-keys. Free, no card.
Each example below shows Node first, then Python. Use one, not both — two copies of the same server would just show every tool twice.
Add to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):
{
"mcpServers": { "ktemia": { "command": "npx", "args": ["-y", "@ktemia/mcp"], "env": { "KTEMIA_API_KEY": "${env:KTEMIA_API_KEY}" } } } }
Python instead:
{
"mcpServers": { "ktemia": { "command": "uvx", "args": ["ktemia-mcp"], "env": { "KTEMIA_API_KEY": "${env:KTEMIA_API_KEY}" } } } }
${env:KTEMIA_API_KEY} reads the key from your shell environment, so the key itself is not committed in a project file. Export it in your shell profile:
export KTEMIA_API_KEY="your-key"
To paste the key directly instead, put it in ~/.cursor/mcp.json rather than a project file, and do not commit it.
claude mcp add ktemia -e KTEMIA_API_KEY=your-key -- npx -y @ktemia/mcp
Python instead:
claude mcp add ktemia -e KTEMIA_API_KEY=your-key -- uvx ktemia-mcp
Everything after -- is the command Claude Code runs. Check it with claude mcp list.
Add to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, or %APPDATA%\Claude\claude_desktop_config.json on Windows:
{
"mcpServers": { "ktemia": { "command": "npx", "args": ["-y", "@ktemia/mcp"], "env": { "KTEMIA_API_KEY": "your-key" } } } }
Python instead: "command": "uvx", "args": ["ktemia-mcp"].
Restart Claude Desktop, then ask for a flight.
Claude Desktop launches servers from a GUI process that does not read your shell profile, so npx or uvx must be somewhere it can see. If the server fails to start, use the absolute path from which npx or which uvx as command.
Add to ~/.codex/config.toml:
[mcp_servers.ktemia]
command = "npx" args = ["-y", "@ktemia/mcp"] env = { KTEMIA_API_KEY = "your-key" }
Python instead:
[mcp_servers.ktemia]
command = "uvx" args = ["ktemia-mcp"] env = { KTEMIA_API_KEY = "your-key" }
The server speaks MCP over stdio. Run npx -y @ktemia/mcp or uvx ktemia-mcp with KTEMIA_API_KEY in the environment.
It negotiates the protocol revision per connection, so it answers both current (2026-07-28) clients and clients that still open with the older initialize handshake.
Run the command in a terminal first:
KTEMIA_API_KEY=your-key npx -y @ktemia/mcp # or: uvx ktemia-mcp
It should sit silently waiting for JSON-RPC on stdin; Ctrl-C to quit. An immediate error means the environment is wrong, and reading it here is easier than digging through a client's logs.
Find flights from Lisbon to London on 15 March 2027.
I need a car at Austin airport from 10 to 17 March, automatic, and I am 23.
A hotel in London for two, 10–12 March, four stars or better, free cancellation if you can find it. Then show me recent reviews for the one I pick.
How many Ktemia requests do I have left this month?
A search is two steps upstream, folded into one tool call:
ktemia_search_flights (or hotels, or cars) with the trip details. You get the first page of results and a nextToken.nextToken to get the next page. When nextToken is absent, that was the last page.Tokens are opaque and expire one hour after the search starts. If a token expires, start a new search rather than retrying it.
Hotel and car searches need a location id from ktemia_lookup — the locationId field of a result, which is a numeric string like 29230, not a city name. Flight searches take IATA codes from the code field instead, such as LHR for Heathrow or LON for every London airport.
ktemia_get_details expands one result into every price and booking link. Search pages carry only the leading offers, so this is the call that answers "where do I actually book this".
Every tool call is one request against your plan's monthly quota, with one exception: ktemia_key_status is free and keeps answering after the quota is spent, which is how an agent diagnoses a QUOTA_EXCEEDED error without making it worse.
A search costs at least two requests — one to start it, one per page read — so budget accordingly. The quota is shared across every key on an account, so creating a second key does not raise the limit.
Two different errors both arrive as HTTP 429, and they mean opposite things:
| Code | Meaning | What to do |
|---|---|---|
RATE_LIMIT_EXCEEDED | Too many requests per second | Wait for Retry-After, then retry |
QUOTA_EXCEEDED | The month's allowance is gone | Stop. Retrying cannot help. |
Limits per plan are on pricing.
KTEMIA_API_KEY and sent only as the X-API-Key header, over HTTPS, to https://api.ktemia.com.KTEMIA_API_URL override must be https:// (or localhost, for development), and redirects are refused, so the key cannot be sent to another host.X-Ktemia-Client: mcp/ , so MCP traffic is distinguishable from direct API traffic in Ktemia's own logs.Consider using a separate key for your editor, so you can revoke it without touching a production integration. The quota is per account, so a second key costs you nothing in allowance.
A hosted server at mcp.ktemia.com is planned, and it will accept your API key and forward it to api.ktemia.com. The MCP security guidance names that shape "token passthrough" and advises against it, so it is worth being explicit about why it is acceptable here: the guidance targets OAuth audience confusion, where a server accepts a token minted for a different service and deceives a third-party resource server into trusting it. A Ktemia key is first-party, the MCP server is Ktemia, and the quota and rate limits live on that same key upstream — one audience, no third party, and no control bypassed. If that changes, OAuth 2.1 is the migration, and the credential source is a single seam in the code so it will not ripple into the tools.
Until then, run it locally over stdio as above.
git clone https://github.com/Ktemiaa/ktemia-mcp.git
cd ktemia-mcp
TypeScript
cd typescript
npm install npm run build npm test
Python
cd python
uv sync # also copies spec/tools.json into the package uv run pytest
Point your client at whichever you built:
{
"mcpServers": { "ktemia": { "command": "node", "args": ["/absolute/path/to/ktemia-mcp/typescript/dist/index.js"], "env": { "KTEMIA_API_KEY": "your-key" } } } }
For Python, "command": "uv" with "args": ["--directory", "/absolute/path/to/ktemia-mcp/python", "run", "ktemia-mcp"].
spec/tools.json shared tool contract: names, descriptions, enums, defaults
typescript/ the npm package, @ktemia/mcp python/ the PyPI package, ktemia-mcp
Tool names, descriptions, enums, and defaults live in spec/tools.json, which both implementations read. The descriptions are what steer an agent — text like "a guessed city searches the wrong trip and spends quota" is what stops it inventing a departure airport — so they are written once rather than copied, since prose that drifts between two packages would change agent behaviour with nothing in any log to show why.
Each package copies that file in at build time, because neither npm nor a Python wheel can include a file from outside its own directory. typescript/scripts/sync-spec.mjs and python/hatch_build.py do that, and CI asserts both copies are byte-identical to the original.
TypeScript
npm test # offline, deterministic, no key needed
npm run test:live # opt-in, spends real quota
Python
uv run pytest # offline; the live tests skip themselves
KTEMIA_API_KEY=your-key uv run pytest tests/test_live.py uv run python scripts/smoke_wheel.py # checks an installed build can start
The offline suites stub the transport, so they cover what production cannot reach on demand — a spent quota, a rate limit, a timeout, a malformed upstream body — and assert that a missing required field is refused locally without an upstream call, so a guessed search cannot cost you a request.
python/tests/test_parity.py is the one that keeps the packages honest: it asserts both register the same seven tools in the same order, that every description contains the shared spec's prose verbatim, that every metered tool says so and ktemia_key_status does not, and that no numeric parameter advertises an absurd bound.
The live suites run only