Provides DSP Booking MCP access via stdio, HTTP, or Docker for end-to-end DSP booking flows.
Configuration
View docs{
"mcpServers": {
"hrz8-mcp-openapi": {
"url": "http://localhost:3067/mcp",
"headers": {
"DSP_OAUTH_CLIENT_ID": "xxx",
"DSP_OAUTH_TOKEN_URL": "https://example.com/security/oauth2/token",
"DSP_BOOKING_BASE_URL": "https://example.com/booking",
"DSP_BOOKING_API_VERSION": "v1",
"DSP_OAUTH_CLIENT_SECRET": "xxx",
"DSP_APIM_SUBSCRIPTION_KEY": "xxx"
}
}
}
}You can run DSP MCP Server as an MCP endpoint to handle DSP Booking flows through your MCP client. It supports local stdio execution, HTTP transport for local or remote access, and Docker-based deployment. This guide walks you through using the server, installing it, and managing configurations so you can start booking requests end-to-end.
Connect your MCP client to the server using one of the available MCP connection methods. You can run a local stdio server that launches the DSP MCP Server directly, expose the server over HTTP for local or remote access, or run a Docker container for deployment. When connected, your client can perform booking-related operations through the DSP MCP Server and receive responses through the chosen transport.
Prerequisites you need on your machine: a supported Node.js runtime, a package manager (pnpm or npm), and Docker if you plan to run the Docker variant.
# Install dependencies and build if needed
pnpm install
pnpm run build
# Start the server using the local stdio flow (Node)
posix
```,Configuration and deployment options are available for multiple environments. You can run a local Node-based stdio server, a local HTTP server accessible at a specific port, or a Dockerized variant with environment variables injected at runtime. Each option is designed to integrate with Claude or other MCP clients through the standard MCP protocol.