RideDesk Developer Docs MCP Server

by ridedesk Your server? Claim it

answering

RideDesk Developer Docs is answering right now. Last checked 13 min ago. It exposes 5 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 81 days of history · worst day 93%

81 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

747 ms

Response time

average over 24h

open, no key

Access

streamable-http

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add docs --transport http https://ridedesk.app/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://ridedesk.app/api/mcp

~/.codex/config.toml

[mcp_servers.docs]
url = "https://ridedesk.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "docs": {
      "url": "https://ridedesk.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "docs": {
      "type": "http",
      "url": "https://ridedesk.app/api/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

docs

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.

doc

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.

integration

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.

widget

get_widget_snippets

Copy-paste tags: the attribution script, the live-chat script, and the embeddable booking/enquiry/rental widget iframes.

Endpoints

URL	Transport	State	Latency	Checked
https://ridedesk.app/api/mcp	streamable-http	answering	170 ms	13 min ago

Alternatives to RideDesk Developer Docs

same job, measured the same way

SearchPipe

by searchpipe

Web search API and MCP server for developers building AI agents.

3 tools answering

OwnSERP

by devops-infinity

MCP server for the Serper.dev search API with per-call credit accounting

1 096 installs/wk local only

Sorted Travel Docs

by sorted

Search Sorted Travel developer docs for MCP, API, SDK, and auth questions.

3 tools answering

Spree Commerce developer docs for AI agents

by spree

Spree Commerce docs for AI coding agents: build headless B2B and marketplace ecommerce on its APIs.

3 tools answering

PolyAccounts synthetic accounting demo

by andrewblount

Synthetic accounting MCP demo with exact balances and ledger evidence. No account or API key.

local only

FaxFair

by nico02138-ops

Fax API and MCP server for AI agents. Fax US and Canada, pay per request with x402. No account.

3 tools answering

Google Docs

by pulsemcp

MCP server for Google Docs integration with OAuth2 and service account support.

78 installs/wk local only

ForgeBridge

by t1ktakdev

A local, permissioned MCP agent for authorized developer workstations.

41 installs/wk local only

RideDesk Developer Docs — questions

Answers built from our own checks of this server.

What can RideDesk Developer Docs do?

It exposes 5 tools, read directly from the server on our last check. Among them: get_doc, get_integration_brief, get_widget_snippets, list_docs, search_docs. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is RideDesk Developer Docs working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 747 ms. The bar chart above shows every period we have measured.

Is RideDesk Developer Docs still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect RideDesk Developer Docs?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does RideDesk Developer Docs need an API key?

No. RideDesk Developer Docs completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is RideDesk Developer Docs?

It answers our handshake in 747 ms on average, which is faster than 11% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.