What is MCP Server
RideClaw MCP Server exposes travel search, pricing and booking capabilities as structured tools that AI assistants can call. Compatible with any client that speaks the Model Context Protocol (MCP), including Claude Desktop, IDE plugins, and custom agent frameworks.
Available tools
The server provides 9 read-only tools for searching and planning. Write operations (creating orders, payment, cancellation) require explicit user confirmation and are not exposed as auto-callable tools.
Setup for Claude Desktop
Add RideClaw to your Claude Desktop MCP configuration. The server will authenticate using your API key and expose travel tools directly in the chat interface.
// claude_desktop_config.json
{
"mcpServers": {
"rideclaw": {
"command": "curl",
"args": [
"-X", "POST",
"https://open.longxiachuxing.com/api/open/v1/mcp",
"-H", "Authorization: Bearer YOUR_API_KEY",
"-H", "Content-Type: application/json",
"-d", "@-"
]
}
}
}Setup for custom agents
Point your MCP client to the RideClaw endpoint and authenticate with your API key. The endpoint accepts standard JSON requests and can also stream responses for real-time progress.
POST https://open.longxiachuxing.com/api/open/v1/mcp
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Accept: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list"
}Example queries
Once connected, your AI assistant can handle travel queries in natural language. The MCP server translates these into structured API calls and returns results the assistant can work with.
Safety and validation
All booking-related operations require explicit user confirmation. The MCP server only exposes read-only search and pricing tools — agents cannot create orders or process payments without your approval flow.