Developer docs for building on RideDesk: booking API, widgets, per-account booking MCP. No auth.
Connect Remote server
claude mcp add --transport http docs https://ridedesk.app/api/mcp
{
"mcpServers": {
"docs": {
"url": "https://ridedesk.app/api/mcp"
}
}
}
{
"servers": {
"docs": {
"type": "http",
"url": "https://ridedesk.app/api/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://ridedesk.app/api/mcp
Tools 5 found in our last check
list_docsThe available documentation topics with one-line summaries. Call first, then get_doc.
get_docOne documentation topic as markdown: the booking API contract, checkout, widgets, attribution, live chat, the customer portal, or the per-account booking MCP server.
search_docsKeyword search across all documentation topics. Returns matching sections with excerpts; follow up with get_doc for the full topic.
get_integration_briefA self-contained brief for a coding agent building a transfer-booking website on the RideDesk API — the flow, the rules the server enforces, and the acceptance criteria.
get_widget_snippetsCopy-paste tags: the attribution script, the live-chat script, and the embeddable booking/enquiry/rental widget iframes.
Details
| Endpoint | https://ridedesk.app/api/mcp (Streamable HTTP) |
| First published | 19 Aug 2026 |
| Last updated | 19 Aug 2026 |
| Registry name | app.ridedesk/docs |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
