A quick demo might save your team weeks of engineering work.
Resources
Free Tools
Paste one prompt into Claude Code, Cursor, or your agent and it installs itself. Your agent then pulls Trip.com data from plain-English prompts. Same API key, same billing as the REST API.
Trusted by hospitality teams at
Whatever you'd ask a junior analyst about a hotel, ask your agent. No syntax to learn.
Find Shanghai hotels for my stay and compare the source stay totals, including taxes when available.
What do guests say about Trip.com hotel 702258?
Summarize the most recent Trip.com reviews for hotel 702258 and flag anything negative.
Group the Trip.com reviews for hotel 702258 by travel type and room type.
Show which Trip.com reviews for hotel 702258 got a reply from the property.
Real examples. You ask, the agent picks a tool and fills the parameters, you read the answer. These outputs are illustrative.
What do guests say about Trip.com hotel 702258?
tripcom_hotel_reviews(hotel_id="702258", page=1, page_size=10)
The most recent Trip.com reviews for that hotel with their ratings and stay dates, read back as a short summary instead of a raw list.
Group the Trip.com reviews for hotel 702258 by travel type and room type.
tripcom_hotel_reviews(hotel_id="702258", page_size=20)
The same reviews split by the travel type each guest picked and the room they booked, so a pattern in one segment stands out.
Show which Trip.com reviews for hotel 702258 got a reply from the property.
tripcom_hotel_reviews(hotel_id="702258", page=1)
The reviews that carry an owner response, paired with the reply and its date, so anything still unanswered is easy to spot.
Copy the prompt into the agent you already have open. It reads our setup page and wires up the connector itself.
Paste into Claude Code
Read https://stayapi.com/install and set up the StayAPI MCP server for me.
Then open a new session and run claude mcp list — stayapi should read ✓ Connected.
Add to Cursor in one click
Installs with a YOUR_API_KEY placeholder you swap in Cursor.
Paste into Cursor's chat
Read https://stayapi.com/install and set up the StayAPI MCP server for me.
The agent writes ~/.cursor/mcp.json, then asks you to restart Cursor.
Paste into Codex
Read https://stayapi.com/install and set up the StayAPI MCP server for me.
Codex reads the page and writes its own MCP config.
Paste into your agent
Read https://stayapi.com/install and set up the StayAPI MCP server for me.
Gemini CLI, Windsurf, or anything else that speaks MCP — the agent adds a remote HTTP server with the X-API-Key header to that client's own config.
No key yet? Sign up for 50 free requests — the agent asks you for it.
Claude on the web, desktop, or mobile doesn't need this prompt: add StayAPI under Settings → Connectors and sign in. ChatGPT: add it as an MCP app in developer mode and sign in. Other clients: manual setup below.
Add StayAPI as a connector and sign in. Nothing to paste.
StayAPI and set the URL to https://api.stayapi.com/mcp.Add StayAPI as an MCP app and sign in. Plus, Pro, Business, Enterprise, or Edu, on the web.
chatgpt.com/plugins, click +, and choose Create MCP app.StayAPI, set the URL to https://api.stayapi.com/mcp, and pick OAuth. Leave the client ID and secret blank.@StayAPI and ask.One terminal command.
claude mcp add --scope user --transport http stayapi https://api.stayapi.com/mcp --header "X-API-Key: YOUR_API_KEY"
claude mcp list.Edit ~/.cursor/mcp.json.
{
"mcpServers": {
"stayapi": {
"type": "http",
"url": "https://api.stayapi.com/mcp",
"headers": { "X-API-Key": "YOUR_API_KEY" }
}
}
}
YOUR_API_KEY, save.Edit claude_desktop_config.json.
{
"mcpServers": {
"stayapi": {
"command": "npx",
"args": [
"-y", "mcp-remote@0.1.18",
"https://api.stayapi.com/mcp",
"--header", "X-API-Key:YOUR_API_KEY"
]
}
}
}
On Windows, a bare npx can fail with spawn npx ENOENT. Use the absolute path to npx.cmd. Windows setup notes →
Full reference — every tool, error shapes, Windows notes: MCP documentation →
Most agents pick the right tool from your prompt, so you never name it. One tool call counts as one request, the same as a REST request.
tripcom_search_hotels
Search by Trip.com city_id and required check_in/check_out. Optional hotel_name requests native name matching within the required city/stay (trimmed 1–200 characters; no controls); response hotel_name is a nullable normalized keyword. First page only, limit 1–20 (default 10). Advertised price basis and tax inclusion are unspecified; quoted payment totals can exclude charges due at the property. Retain labels and notes; search does not guarantee bookability. Selected-room metadata and source labels describe one offer, not full inventory or capacity.
tripcom_hotel_reviews
Get paginated reviews served by Trip.com, with per-review source: tripcom, ctrip, expedia, hotelscom, tripadvisor, or unknown. Includes ratings, text, stay dates and owner responses. Aggregate Expedia counts do not identify review origin; token and signature fields are excluded. total_reviews is the hotel aggregate; pageable_reviews is the current feed count, not a promise that all aggregate rows are retrievable. page_size is 1 to 50, default 10.
Full parameters and response shapes live in the MCP docs. For the same data over REST, see the Trip.com API hub.
Sign up, paste one prompt, let your agent install itself. Both paths end with your agent answering Trip.com questions in plain English.
50 free requests on signup. Paste one prompt into your agent, then start asking it for Trip.com data.
Start free Read the MCP docs15 minutes. We screen-share and wire Claude or Cursor to your real properties. Free of charge.
Book a demo