plantrip-mcp-server
# Plantrip MCP Server
[](https://www.npmjs.com/package/plantrip-mcp-server)
[](https://opensource.org/licenses/MIT)
An MCP (Model Context Protocol) server that connects AI assistants like Claude to [Plantrip's](https://plantrip.io) travel planning tools. Create itineraries, generate packing lists, get weather insights, estimate trip costs, and more.
## Features
- **Create Itineraries** - Generate detailed day-by-day travel plans with activities, costs, and locations
- **Packing Lists** - AI-powered packing lists based on destination, weather, and activities
- **Weather Insights** - Detailed climate information and weather patterns
- **Cost Estimates** - Budget breakdowns for accommodations, food, transport, and activities
- **Travel Expert** - Ask any travel question and get expert answers
- **Travel Guides** - Search Plantrip's library of destination guides
- **Tour Availability** - Check tour dates and submit booking inquiries
## Quick Start
### 1. Get an API Key
1. Go to [plantrip.io/developers](https://plantrip.io/developers)
2. Sign in (free — no subscription required)
3. Create a new API key
### 2. Configure Claude Desktop
Add to your Claude Desktop config:
**macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
**Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
```json
{
"mcpServers": {
"plantrip": {
"command": "npx",
"args": ["-y", "plantrip-mcp-server"],
"env": {
"PLANTRIP_API_KEY": "pt_agent_your_key_here"
}
}
}
}
```
### 3. Restart Claude Desktop
Quit and reopen Claude Desktop to load the server.
## Usage
Ask Claude things like:
- *"Create a 5-day itinerary for Tokyo focused on food and culture"*
- *"What should I pack for a hiking trip to Patagonia in March?"*
- *"What's the weather like in Bali in August?"*
- *"How much would a week in Iceland cost for 2 people?"*
- *"What are the visa requirements for US citizens visiting Vietnam?"*
## Available Tools
| Tool | Description |
|------|-------------|
| `create_itinerary` | Create a new travel itinerary |
| `get_itinerary_status` | Poll generation status |
| `get_itinerary` | Retrieve complete itinerary |
| `modify_itinerary` | Modify with natural language |
| `list_user_trips` | List saved trips |
| `save_itinerary` | Save to user's trips |
| `delete_trip` | Remove from saved trips |
| `generate_packing_list` | AI packing list |
| `ask_travel_expert` | Travel Q&A |
| `get_weather_insights` | Weather/climate info |
| `estimate_trip_cost` | Budget breakdown |
| `search_guides` | Search travel guides |
| `get_tour_availability` | Check tour dates |
| `submit_tour_inquiry` | Tour booking inquiry |
## Claude Code Setup
Add to `.mcp.json` in your project:
```json
{
"mcpServers": {
"plantrip": {
"command": "npx",
"args": ["-y", "plantrip-mcp-server"],
"env": {
"PLANTRIP_API_KEY": "pt_agent_your_key_here"
}
}
}
}
```
## Environment Variables
| Variable | Required | Description |
|----------|----------|-------------|
| `PLANTRIP_API_KEY` | Yes | Your API key from [plantrip.io/developers](https://plantrip.io/developers) |
| `PLANTRIP_API_URL` | No | API base URL (default: `https://plantrip.io/api/agent`) |
## REST API
You can also use the Plantrip API directly:
```bash
curl -X POST https://plantrip.io/api/agent/execute \
-H "X-API-Key: pt_agent_your_key" \
-H "Content-Type: application/json" \
-d '{
"tool": "create_itinerary",
"arguments": {
"destination": "Tokyo, Japan",
"days": 5
}
}'
```
Full API docs at [plantrip.io/developers](https://plantrip.io/developers).
## Rate Limits
- 60 requests/minute
- 10,000 requests/day
## Links
- [Plantrip](https://plantrip.io)
- [Developer Portal & API Docs](https://plantrip.io/developers)
- [Get API Key](https://plantrip.io/developers#keys)
## License
MIT
TDQS
Scored across 14 tools
Each tool targets a distinct combination of resource and action: itinerary creation/retrieval/modification/status, user trip management, packing, expert Q&A, weather, cost, guides, and tour availability/inquiry. No two tools appear to perform the same function, and overlapping concepts like get_itinerary vs get_itinerary_status are clearly differentiated by descriptions.
All tools follow a consistent verb_noun pattern in snake_case: create_itinerary, get_weather_insights, submit_tour_inquiry, etc. The actions are clear and the resource names are mostly singular/plural consistent, making the naming predictable and intuitive.
14 tools is well within the ideal 3-15 range for a travel planning server. Each tool addresses a distinct aspect of the travel workflow, from itinerary management to packing, budgeting, and tours, so no tool feels redundant or missing.
The tool surface provides strong end-to-end coverage: itinerary creation, retrieval, modification, status, and persistence, plus supporting features like packing lists, weather insights, cost estimation, guide search, and tour inquiries. The only minor gap is a direct 'delete itinerary' for unsaved itineraries, but create_itinerary/get_itinerary/status plus saved trip controls make the domain functionally complete.