Skip to main content
Glama
deenesjakoruzh
nxGnosis

Travel Agent MCP Server

by nxGnosis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

TravelAgentMCP 🌍✈️

Un monorepo de servidores MCP (Model Context Protocol) para la plataforma TVA OTA: búsqueda y reserva de vuelos y hoteles, requisitos de visado e inmigración y seguimiento de reservas, y gestión de cuentas de usuario — creado para agentes de viaje con IA.

Arquitectura

TravelAgentMCP/
├── mcps/
│   ├── shared/            @travelagent-mcp/shared — HTTP client, config, guardrails, tool helper (not a server)
│   ├── flight-mcp/        tva-flight-mcp   — search, pricing, seatmaps, booking lifecycle
│   ├── hotel-mcp/         tva-hotel-mcp    — search, availability, booking lifecycle
│   ├── visa-mcp/          tva-visa-mcp     — country requirements + booking tracking
│   ├── immigration-mcp/   tva-immigration-mcp — service info + booking tracking
│   └── account-mcp/       tva-account-mcp  — auth, profile, promo codes, notifications
└── src/index.ts           travelagent-mcp  — gateway that mounts all five servers' tools in one process

Cada paquete mcps/* es un servidor MCP stdio ejecutable de forma independiente con su propio bin. Ejecuta los que necesites (p. ej., solo tva-flight-mcp + tva-hotel-mcp para un widget de reservas, o solo tva-visa-mcp + tva-immigration-mcp para un bot de asesoramiento), o ejecuta el gateway raíz (travelagent-mcp) para tenerlo todo en un solo proceso — así ha sido siempre el paquete npm publicado, mantenido por compatibilidad hacia atrás.

Una API de origen, dos modos de autenticación:

  • Backend TVA OTA (TVA_BASE_URL) — vuelos, hoteles, reservas, cuenta y el lado "cliente" del seguimiento de reservas de visado/inmigración (actualizaciones, notificaciones, transacciones). La mayoría de los endpoints de gestión de reservas requieren un bearer token; los flujos de pago como invitado (book, cancel-by-UUID, verify, resend-ticket) no.

  • Contenido de visado/inmigración (misma TVA_BASE_URL, autenticado mediante CONTENT_API_KEY en lugar de un bearer token) — requisitos por país, tipos de visado, tasas y preguntas frecuentes, utilizado únicamente por GET_VISA_INFO_BY_COUNTRY / GET_IMMIGRATION_INFO_BY_COUNTRY.

Related MCP server: orizn-visa-mcp

Salvaguardas

  • Mínimo privilegio: solo se exponen endpoints orientados al usuario. Los endpoints de administración/operaciones (gestión de reservas, reembolsos, estadísticas de ingresos) deliberadamente no se exponen como herramientas — no son apropiados para un agente conversacional.

  • Confirmación explícita: toda herramienta que mueve dinero o es irreversible (BOOK_FLIGHT, BOOK_HOTEL, CANCEL_FLIGHT_BOOKING, CANCEL_HOTEL_BOOKING, CONFIRM_FLIGHT_PAYMENT, CONFIRM_HOTEL_PAYMENT, SELECT_FLIGHT_SEAT, CHANGE_PASSWORD, CLOSE_ACCOUNT) requiere confirm: true, que el agente llamante solo debe establecer después de leer al usuario los detalles específicos.

  • Sin secretos en el contexto del LLM: TVA_ACCESS_TOKEN nunca es un parámetro de herramienta — se lee del entorno del proceso, inyectado por sesión de usuario por cualquier agente que lance estos servidores. LOGIN_USER / SOCIAL_AUTH_LOGIN devuelven el token envuelto en un sobre __session para que el agente que lo lanza lo intercepte y lo almacene fuera de banda; el modelo solo ve un mensaje de confirmación simple. Consulta mcps/account-mcp/src/lib/session.ts para el contrato.

  • Sin repetición de ofertas en bruto: las ofertas de vuelo de Amadeus son grandes blobs JSON opacos. SEARCH_FLIGHTS almacena en caché cada oferta en el servidor (SQLite, consulta mcps/flight-mcp/src/lib/offerCache.ts) y entrega al modelo un offerRef corto en su lugar — el modelo nunca reconstruye el JSON de la oferta manualmente, lo que podría provocar un aumento excesivo de tokens o una corrupción silenciosa de precios/tarifas.

  • Redacción: las contraseñas, tokens, OTPs y números de tarjeta se enmascaran antes de registrar cualquier cosa (consulta mcps/shared/src/guardrails.ts).

  • Riesgo conocido — pagos de hotel: BOOK_HOTEL actualmente toma los datos de la tarjeta directamente (la API de hoteles de TVA aún no tiene un paso de pago tokenizado). Solo debe llamarlo un cliente que haya recopilado los datos de la tarjeta a través de una superficie segura y compatible con PCI — nunca pidiendo al usuario que escriba un número de tarjeta en el chat. Consulta la descripción de la herramienta para más detalles.

  • Limitación de tasa: cada llamada a herramienta se limita por proceso (defensa contra un bucle descontrolado de llamadas a funciones). Esto no sustituye una limitación persistente entre turnos — rastrea el abuso de forma persistente en la capa de sesión si necesitas protección real.

Configuración

pnpm install
cp .env.example .env   # fill in TVA_BASE_URL and content-API keys
pnpm build              # builds mcps/shared first, then every domain server, then the gateway

Ejecuta el gateway (todas las herramientas en un solo proceso):

pnpm start

O ejecuta un servidor de un solo dominio directamente:

node mcps/flight-mcp/dist/index.js

Referencia de herramientas

Vuelo (tva-flight-mcp)

SEARCH_FLIGHTS, GET_POPULAR_FLIGHT_ROUTES, GET_FLIGHT_PRICE_ANALYSIS, GET_MOST_TRAVELED_DESTINATIONS, GET_MOST_BOOKED_DESTINATIONS, GET_BUSIEST_TRAVEL_PERIOD, GET_FLIGHT_SEATMAP_BY_OFFER, GET_FLIGHT_SEATMAP_BY_ORDER, GET_FLIGHT_FARE_UPSELL, PREDICT_FLIGHT_CHOICE, CONFIRM_FLIGHT_PRICE, BOOK_FLIGHT, LIST_MY_FLIGHT_BOOKINGS, GET_FLIGHT_BOOKING, VERIFY_FLIGHT_BOOKING, CANCEL_FLIGHT_BOOKING, GET_FLIGHT_SEAT_PRICE, SELECT_FLIGHT_SEAT, RESEND_FLIGHT_TICKET, GET_FLIGHT_TICKET_DOWNLOAD_LINK, CONFIRM_FLIGHT_PAYMENT

Hotel (tva-hotel-mcp)

SEARCH_HOTELS, SEARCH_HOTEL_CITIES, CHECK_HOTEL_AVAILABILITY, BOOK_HOTEL, LIST_MY_HOTEL_BOOKINGS, GET_HOTEL_BOOKING, CONFIRM_HOTEL_PAYMENT, CANCEL_HOTEL_BOOKING

Visa (tva-visa-mcp)

GET_VISA_INFO_BY_COUNTRY, LIST_MY_VISA_BOOKINGS, GET_VISA_BOOKING, GET_VISA_BOOKING_BY_APPLICATION_UUID, GET_VISA_UPDATES, GET_VISA_UPDATES_BY_BOOKING, GET_VISA_FOLLOWUP_QUESTIONS, ANSWER_VISA_FOLLOWUP, GET_VISA_NOTIFICATIONS, MARK_VISA_NOTIFICATION_READ, GET_VISA_TRANSACTIONS, GET_VISA_TRANSACTION_DETAIL

Inmigración (tva-immigration-mcp)

GET_IMMIGRATION_INFO_BY_COUNTRY, LIST_MY_IMMIGRATION_BOOKINGS, GET_IMMIGRATION_BOOKING, GET_IMMIGRATION_UPDATES, GET_IMMIGRATION_UPDATES_BY_BOOKING, GET_IMMIGRATION_NOTIFICATIONS, MARK_IMMIGRATION_NOTIFICATION_READ, GET_IMMIGRATION_TRANSACTIONS, GET_IMMIGRATION_TRANSACTION_DETAIL

Cuenta (tva-account-mcp)

REGISTER_USER, LOGIN_USER, SOCIAL_AUTH_LOGIN, FORGOT_PASSWORD, RESEND_OTP, VERIFY_OTP, LOGOUT_USER, GET_CURRENT_USER, GET_USER_PROFILE, EDIT_USER_PROFILE, CHANGE_PASSWORD, CHECK_DISCOUNT_PROMO, GET_USER_NOTIFICATIONS, CLOSE_ACCOUNT

Usado por

El agente de viajes NomadSage de MegaMind lanza estos servidores (vía stdio, uno por dominio) junto con sus herramientas de búsqueda en la base de conocimiento y de respuesta de social-mcp — consulta travel-agent/src/lib/tva-client.ts y travel-agent/src/lib/tva-session.ts en ese repositorio.

Available Tools

2 tools
GET_IMMIGRATION_INFO_BY_COUNTRYC

Get immigration information for a specific country.

NameRequiredDescriptionDefault
countryCodeYes

TDQS

C2.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It states 'Get' which implies a read-only operation, but does not disclose any behavioral traits such as rate limits, authentication needs, data freshness, or error handling. This is a significant gap for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no wasted words. It is appropriately sized and front-loaded, efficiently conveying the core purpose without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of immigration information, lack of annotations, no output schema, and low schema coverage, the description is incomplete. It does not address what type of information is returned, potential limitations, or how it differs from the sibling tool, leaving the agent with insufficient context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, and the description does not add any meaning beyond the schema. It mentions 'specific country' but does not explain the 'countryCode' parameter's format, valid values, or semantics, failing to compensate for the low schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'immigration information for a specific country', making the purpose understandable. However, it does not explicitly differentiate from its sibling tool GET_VISA_INFO_BY_COUNTRY, which likely provides overlapping or related information, so it misses the highest score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus its sibling GET_VISA_INFO_BY_COUNTRY, nor does it mention any prerequisites or alternative contexts. It lacks explicit usage instructions, leaving the agent to infer based on tool names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GET_VISA_INFO_BY_COUNTRYC

Get visa information for a specific country.

NameRequiredDescriptionDefault
countryCodeYes
currencyCodeNo

TDQS

C2.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure but only states the basic action without details on permissions, rate limits, error handling, or response format. It doesn't add meaningful context beyond the minimal purpose, failing to compensate for the lack of structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no wasted words, making it highly concise and front-loaded. It efficiently communicates the core purpose without unnecessary elaboration, earning full marks for brevity and structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (2 parameters, no output schema, and no annotations), the description is insufficient. It lacks details on parameter usage, behavioral traits, and output expectations, making it incomplete for effective agent operation despite the concise structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, and the description doesn't mention any parameters or their meanings. It fails to explain what 'countryCode' and 'currencyCode' represent, their expected formats, or how they influence the output, leaving both parameters undocumented and adding no value beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('visa information for a specific country'), making it immediately understandable. However, it doesn't explicitly differentiate from its sibling tool 'GET_IMMIGRATION_INFO_BY_COUNTRY', which likely covers related but distinct information, preventing a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus its sibling 'GET_IMMIGRATION_INFO_BY_COUNTRY', nor does it mention any prerequisites, alternatives, or exclusions. It only states what the tool does, leaving the agent to infer usage context without explicit direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

  1. 2 tool updates
    • First observedGET_IMMIGRATION_INFO_BY_COUNTRY
    • First observedGET_VISA_INFO_BY_COUNTRY
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

C2.8/5.0

Scored across 2 tools

Disambiguation2/5

The two tools have unclear boundaries and significant overlap. 'Immigration information' and 'visa information' are closely related concepts in travel, and their descriptions do not clearly differentiate what each tool provides, leading to potential confusion for an agent trying to select the right one.

Naming Consistency5/5

The tool names follow a consistent pattern of uppercase snake_case with a clear 'GET_<domain>_BY_COUNTRY' structure. Both tools use the same verb ('GET') and format, making them predictable and easy to parse.

Tool Count2/5

With only 2 tools, the server feels thin for a 'Travel Agent' domain, which typically involves broader functionality like booking flights, hotels, or checking travel advisories. The limited scope suggests an incomplete or overly narrow implementation.

Completeness2/5

The server is severely incomplete for a travel agent purpose. It lacks core travel operations such as searching for flights, booking accommodations, checking weather, or providing general travel tips, leaving obvious gaps that will hinder agent workflows.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches