Ktemia MCP Server
OfficialThis server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Ktemia MCP server
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 · 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 |
| Plan, rate limits, and requests left this month. Costs no quota. |
| Airport, airline, hotel, and car rental location codes |
| One-way, round trip, and multi-city fares |
| Stays, with stars, ratings, and amenity filters |
| A hire at a city or airport |
| Every price and booking link for one chosen result |
| 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.
Two packages, one behaviour
The server ships in both languages, so you can run it with whichever runtime your machine already has:
Package | Command | Needs | |
Node |
| Node 20+ | |
Python |
| Python 3.10+ and |
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.
Related MCP server: Jinko Hotel Booking MCP Server
Install
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.
Cursor
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 Code
claude mcp add ktemia -e KTEMIA_API_KEY=your-key -- npx -y @ktemia/mcpPython instead:
claude mcp add ktemia -e KTEMIA_API_KEY=your-key -- uvx ktemia-mcpEverything after -- is the command Claude Code runs. Check it with claude mcp list.
Claude Desktop
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.
Codex CLI
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" }Any other MCP client
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.
Check it before wiring it up
Run the command in a terminal first:
KTEMIA_API_KEY=your-key npx -y @ktemia/mcp # or: uvx ktemia-mcpIt 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.
Try it
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?
How the search tools work
A search is two steps upstream, folded into one tool call:
Call
ktemia_search_flights(or hotels, or cars) with the trip details. You get the first page of results and anextToken.Call the same tool again with only
nextTokento get the next page. WhennextTokenis 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".
Quota
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 |
| Too many requests per second | Wait for |
| The month's allowance is gone | Stop. Retrying cannot help. |
Limits per plan are on pricing.
Security
The key is read from
KTEMIA_API_KEYand sent only as theX-API-Keyheader, over HTTPS, tohttps://api.ktemia.com.The key is never a tool parameter. An agent should never ask you to paste it into a tool call, and the server never exposes it in a result.
A
KTEMIA_API_URLoverride must behttps://(or localhost, for development), and redirects are refused, so the key cannot be sent to another host.Upstream calls carry
X-Ktemia-Client: mcp/<version>, so MCP traffic is distinguishable from direct API traffic in Ktemia's own logs.Every tool is read-only. Nothing here books, pays, holds, or cancels anything.
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 note on the hosted server
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.
Self-host and develop
git clone https://github.com/Ktemiaa/ktemia-mcp.git
cd ktemia-mcpTypeScript
cd typescript
npm install
npm run build
npm testPython
cd python
uv sync # also copies spec/tools.json into the package
uv run pytestPoint 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"].
Layout
spec/tools.json shared tool contract: names, descriptions, enums, defaults
typescript/ the npm package, @ktemia/mcp
python/ the PyPI package, ktemia-mcpTool 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.
Tests
TypeScript
npm test # offline, deterministic, no key needed
npm run test:live # opt-in, spends real quotaPython
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 startThe 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 when KTEMIA_API_KEY is set. They exist to catch upstream contract drift: a renamed field would pass every stubbed test and break every real agent. A full pass is about a dozen requests per language.
npm run inspect:modern # tools/list over the 2026-07-28 protocol
npm run inspect:legacy # tools/list over the older initialize handshakeBoth servers negotiate the protocol era per connection. The Python SDK does this in its stdio loop; the TypeScript one needs serveStdio, and the hand-wired transport silently serves 2025-era clients only, which is why CI checks both eras explicitly.
Releasing
See PUBLISHING.md for the npm and PyPI release process, including the account setup each registry needs and why a bad version cannot be replaced.
Learn more
Docs
Travel API reference — every field and error, with code in cURL, Python, Node, Go, Java, Ruby, and PHP
For agents and tools
Ktemia skills for Claude Code, Codex, and Cursor — the same searches as agent skills rather than MCP tools
Guides
About Ktemia
Ktemia is a search and compare platform for flights, hotels, car rentals, and real estate. Flights, hotels, and cars are live in the API; real estate is next. Use it in the dashboard, through the API, or with the AI copilot.
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Travel tools for AI agents: plan and edit real trips, search stays and tours, import travel videos.
Give AI assistants access to real-time data. Search the web, compare flights, find hotels, and more.
Airbnb, hotel and TripAdvisor search as agent tools.
Live hotel search and booking for AI agents in DACH, the UK and 10 US cities.
Related MCP Servers
- AlicenseAqualityFmaintenanceEnables LLMs to perform travel-related tasks by interacting with Google Maps and travel planning services including location search, place details, and travel time calculations.598MIT
- AlicenseAqualityDmaintenanceEnables AI agents to search, browse, and book hotels from a database of 2 million properties worldwide. Provides comprehensive hotel search capabilities with location lookup, filtering by amenities, detailed property information, and integrated booking functionality.61ISC
- AlicenseAqualityDmaintenanceEnables AI agents to plan trips by searching flights, accommodations, and activities, and managing itineraries collaboratively with role-based permissions.201MIT

DIDA Hotel MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to search, compare, and book hotels with real-time pricing and availability, supporting multiple location types, star ratings, and price filters.12MIT