Redocly

endpoint

https://redocly.com/mcp

door code

0568ce63dfe50cff

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is Redocly live?

Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.

Is Redocly free to use?

Yes — the hub reached it with no key and no payment.

What tools does Redocly have?

3 tools: execute, submit-feedback, discover.

Is Redocly safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• discover open 17h ago

  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.

  mcp-tool

  1234567891011121314151617181920212223242526

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

  arguments 26 lines copy
• execute reads unknown never probed

  Run plain JavaScript (no TypeScript syntax) 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.

  mcp-tool

  1234567891011121314151617181920

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

  arguments 20 lines copy
• submit-feedback unknown never probed

  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.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334

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

  arguments 34 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

• cafe.redocly.com Docs MCP server mcp · 5 tools