MCP Server · operational
The official Model Context Protocol server for the CDS Groupe Hotel Booking API. It exposes the booking platform as 21 typed tools any MCP-compatible assistant — Claude, ChatGPT, Cursor, Copilot — can call directly. No SDK, no integration project: connect once, then ask in plain language.
21 tools wired into one graph — the CDS network reasoning alongside your assistant, not just answering it.
RSV-8F2K; voucher attached. ✓The assistant phrases the request; the server resolves the rest — company scope, negotiated rates, availability, booking guards and payment rules — and calls the CDS API on the user's behalf.
Find hotels by destination or geo-radius, scoped to the traveller's company programme and ranked like the native portal.
Live room availability with negotiated corporate fares, board options and cancellation policies — straight from CDS.
Guarded write operations — ownership and role checks, payment-model rules and no-retry safeguards against double-booking.
Booking vouchers and documents, traveller profiles, company scope and GDS record (PNR) retrieval.
Register the server in your MCP client. The transport is Streamable HTTP — point it at the URL below:
{
"mcpServers": {
"cds": { "url": "https://mcp.cdsgroupe.com" }
}
}
Restart the client and trigger the connection. The client registers automatically and opens the sign-in page in a browser.
Choose your CDS environment and sign in with your CDS username and password. Authorization uses OAuth 2.1 with PKCE; credentials are sent only to the CDS API and never stored by this server.
The 21 tools are now exposed to the assistant — it can call them on your behalf for the duration of the session.