MCP MeasureMCP Measure

index observed

RideDesk Developer Docs

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
82%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~943Tokens (tool definitions)
~1.6 KBTypical response size
Moderate attention impact (0.74% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://ridedesk.app/api/mcpstreamable-http

What it can do

Tool inventory

Tools (5)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢list_docs

The available documentation topics with one-line summaries. Call first, then get_doc.

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {
    "docs": {
      "type": "array",
      "description": "Every documentation topic this server can serve.",
      "items": {
        "type": "object",
        "properties": {
          "topic": {
            "type": "string",
            "enum": [
              "overview",
              "quote-and-book",
              "checkout",
              "endpoints",
              "widgets",
              "attribution",
              "live-chat",
              "customer-portal",
              "mcp-connector"
            ],
            "description": "Pass this to get_doc"
          },
          "title": {
            "type": "string"
          },
          "summary": {
            "type": "string"
          }
        },
        "required": [
          "topic",
          "title",
          "summary"
        ],
        "additionalProperties": false
      }
    },
    "note": {
      "type": "string"
    }
  },
  "required": [
    "docs",
    "note"
  ],
  "additionalProperties": false
}
🟢get_doc(topic, host)

One documentation topic as markdown: the booking API contract, checkout, widgets, attribution, live chat, the customer portal, or the per-account booking MCP server.

Input Schema

{
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "enum": [
        "overview",
        "quote-and-book",
        "checkout",
        "endpoints",
        "widgets",
        "attribution",
        "live-chat",
        "customer-portal",
        "mcp-connector"
      ],
      "description": "A topic from list_docs"
    },
    "host": {
      "type": "string",
      "description": "The operator's RideDesk domain (e.g. their-workspace.ridedesk.app or a custom domain). Optional — examples use a placeholder without it."
    }
  },
  "required": [
    "topic"
  ],
  "additionalProperties": false
}
🟢search_docs(query, host)

Keyword search across all documentation topics. Returns matching sections with excerpts; follow up with get_doc for the full topic.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Keywords, an endpoint path, or a field name (e.g. \"quote_ref\", \"apple pay\", \"/api/enquiries\")"
    },
    "host": {
      "type": "string",
      "description": "The operator's RideDesk domain (e.g. their-workspace.ridedesk.app or a custom domain). Optional — examples use a placeholder without it."
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {
    "results": {
      "type": "array",
      "description": "Matching sections, best first. Empty when nothing matched.",
      "items": {
        "type": "object",
        "properties": {
          "topic": {
            "type": "string",
            "enum": [
              "overview",
              "quote-and-book",
              "checkout",
              "endpoints",
              "widgets",
              "attribution",
              "live-chat",
              "customer-portal",
              "mcp-connector"
            ],
            "description": "Pass this to get_doc for the full topic"
          },
          "heading": {
            "type": "string",
            "description": "The section heading the match sits under"
          },
          "excerpt": {
            "type": "string",
            "description": "Up to 600 characters of the matching section"
          }
        },
        "required": [
          "topic",
          "heading",
          "excerpt"
        ],
        "additionalProperties": false
      }
    },
    "note": {
      "type": "string",
      "description": "Present only when there were no matches."
    }
  },
  "required": [
    "results"
  ],
  "additionalProperties": false
}
🟢get_integration_brief(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.

Input Schema

{
  "type": "object",
  "properties": {
    "host": {
      "type": "string",
      "description": "The operator's RideDesk domain (e.g. their-workspace.ridedesk.app or a custom domain). Optional — examples use a placeholder without it."
    }
  },
  "additionalProperties": false
}
🟢get_widget_snippets(host)

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

Input Schema

{
  "type": "object",
  "properties": {
    "host": {
      "type": "string",
      "description": "The operator's RideDesk domain (e.g. their-workspace.ridedesk.app or a custom domain). Optional — examples use a placeholder without it."
    }
  },
  "additionalProperties": false
}

Recommended Prompts

search_research
Search for information about [topic] using RideDesk Developer Docs
Expected tools: search_docs
find_specific
Find [specific item] using RideDesk Developer Docs
Expected tools: search_docs
retrieve_data
Get details about [item] from RideDesk Developer Docs
Expected tools: get_doc
fetch_info
Fetch [information type] using RideDesk Developer Docs
Expected tools: get_doc
list_items
List all [items] available in RideDesk Developer Docs
Expected tools: list_docs

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded5 tools
verifiedversion not recorded5 tools
verifiedversion not recorded5 tools
verifiedversion not recorded5 tools
verifiedversion not recorded5 tools
verifiedversion not recorded5 tools