
Hotelbooking
io.github.DIDA-AIPublished by GitHub account DIDA-AIv1.0.0Updated Oct 25, 2026
Hotel Booking MCP Server
Overview
A hotel search and booking MCP server that lets an AI assistant find, compare, price-confirm and book hotels through Dida's travel supply chain.
- What you can do
- Search hotels by city, landmark, airport, station or address, with date, star-rating, price and radius filters, and fetch available filter tags and hotel details with room types and prices. Confirm live prices and lock a selected room type. Create bookings with a payment link and look up order lists and full order details. Set up 24-hour price monitoring with drop alerts. Return hotel names, star ratings, prices, addresses, images and facilities in Chinese or English.
- When to use it
- Useful for AI travel assistants, corporate travel tools, OTA or lifestyle agents, and demos that need a complete search-to-booking loop inside a chat. Also fits price comparison and price-watch reminder features.
- Requirements
- A Dida API key, supplied as the DIDA_API_KEY environment variable or as a Bearer token in the Authorization header. Network access to the remote hotel MCP endpoint. The README notes the API-key version is free with no call limit; the OAuth version with order tools requires business contact.
Installation
In SourceWeft
- Open Hotelbooking in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.