Redocly MCP server

• discoverFree

  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.

• executewrite actionFree

  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.

• submit-feedbackwrite actionFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 3776ms17/20
• Tool poisoning3 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
• Maintenancelast push 0 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year; website matches verified namespace10/10

Safety score

80/100

higher than 70% of 2,174 E-commerce servers

Tools

3

the typical E-commerce server has 6

Tools that change things

67%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote E-commerce server answers 100%

Response time

1,445 ms

faster than 5% of 1,527 E-commerce servers

GitHub stars

1

more than 65% of 1,047 E-commerce servers

Redocly: common questions

Is Redocly MCP server safe?

Mostly: it is graded B (80/100). Read the Redocly safety report

How do I install Redocly?

It runs remotely at redocly.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Redocly need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Redocly maintained?

The last commit was 9 days ago (2026-10-26). The latest release is v1.0.1.

Is Redocly up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of Redocly?

Servers from other publishers that do the same job: HasData Walmart MCP server, WebCake Storefront MCP server and Shopware MCP server. Compare all Redocly alternatives.

How does Redocly compare with other E-commerce MCP servers?

safety score 80/100 (higher than 70% of 2,174 E-commerce servers); tools 3 (the typical E-commerce server has 6); tools that change things 67% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.