# forgemeshlabs/travel-mcp [Health: Active]

**Category:** 🚆 Travel & Transportation  
**Repository:** https://github.com/forgemeshlabs/travel-mcp  
**GitHub Stars:** 1  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/forgemeshlabs-travel-mcp

## Description
Public travel search workflow MCP server for airport lookup, route comparison, timing guidance, and external booking links through generic travel search providers.

## Tools
Capabilities this server exposes over MCP:

- **search_travel_options** — Primary travel search workflow for one origin-destination airport pair. Use when the user wants flight/trip options for a specific route; use compare_routes for multiple routes, build_booking_link only when route details are already known, and get_airport_info only to validate one airport. Read-only, no authentication, no booking side effects. return_date is optional; omit it for one-way trips. Responses include route metadata and may include commission-eligible external booking links.
- **get_airport_info** — Look up metadata for one airport by IATA code. Use to validate or explain a single airport code before route planning; use search_travel_options for an actual trip search and compare_routes for multiple origin-destination pairs. Read-only, no authentication, no external booking links, and no booking side effects.
- **compare_routes** — Compare two or more airport route pairs side by side. Use when the user is choosing between alternate origins, destinations, or airports; use search_travel_options for one dated route and get_airport_info for a single airport lookup. Read-only, no authentication, no booking side effects. Responses may include commission-eligible external booking links for each route.
- **build_booking_link** — Generate only an external booking link for an already chosen route. Use after route details are known or after compare_routes/search_travel_options; do not use as the first step when the user still needs search guidance. Read-only, no authentication, no booking completion, and no reservation side effects. The returned link may be commission-eligible and is disclosed in output.
- **explain_travel_timing** — Explain general travel timing and logistics, including booking windows, airport arrival timing, layovers, and seasonal considerations. Use for advice questions like when to book or how early to arrive; use search_travel_options when the user wants route-specific flight search. Read-only, no authentication, no external booking link, and no booking side effects.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "travel-mcp": {
    "command": "npx",
    "args": ["-y","@forgemeshlabs/travel-assistant-mcp"]
  }
}
```

## Documentation

## What the forgemeshlabs/travel-mcp MCP server does

The forgemeshlabs/travel-mcp MCP server provides a local, no-key travel planning workflow for MCP-compatible clients. It covers airport metadata lookup, route planning, side-by-side route comparison, general timing advice, and creation of external booking links. The server does not complete reservations or create booking side effects.

Use it when an agent needs to validate an airport code, search a specific origin-destination airport pair, compare several route pairs, or answer questions about booking windows, airport arrival timing, layovers, and seasonal considerations.

## How it works

The server exposes five MCP tools:

- `search_travel_options` searches travel options for one airport pair. A return date can be supplied for a round trip; omitting it supports a one-way search. Results include route metadata and may include external booking links.
- `get_airport_info` looks up one airport using its IATA code. It is intended for validating or explaining a single airport before planning a route.
- `compare_routes` compares two or more origin-destination airport pairs. Each route may include an external booking link.
- `build_booking_link` creates a booking-partner link after the route is already selected. It should not be used as the initial planning step.
- `explain_travel_timing` provides general guidance about booking timing, airport arrival, layovers, and seasonal factors.

The forgemeshlabs/travel-mcp MCP server uses generic travel-provider language rather than requiring a configured travel API account. All listed tools are read-only from the server's perspective. External links can be commission-eligible, and that status is disclosed in tool output.

## Setup and configuration

Install the published package globally with npm:

```bash
npm install -g @forgemeshlabs/travel-assistant-mcp
```

For a client that launches MCP servers through a command, run:

```bash
npx -y @forgemeshlabs/travel-assistant-mcp
```

Claude Desktop can use the same command in its `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "travel-assistant": {
      "command": "npx",
      "args": ["-y", "@forgemeshlabs/travel-assistant-mcp"]
    }
  }
}
```

Restart Claude Desktop after changing the configuration. The README also documents a local build-and-run path using `npm run build` followed by `node dist/index.js`.

No API key, travel account, or environment variable is required according to the provided material.

## Limitations and notes

The forgemeshlabs/travel-mcp MCP server is for search, comparison, lookup, advice, and link generation. It does not finish bookings, reserve travel, or provide booking confirmation. Booking completion takes place outside the server with the linked booking partner.

Use `search_travel_options` for one dated route, `compare_routes` for multiple route pairs, and `get_airport_info` for a single airport lookup. Use `build_booking_link` only after route details are known. The server's public data boundary means provider-specific behavior is not described beyond the generic travel-search workflow.

_Full upstream README: https://allmcps.com/mcp/forgemeshlabs-travel-mcp/readme_