RideDesk Developer Docs is an MCP server with 5 tools an agent can call, among them get_doc, get_integration_brief, get_widget_snippets. It answers at https://ridedesk.app/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
Developer docs for building on RideDesk: booking API, widgets, per-account booking MCP. No auth.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_doc | One documentation topic as markdown: the booking API contract, checkout, widgets, attribution, live chat, the customer portal, or the per-account booking MCP server. Inputs: topic, host |
get_integration_brief | A 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. Inputs: host |
get_widget_snippets | Copy-paste tags: the attribution script, the live-chat script, and the embeddable booking/enquiry/rental widget iframes. Inputs: host |
list_docs | The available documentation topics with one-line summaries. Call first, then get_doc. |
search_docs | Keyword search across all documentation topics. Returns matching sections with excerpts; follow up with get_doc for the full topic. Inputs: query, host |
Every block below points at https://ridedesk.app/api/mcp. Pick your client and copy.
claude mcp add --transport http ridedesk-developer-docs https://ridedesk.app/api/mcp
{
"mcpServers": {
"ridedesk-developer-docs": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://ridedesk.app/api/mcp"]
}
}
}{
"mcpServers": {
"ridedesk-developer-docs": {
"url": "https://ridedesk.app/api/mcp"
}
}
}{
"servers": {
"ridedesk-developer-docs": {
"type": "http",
"url": "https://ridedesk.app/api/mcp"
}
}
}{
"context_servers": {
"ridedesk-developer-docs": {
"url": "https://ridedesk.app/api/mcp"
}
}
}{
"mcpServers": {
"ridedesk-developer-docs": {
"serverUrl": "https://ridedesk.app/api/mcp"
}
}
}{
"mcpServers": {
"ridedesk-developer-docs": {
"url": "https://ridedesk.app/api/mcp"
}
}
}name: RideDesk Developer Docs
version: 0.0.1
schema: v1
mcpServers:
- name: RideDesk Developer Docs
type: streamable-http
url: https://ridedesk.app/api/mcp{
"mcpServers": {
"ridedesk-developer-docs": {
"httpUrl": "https://ridedesk.app/api/mcp"
}
}
}{
"mcpServers": {
"ridedesk-developer-docs": {
"type": "http",
"url": "https://ridedesk.app/api/mcp"
}
}
}{
"mcpServers": {
"ridedesk-developer-docs": {
"url": "https://ridedesk.app/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fridedesk.app%2Fapi%2Fmcp&type=streamable_http&id=ridedesk-developer-docs&name=RideDesk%20Developer%20Docs
It answered our last check on 17 October 2026 in 154 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by ridedesk.app and served from ridedesk.app, the vendor's own domain: https://ridedesk.app/api/mcp.
5, as returned by the server's own tools/list on 9 September 2026: get_doc, get_integration_brief, get_widget_snippets, list_docs, search_docs.
It answered our last check on 17 October 2026 in 154 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://ridedesk.app/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: app.ridedesk. Endpoint host: ridedesk.app. ARD identifier: urn:air:app.ridedesk:mcp:docs.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.