Hopper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_flightsA | Search for available flights on Hopper with real-time pricing and AI-powered price predictions. Returns flight options with buy/wait/watch recommendations. |
| search_hotelsB | Search for hotels on Hopper with price predictions. Returns hotel options with ratings, amenities, and Hopper's buy/wait recommendation. |
| get_price_forecastA | Get Hopper's AI price forecast for a flight or hotel. Returns whether to buy now, wait for lower prices, or watch for changes — with confidence percentage and reasoning. |
| set_price_alertA | Create a price drop alert for a flight or hotel. Hopper will notify via the app/email when prices hit your target or when the optimal booking window opens. |
| book_flightA | Initiate a flight booking on Hopper for a specific flight. Requires passenger details and payment information. Returns booking confirmation or authentication requirements. |
| book_hotelA | Initiate a hotel booking on Hopper. Requires guest details and payment information. Hopper's Price Drop Guarantee refunds the difference if prices fall post-booking. |
| get_bookingsA | View current and past bookings from a Hopper account. Returns flight and hotel booking history with status, itinerary details, and pricing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a distinct purpose: booking flights/hotels, retrieving bookings, forecasting prices, searching flights/hotels, and setting alerts. No overlap exists; for example, search_flights and book_flight are clearly separate operations, and get_price_forecast focuses on predictions rather than actions.
All tool names follow a consistent verb_noun pattern (e.g., book_flight, search_hotels, set_price_alert). The verbs are descriptive and aligned with the actions, and there are no deviations in style or convention across the set.
With 7 tools, the server is well-scoped for travel booking and price management. Each tool serves a clear function in the workflow, from search and forecast to booking and alerts, without being overly sparse or bloated.
The tool set provides complete coverage for the travel booking domain: search (flights/hotels), forecast (prices), booking (flights/hotels), management (view bookings), and alerts (price drops). No obvious gaps exist, as it supports the full lifecycle from research to post-booking monitoring.