Developer docs for building on RideDesk: booking API, widgets, per-account booking MCP. No auth.
Scored across 5 tools
Each tool has a clearly distinct purpose: discovery via list_docs and search_docs, retrieval via get_doc, and specialized assets via get_integration_brief and get_widget_snippets. Even the overlapping discovery tools are differentiated by list versus keyword search.
All tool names follow the same snake_case verb_noun pattern: get_, list_, and search_ prefixes with clear noun targets. The naming is predictable and consistent across the entire set.
Five tools is a well-scoped size for a documentation server: two discovery tools, one general retrieval tool, and two specialized content tools. Each tool earns its place without redundancy or bloat.
The surface covers the full documentation workflow: list available topics, search across topics, fetch a full topic, and retrieve purpose-built integration assets. There are no obvious dead ends or missing operations for a read-only developer docs server.
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 (required), host.
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.
Copy-paste tags: the attribution script, the live-chat script, and the embeddable booking/enquiry/rental widget iframes.
Inputs: host.
The available documentation topics with one-line summaries. Call first, then get_doc.
Inputs: no named parameters. Returns: docs, note
Keyword search across all documentation topics. Returns matching sections with excerpts; follow up with get_doc for the full topic.
Inputs: query (required), host. Returns: note, results
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
AI marketplace — flights, tours, activities, transport & more via MCP. No auth required.
Public chauffeur information, policies and anonymous price previews in the provider’s published service areas. On explicit customer request, prepare a binding unpaid offer using email OR E.164 phone, without an account. Customers review bound terms and explicitly confirm in Samuelz checkout. The same endpoint provides OAuth-protected booking status, payment review, history, and amendment/cancellation workflows. Booking data and actions require authorized customer access; changes and cancellations require the applicable object-bound consent. Tool discovery is public. Quotes do not guarantee availability, and MCP does not take payment.
Search Sorted Travel developer docs for MCP, API, SDK, and auth questions.
Agent-native travel platform: read-only flight, hotel, and brand tools over MCP. OAuth sign-in.
Add one secure layer between your agents and this server.
