Skip to main content
Glama
forgemeshlabs

Travel Agent MCP

by forgemeshlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Travel Agent MCP

  • Disruption Intelligence MCP

    forgemeshlabs
    A
    license
    B
    quality
    A
    maintenance
    Disruption Intelligence MCP gives AI agents access to commercial disruption signals through a public MCP server backed by the hosted Forgemesh API. It supports WARN/layoff intelligence, company context, geospatial territory disruption, x402 payment challenge inspection, and economic signal workflows without exposing private scoring logic, ingestion systems, schemas, or infrastructure.
    14
    44 npm
    1
    MIT

Related Servers

  • Travel MCP

    Erredebe
    A
    license
    Not graded
    quality
    D
    maintenance
    A comprehensive travel planning copilot that provides geographic data, weather forecasts, transportation details, currency exchange rates, and contextual content to create personalized travel experiences. Enables users to plan itineraries, check real-time conditions, and gather inspirational content for destinations.
    2 npm
    Apache 2.0

  • drift-roadbook

    tsuru0805
    F
    license
    Not graded
    quality
    B
    maintenance
    Enables an AI companion to take a small solo trip to a real, specific place, choosing its own steps over 4–10 rounds and then writing its own travelogue and picking one thing to bring home. Each journey becomes a station on a self-hosted roadbook map with coordinates, the traveler's own words, their souvenir, and a matching photo, with unfinished trips never lost and no ghostwriting by the engine.
    -

  • x402nano

    Bobjonesgood
    A
    license
    A
    quality
    B
    maintenance
    Provides free Polymarket discovery data alongside paid deep-market intelligence tools via live x402 HTTP handshakes on Base mainnet. It allows AI agents to securely settle real, ultra-low-cost USDC micro-payments (0.05 USDC) directly over the Model Context Protocol.
    4
    MIT
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.1/5.0

Scored across 14 tools

Disambiguation5/5

Each tool targets a distinct travel task: disruptions, routes, currency, booking, airport details, timing, categories, various planning scopes (day trip, weekend, weather-aware, flight route), transit, creator experiences, and local coverage. Even the multiple 'plan' tools are clearly differentiated by domain (day vs weekend vs weather vs flight). No two tools serve the same purpose.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_trip_disruptions, plan_flight_route, convert_currency). The verbs are imperative and descriptive, and there is no mixing of casing styles or unconventional naming.

Tool Count5/5

14 tools is well within the ideal 3-15 range for a travel domain server. The number is sufficient to cover a broad set of travel agent functionalities without being overwhelming or sparse. Each tool earns its place.

Completeness5/5

The tool set covers the major travel agent workflow: discovery (list_travel_categories), airport lookup (get_airport_details), route planning (plan_flight_route, compare_airport_routes), timing advice (get_travel_timing_advice), currency conversion (convert_currency), booking links (create_booking_link), disruptions (check_trip_disruptions), transit (find_transit_options), and specialized planning (day trip, weekend, weather-aware, creator experiences). There are no obvious gaps for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources