MCP Integration
Overview
ETERA implements the Model Context Protocol (MCP) across all four verticals, providing a standardized interface for AI models to discover and execute travel operations.
Dining search, reservations, restaurant data
Activity search, bookings, experience data
Hotel search, room booking, property data
Flight search, pricing, airline data
The Restaurant Booking service also exposes MCP endpoints directly at /restaurant/booking/mcp/*, aggregating booking-specific tools.
Core Endpoints
Every MCP service exposes the same set of endpoints:
How It Works
Advanced Operations
Service Registry
Check which backend services are registered with an MCP aggregator:
Cache Management
MCP aggregators cache tool definitions from their backend services. Force a refresh if tools have been updated:
Health Monitoring
Check the health of any MCP aggregator:
Architecture
Each MCP service acts as an aggregator that discovers tools from related microservices, caches schemas for fast lookup, and routes execution calls to the appropriate backend.
The aggregator pattern means you only need to integrate with one MCP endpoint per vertical, rather than connecting to each backend service individually.
AI Supervisor
For cross-vertical AI coordination, use the AI Supervisor at /ai/input. It automatically detects intent and routes to the appropriate vertical’s agents.
