mcp-tellus-search
Enables Claude to search for geo entities such as cities, airports, and hotels using Skyscanner's Tellus API. Supports entity lookup, search by type/location, fetching children, and nearby entities.
README
mcp-tellus-search
A Model Context Protocol (MCP) server that exposes Skyscanner's Tellus (Travel API v2) to Claude.
What is MCP?
MCP (Model Context Protocol) is a protocol that lets Claude call external tools. This project packages Tellus API functions as MCP tools so Claude can search geo entities (cities, airports, hotels, etc.) directly during a conversation.
When Claude is connected to this MCP server, it can:
- Look up entities by ID
- Search entities by type or location
- Fetch child entities of a parent (e.g. all hotels in a city)
- Find nearby entities by radius
- Get suggested airports for a city
How it works
Architecture
Claude Code
│
│ stdio (JSON messages)
▼
Docker Container ←── mcp.run() blocks here, waiting for requests
│
└── python src/server.py
│
└── FastMCP registers all @mcp.tool() functions
│
└── requests → Tellus API (gateway.skyscanner.net)
Key concepts
@mcp.tool()decorator registers a function as an MCP tool. Claude sees the function name, docstring, and type annotations — it never sees the raw source code.mcp.run()starts the server and blocks, listening on stdin. The container stays alive for the entire Claude session (one container per session).- The container is started automatically by Claude Code when it reads
.mcp.json, and destroyed on exit (--rm).
Project structure
.
├── Dockerfile # Packages the server into a Docker image
├── .mcp.json # Tells Claude Code how to launch the server
├── requirements.txt # Python dependencies installed inside the image
└── src/
└── server.py # MCP tools + Tellus API helper functions
Available tools
| Tool | Description |
|---|---|
get_entities |
Fetch entities by ID list (up to 200) via GET /v2/entities |
search_entities |
Search entities by type/ID with optional name filter via POST /v2/search |
fetch_children |
Fetch child entities of a parent, auto-selects filter strategy by type |
fetch_nearby_entities |
Fetch entities within a radius of an entity or lat/lon |
get_entity_type |
Resolve the type of a single entity |
get_suggested_airports |
Get suggested airports for a city (deprecated endpoint, limited coverage) |
fetch_children_parallel |
fetch_children for multiple parents in parallel |
fetch_nearby_entities_parallel |
fetch_nearby_entities for multiple locations in parallel |
search_entities_parallel |
search_entities for multiple queries in parallel |
Filter strategy by entity type
| Entity type | Filter used |
|---|---|
| Hotel, Airport, CarHireOffice | relations.geopolitical_parents:containsAny |
| TouristAttraction, MetroStation, District, City | hierarchy:isChildOf |
Build and deploy
Prerequisites
- Docker Desktop installed and running
- Claude Code
1. Build the image
cd /path/to/this/project
docker build -t mcp-tellus-search .
docker build executes all RUN instructions in the Dockerfile (installs dependencies, copies source). The resulting image is stored in your local Docker registry.
docker run is what actually starts the container and triggers CMD ["python", "src/server.py"].
2. Configure Claude Code
Project-level (only active when Claude Code is opened in this directory):
.mcp.json is already configured:
{
"mcpServers": {
"mcp-tellus-search": {
"command": "docker",
"args": ["run", "--rm", "-i", "mcp-tellus-search"]
}
}
}
Global (active in any directory):
Add to ~/.claude.json under mcpServers:
"mcp-tellus-search": {
"type": "stdio",
"command": "docker",
"args": ["run", "--rm", "-i", "mcp-tellus-search"]
}
3. Restart Claude Code
Run /mcp to verify the server shows as connected.
How Claude Code finds .mcp.json
Claude Code scans upward from the current working directory for .mcp.json, the same way git looks for .git. It also loads global MCP servers from ~/.claude.json. Project-level config takes precedence over global config for servers with the same name.
Distributing the image
To share this server with others without requiring them to build from source:
# Push to Docker Hub
docker push your-username/mcp-tellus-search
# Others only need .mcp.json pointing to the image name
# Docker pulls it automatically on first run
This is the key advantage of Docker packaging: the recipient needs no Python, no pip install — just Docker and the .mcp.json config file.
Tellus API reference
- Base URL:
https://gateway.skyscanner.net/travel-api/v2 - Docs: Travel API v2 User Guide
- Use
geometry_centroidinstead ofgeometry(per API guidelines) - Parallel fetch functions use
ThreadPoolExecutorwithMAX_WORKERS=10(~8x speedup) - Do not use
requests.Session()in parallel code — use plainrequests.post()which is thread-safe
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。