Developer · Remote MCP server

RideDesk Developer Docs

Developer docs for building on RideDesk: booking API, widgets, per-account booking MCP. No auth.

Visit RideDesk Developer Docs's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
app.ridedesk/docs
Version
1.0.3
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-08-19
Updated
2026-08-19
Publisher
app.ridedesk · 2 servers with pages here
Namespace
Namespace verified by the MCP Registry via the domain ridedesk.app · how
Website
ridedesk.app/developers
Repository
github.com/ridedeskapp/ridedesk
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://ridedesk.app/api/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
RideDesk developer docs 1.0.0 · protocol 2025-06-18
Tools discovered
5: list_docs, get_doc, search_docs, get_integration_brief, get_widget_snippets
Checked on
2026-10-05

How the live check works

How to connect RideDesk Developer Docs

RideDesk Developer Docs is a remote MCP server: there is nothing to install. Its endpoint is https://ridedesk.app/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

Site checks

The website's own root, ridedesk.app, was checked for the files that tell AI systems about a site.

FileResult
/llms.txtReal file, HTTP 200 · 2026-10-04
/.well-known/mcp.jsonNo real file found
/.well-known/ai-plugin.jsonNo real file found
/agents.jsonNo real file found

More from app.ridedesk

All 2 →
ServerRunsEndpoint or package
RideDesk BookingsQuote and book airport transfers on a RideDesk operator's live desk. Agents never set prices.Remote · HTTPx

More developer servers

All 5,152 →
ServerRunsEndpoint or package
ReviewGuardSafety boundary for agent written GitHub PR reviews: pending and invisible, submitting is opt-in.Local · stdionpm: @eclipsesource/review-guard-mcp
RFixCreate RF signal projects from prompts, inspect graphs, and export IQ data.Remote · HTTPLive check: ✓ handshakemcp.rfix.ai
RFP.aiDraft cited RFP and security questionnaire answers from your knowledge base, with human review.Remote · HTTPLive check: sign-in requiredrfp.ai
RheaRhea MCP - expert-curated database of biochemical reactions.Remote · HTTPLive check: ✓ handshakegateway.pipeworx.io
Rigor MCPVerified statistical inference for AI agents: hypothesis tests, sequential testing, power.Local · stdioPyPI: rigor-mcp
RigourQuality gates for AI agents. Lint, test, build checks with memory persistence.Local · stdionpm: @rigour-labs/mcp
RIPE AtlasRIPE Atlas network measurements - ping, traceroute, DNS, TLS, HTTP, NTP, and probes.Local · stdionpm: ripe-atlas-mcp-server
RiskRover MCPDraft risk-based test plans and assess automated test coverage against product risks with RiskRover.Local · stdionpm: riskrover-mcp-server