RideDesk Developer Docs

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

Install

Remote server: your requests and data go to ridedesk.app. Claude Code: claude mcp add --transport http ridedesk-developer-docs https://ridedesk.app/api/mcp · Claude app: Settings → Connectors → Add custom connector.

What it can do

The tools this server listed when we connected to it, in its own words.

• list_docs — The available documentation topics with one-line summaries. Call first, then get_doc.
• get_doc — One documentation topic as markdown: the booking API contract, checkout, widgets, attribution, live chat, the customer portal, or the per-ac
• search_docs — Keyword search across all documentation topics. Returns matching sections with excerpts; follow up with get_doc for the full topic.
• 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,
• get_widget_snippets — Copy-paste tags: the attribution script, the live-chat script, and the embeddable booking/enquiry/rental widget iframes.

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools

• rea-changelog-update 456,474 ★
  Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified cont
• git-guardrails-claude-code 323,337 ★
  Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before t
• pr
• setup-matt-pocock-skills 323,337 ★
  Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain
• setup-pre-commit 323,337 ★
  Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use w