RideDesk MCP server
Which servers in the official MCP registry are RideDesk's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-14
- Registry nameapp.ridedesk/docsverified in the MCP registry
The registry name sits under ridedesk.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-14
- Tools5
- Server calls itselfRideDesk developer docs
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 206 ms.
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.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"docs": {
"type": "http",
"url": "https://ridedesk.app/api/mcp"
}
}
}- app.ridedesk/bookingsaddress differs per installverified in the MCP registry
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.