MCP integration
YSystem Open Platform provides a standard MCP Streamable HTTP service at:
POST /services/mcp
After obtaining an OAuth 2.1 access token, send it in the request header:
Authorization: Bearer <access-token>
Content-Type: application/json
The server uses the token scopes to determine which tools are visible in the session. Unauthorized tools are omitted from the tools/list response.
Public tools
| Tool | OAuth scope | Purpose |
|---|---|---|
hotel_meta_search |
mcp:hotel.meta.search |
Search hotel metadata without stay dates, live prices, or availability |
hotel_search |
mcp:hotel.search |
Search hotels |
hotel_rates |
mcp:hotel.rates |
Query rooms and rate plans |
hotel_rateRule |
mcp:hotel.rate-rule |
Query a rate plan and its rules |
order_search |
mcp:order.search |
Query order details |
Existing tokens must be reauthorized for mcp:hotel.meta.search before the new tool appears in tools/list.
Statistics, summaries, and trend analysis are controlled capabilities and are not part of the public tool list. Contact the platform to enable the required capability for an account.
Tool selection
- Use
hotel_meta_searchfor hotel metadata without stay dates; usehotel_searchwhen live prices are needed. - Use the rate and order tools for specific detail queries.
- Use platform-provided analysis tools for statistics, summaries, trends, and comparisons.
- The MCP session is bound to the user and channel in the OAuth token. Channel headers do not change that binding.
Protocol discovery
MCP clients that support OAuth discovery can read:
GET /.well-known/oauth-protected-resource/services/mcp
The authorization server metadata is available at:
GET /.well-known/oauth-authorization-server
See MCP OAuth authorization for the authorization flow.