Skip to main content
Glama
DSP Booking MCP Server

DSP Booking MCP Server

by hrz8

DSP-MCP

PoC for DSP Booking flow through MCP Server.

MCP Config stdio

$ pnpm run build
{
  // use `mcpServers` for Claude
  "servers": {
    "dsp-server": {
      "type": "stdio", // no need in claude_desktop_config.json
      "command": "node",
      "args": ["~/dsp-mcpserver/dist/index.js"],
      "env": {
        "DSP_BOOKING_BASE_URL": "https://example.com/booking",
        "DSP_BOOKING_API_VERSION": "v1",
        "DSP_APIM_SUBSCRIPTION_KEY": "xxx",
        "DSP_OAUTH_CLIENT_ID": "xxx",
        "DSP_OAUTH_CLIENT_SECRET": "xxx",
        "DSP_OAUTH_TOKEN_URL": "https://example.com/security/oauth2/token"
      }
    }
  }
}

Related MCP server: Google Ad Manager MCP Server

MCP Config HTTP VSCode (Able to start locally or even MCP Remote)

Using VSCode Agent we are able to use local MCP Remote or even public MCP Remote

$ pnpm run build
$ pnpm run start --transport http --port 3067
# OR Docker
$ docker-compose up --build -d
{
  // use `mcpServers` for Claude
  "servers": {
    "dsp-server": {
      "type": "http",
      "url": "http://localhost:3067/mcp" // or https://your-host.or.lambda.url/mcp if publicly accessibile
    }
  }
}

MCP Config HTTP Claude Desktop (Required HTTPS)

Make sure you have deploy the server to the public-accessible endpoint e.g., https://your-host.or.lambda.url/mcp

Option 1

Use a Custom Connector settings in the Claude Settings

Name: DSP Server
Remote MCP Server URL: https://your-host.or.lambda.url/mcp

Option 2

Use mcp-remote in your claude_desktop_config.json

{
  "mcpServers": {
    "dsp-server": {
      "command": "npx",
      "args": ["mcp-remote", "https://your-host.or.lambda.url/mcp"]
    }
  }
}

MCP Config Docker

$ docker build -t dsp-mcpserver:stdio . -f Dockerfile.stdio
{
  // use `mcpServers` for Claude
  "servers": {
    "dsp-server": {
      "type": "stdio", // no need in claude_desktop_config.json
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "DSP_BOOKING_BASE_URL=https://example.com/booking",
        "-e",
        "DSP_BOOKING_API_VERSION=v1",
        "-e",
        "DSP_APIM_SUBSCRIPTION_KEY=xxx",
        "-e",
        "DSP_OAUTH_CLIENT_ID=xxx",
        "-e",
        "DSP_OAUTH_CLIENT_SECRET=xxx",
        "-e",
        "DSP_OAUTH_TOKEN_URL=https://example.com/security/oauth2/token",
        "dsp-mcpserver:stdio"
      ]
    }
  }
}

Available Tools

3 tools
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.

Inputs: session-token (required), requestBody (required).

initialize_booking_sessionA

Initialize a new booking session.

Inputs: requestBody (required).

search_flightsA

Perform a flight search based on search criteria. This operation required 'initialize_booking_session' to be exexcuted first to start the session.

Inputs: session-token (required), requestBody (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct and clear purpose: initialize_booking_session starts the session, search_flights finds available flights, and create_cart adds selected flights to a cart. There is no overlap or ambiguity in their functions, making it easy for an agent to select the right tool at each step.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (initialize_booking_session, search_flights, create_cart) with clear, descriptive verbs. There are no deviations in style or convention, ensuring predictable and readable naming throughout.

    Tool Count3/5

    With only 3 tools, the set feels thin for a booking server, as it lacks operations for passenger details, payment, or booking confirmation. While the tools cover the initial workflow steps, the count is borderline low for the apparent scope of a full booking process.

    Completeness2/5

    The tool surface is significantly incomplete for a booking domain. It includes initialization, search, and cart creation but misses critical operations like adding passenger information, processing payment, or finalizing the booking. This creates dead ends and will likely cause agent failures in completing a booking.

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      D
      maintenance
      Enables authentication and interaction with DhanHQ trading APIs through OAuth-based login flow, allowing users to manage trading operations and access market data through natural language.
      18
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage Google Ad Manager campaigns, line items, creatives, and advertisers through natural language, automating ad operations that normally require countless clicks through the UI.
      35
      58 PyPI
      20
      MIT