RideDesk Developer Docs MCP Server

by ridedesk Your server? Claim it

answering

RideDesk Developer Docs is answering right now. Last checked 5 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 31 days of history

31 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

406 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 5 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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "docs": {
      "url": "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

{
  "mcpServers": {
    "docs": {
      "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	176 ms	5 min ago

Alternatives to RideDesk Developer Docs

same job, measured the same way

PolyAccounts synthetic accounting demo

by andrewblount

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

local only

Google Docs

by pulsemcp

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

82 installs/wk local only

Smarter Weather Developer Onboarding

by smarterweather

Agent-first onboarding to Smarter Weather: plans, docs, signup, API keys, MCP config, billing.

51 installs/wk 3 tools answering

IMBA Agent Docs

by imbawallet

Read-only IMBA Agent API docs MCP. No register, deposit, buy, or withdraw.

72 installs/wk 6 tools answering

MCP Persona

by codespar

MCP server for Persona — developer-first identity verification + KYC (inquiries, accounts, reports)

35 installs/wk local only

ADITUS Developer Portal MCP

by aditus-developers

Read-only docs for the ADITUS event-technology APIs (ticketing, access, BI) and Shop Micro Frontend.

5 tools answering

.NET MCP Server

by jongalloway

AI assistant access to .NET SDK for projects, packages, building, testing, and development tools.

local only

Ausca

by ausca

Pay-per-call APIs and MCP services for agents, no accounts or keys, with verifiable receipts.

86 installs/wk 14 tools answering

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 92 of 92 checks got a reply (100.0%), average response time 406 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 with the file path 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 406 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.