
Search and read the Redocly product docs, guides and blog on redocly.com, and report a wrong page.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
Names of the sandbox functions to discover: listApis, getEndpoints, getEndpointInfo, getSecuritySchemes, getFullApiDescription, search, listPages, getPage, grepPages. Omit to discover all of them.
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.
| Argument | Type | Description |
|---|---|---|
| names | array | Names of the sandbox functions to discover: listApis, getEndpoints, getEndpointInfo, getSecuritySchemes, getFullApiDescription, search, listPages, getPage, grepPages. Omit to discover all of them. |
{
"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
}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.
| Argument | Type | Description |
|---|---|---|
| code* | string | JavaScript to run in the sandbox. Return a value to receive it as the result. |
| description* | string | A short, human-readable summary of what this code does. |
{
"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
}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.
| Argument | Type | Description |
|---|---|---|
| path* | string | Path or URL of the documentation page the feedback is about (e.g. /guides/auth) |
| details | string | Expected versus actual behavior, missing steps, or the snippet that failed |
| summary* | string | One sentence that names what is wrong with the page |
| targetFeature | string | The API or feature the page documents |
{
"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
}