Travel MCP Server
by jranjan01
README.md
# š Travel MCP Server
A reusable **Model Context Protocol (MCP)** server built with **Python** and the **MCP Python SDK**. It exposes travel-related tools that can be dynamically discovered and invoked by AI clients such as **Google ADK**, **Claude Desktop**, and other MCP-compatible applications.
---
## ⨠Features
- š Built using the **Model Context Protocol (MCP)**
- š ļø Exposes reusable travel tools
- š¤ļø Retrieves live weather information
- š
Provides the current date
- š Automatic tool discovery
- š¤ Compatible with Google ADK and other MCP clients
- š§© Easily extensible with new travel services
---
## šļø Architecture
```text
AI Client (Google ADK / Claude Desktop)
ā
ā¼
MCP Client
ā
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā
Travel MCP Server
ā
āāāāāāāāāāā“āāāāāāāāāā
ā¼ ā¼
Tool 1 Tool 2
ā
ā¼
External APIs
```
---
## š ļø Available Tools
| Tool | Description |
|------|-------------|
| š¤ļø `get_weather(city)` | Returns the current weather for the specified city |
| š
`get_current_date()` | Returns today's date in a human-readable format |
---
## š Running the Server
Install dependencies:
```bash
uv sync
```
Start the MCP server:
```bash
uv run python server.py
```
---
## š§° Tech Stack
| Category | Technologies |
|----------|--------------|
| **Language** | Python |
| **Protocol** | Model Context Protocol (MCP) |
| **SDK** | MCP Python SDK |
| **Weather API** | Open-Meteo API |
| **Package Manager** | uv |
---
## š Related Project
This server is used by the **AI Multi-Agent Travel Planner** built with **Google ADK**.
**Repository:** https://github.com/jranjan01/agentic-travel-plannerTDQS
B3.2/5.0
Scored across 2 tools
Disambiguation5/5
The two tools are completely distinct: one returns the current date, the other returns weather for a city. There is no overlap in their purposes.
Naming Consistency4/5
Both tools use the 'get_' prefix, but one includes a redundant '_tool' suffix. Otherwise, naming patterns are consistent (verb_noun).
Tool Count2/5
With only 2 tools, the server is very thin for a travel domain. Typical travel services would require many more tools (e.g., flights, hotels, destinations).
Completeness2/5
The tool surface is severely incomplete for a travel server. Essential operations like searching destinations, booking flights, or getting hotel info are missing.
Maintenance
ActivityStale
ResponsivenessNo issues