Skip to main content
Glama
Sign In
Travel Assistant MCP

Travel Assistant MCP

by forgemeshlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Travel Assistant MCP

No-key travel assistant for Claude Desktop, Codex-style agent workflows, Hermes, and other MCP clients. It helps agents look up airports, compare routes, explain travel timing, and build external booking links without requiring a travel API account.

Features

  • Look up airport metadata by IATA code

  • Compare alternate origin and destination airport routes

  • Explain booking windows, airport arrival timing, layovers, and seasonal travel factors

  • Build external booking links for selected routes

  • Run locally with no API key or account setup

  • Disclose commission-eligible links in tool output

Related MCP server: Travel Assistant MCP

Install

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

Claude Desktop

Add this to your Claude Desktop claude_desktop_config.json:

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

Restart Claude Desktop after saving the config, then ask Claude to plan or compare travel routes.

Codex, Hermes, and other MCP-capable agent runtimes can use the same server command:

npx -y @forgemeshlabs/travel-assistant-mcp

Local Run

npm run build
node dist/index.js

Tools

  • search_travel_options

  • get_airport_info

  • compare_routes

  • build_booking_link

  • explain_travel_timing

Public Data Boundary

This package uses generic language for provider integrations. Tool responses may include external booking links and commission-eligible links. Booking completion happens with booking partners outside this MCP server.

Available Tools

5 tools
build_booking_linkA
Read-onlyIdempotent

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.

Inputs: origin, destination, departure_date, return_date, +1 more.

compare_routesA
Read-onlyIdempotent

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.

Inputs: routes (required).

explain_travel_timingA
Read-onlyIdempotent

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.

Inputs: origin, destination.

get_airport_infoA
Read-onlyIdempotent

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.

Inputs: code (required).

search_travel_optionsA
Read-onlyIdempotent

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.

Inputs: origin (required), destination (required), departure_date, return_date, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: airport info lookup, route search, route comparison, booking link generation, and general timing advice. No overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, making them predictable and easy to understand.

    Tool Count5/5

    5 tools is well-scoped for a travel assistant server, covering essential workflows without being excessive or insufficient.

    Completeness5/5

    Given the stated read-only, no-booking scope, the tool set covers the full lifecycle from airport validation to route search, comparison, and booking link generation, with no obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Resources

    Related MCP Connectors

    Related MCP Servers