Redocly

Search and read the Redocly product docs, guides and blog on redocly.com, and report a wrong page.

我該用這個嗎

品質與安全性

A
說明品質
90%
結構描述完整度
97%
命名品質
83%
汙染風險
80%
權限相符程度
100%
協定合規性
100%

發現項目(4)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool description contains URL to non-standard domain在 execute 中
  • LOWTool 'submit-feedback' description lacks action verb在 submit-feedback 中
  • LOWTool 'submit-feedback' doesn't follow camelCase/snake_case在 submit-feedback 中

根據工具定義與協定合規性的自動化分析。

上下文成本

~1,015Token(工具定義)
~1.8 KB典型回應大小
中等的注意力影響(128k 上下文的 0.79%)

這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。

安裝

一鍵安裝

將以下內容加入你的 `claude_desktop_config.json` 檔案:

{
  "mcpServers": {
    "mcp": {
      "url": "https://redocly.com/mcp"
    }
  }
}

遠端端點

https://redocly.com/mcpstreamable-http

它能做什麼

工具清單

工具(3)

🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
🟢execute(code, description)

Run JavaScript in a sandbox against the documentation at https://redocly.com. The script calls the sandbox functions on the global `site` object. The only extra global is `site` - there is no `fetch`, `console`, `setTimeout`, `require`, or Node.js API; all I/O goes through `site`. Workflow - minimize round-trips; one `discover` call plus one `execute` call covers most requests: 1. Analyze the request and decide which sandbox functions it needs. 2. Call `discover` with those names to get their exact TypeScript signatures - inputs, result shapes, and a worked example. NEVER call `execute` with guessed function names, parameter names, enum values, or result field names: read fields off the declared return types, not from assumptions. 3. Batch everything into a SINGLE script: chain function calls, pass one call's output into the next, process results in plain JavaScript, and `return` only what the request needs. Functions for `execute` scripts (signatures come from `discover`): - listApis — List the available APIs. - getEndpoints — Get all endpoints for an API. - getEndpointInfo — Get the details of an endpoint. - getSecuritySchemes — Get the security schemes for an API. - getFullApiDescription — Get the complete OpenAPI description. - search — Search the documentation. - listPages — List the docs navigation, one level per call. - getPage — Read a docs page as Markdown, in line windows. - grepPages — Find the docs lines that contain a text.

輸入結構描述

{
  "type": "object",
  "properties": {
    "code": {
      "type": "string",
      "description": "JavaScript to run in the sandbox. Return a value to receive it as the result.",
      "minLength": 1
    },
    "description": {
      "type": "string",
      "description": "A short, human-readable summary of what this code does.",
      "minLength": 1
    }
  },
  "required": [
    "code",
    "description"
  ],
  "additionalProperties": false
}

輸出結構描述

{
  "type": "object",
  "properties": {
    "result": {
      "description": "The value the code returned, as JSON"
    },
    "error": {
      "type": "string",
      "description": "Why the code failed. Set only on a failed call"
    }
  }
}
🟢discover(names)

Get the exact TypeScript signatures of the sandbox functions that `execute` scripts can call. Analyze the user request first, then pass `names` with only the functions the request needs (every name is listed in this input schema / description); omit `names` only when you cannot tell which functions apply. Always call this before your first `execute` and never guess signatures. Request every function the task may need in ONE call instead of calling this repeatedly.

輸入結構描述

{
  "type": "object",
  "properties": {
    "names": {
      "type": "array",
      "description": "Names of the sandbox functions to discover: listApis, getEndpoints, getEndpointInfo, getSecuritySchemes, getFullApiDescription, search, listPages, getPage, grepPages. Omit to discover all of them.",
      "items": {
        "type": "string",
        "enum": [
          "listApis",
          "getEndpoints",
          "getEndpointInfo",
          "getSecuritySchemes",
          "getFullApiDescription",
          "search",
          "listPages",
          "getPage",
          "grepPages"
        ]
      },
      "nullable": true
    }
  },
  "required": [],
  "additionalProperties": false
}
🟡submit-feedback(path, summary, details, targetFeature)

Report a documentation page that is wrong or incomplete. Use it when the user reports a problem with a page on this site, or agrees to report a problem that you found. Do not use it for product bugs or support questions.

輸入結構描述

{
  "type": "object",
  "properties": {
    "path": {
      "type": "string",
      "description": "Path or URL of the documentation page the feedback is about (e.g. /guides/auth)",
      "minLength": 1,
      "maxLength": 1000
    },
    "summary": {
      "type": "string",
      "description": "One sentence that names what is wrong with the page",
      "minLength": 1,
      "maxLength": 500
    },
    "details": {
      "type": "string",
      "description": "Expected versus actual behavior, missing steps, or the snippet that failed",
      "maxLength": 4000,
      "nullable": true
    },
    "targetFeature": {
      "type": "string",
      "description": "The API or feature the page documents",
      "maxLength": 500,
      "nullable": true
    }
  },
  "required": [
    "path",
    "summary"
  ],
  "additionalProperties": false
}

輸出結構描述

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string"
    },
    "page": {
      "type": "string"
    },
    "message": {
      "type": "string"
    }
  },
  "required": [
    "status",
    "page",
    "message"
  ]
}

社群

為此伺服器評分

證據

近期觀測

已驗證未記錄版本3 個工具