DSP Booking MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DSP_OAUTH_CLIENT_ID | Yes | The OAuth client ID for DSP authentication | |
| DSP_OAUTH_TOKEN_URL | Yes | The OAuth token URL for DSP authentication | |
| DSP_BOOKING_BASE_URL | Yes | The base URL for DSP booking API | |
| DSP_BOOKING_API_VERSION | Yes | The API version for DSP booking | |
| DSP_OAUTH_CLIENT_SECRET | Yes | The OAuth client secret for DSP authentication | |
| DSP_APIM_SUBSCRIPTION_KEY | Yes | The subscription key for DSP APIM |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| initialize_booking_sessionA | Initialize a new booking session. |
| search_flightsA | Perform a flight search based on search criteria. This operation required 'initialize_booking_session' to be exexcuted first to start the session. |
| create_cartA | Create a shopping cart with selected flight options. PREREQUISITES: Must call 'initialize_booking_session' first, then 'search_flights' to get available flight options. This endpoint adds the customer's selected flights (identified by airBoundIds from search results) to a cart for booking. The cart validates selections, checks availability, and calculates final pricing. WORKFLOW POSITION: Step 3 of the booking flow (after initialization and search, before passenger details and payment). RESPONSE: Returns a cartId which is required for subsequent booking operations. IMPORTANT: All airBoundIds must come from the most recent search_flights response within the same session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| generate-itinerary | Create a detailed travel itinerary for supported destinations with required closing phrase |
| unsupported-route-response | Generate standardized response for unsupported route requests with exact business messaging |
| supported-route-confirmed | Confirm route is supported and transition to itinerary planning |
| booking-transition | Handle transition from itinerary to flight booking when user shows booking intent |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| supported-routes | All flight routes currently operated by Malaysia Airlines |
| route-check | Check if a specific route is supported by Malaysia Airlines |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/hrz8/mcp-openapi'
If you have feedback or need assistance with the MCP directory API, please join our Discord server