# com.redpanda/docs-mcp (remote · docs.redpanda.com)

Get authoritative answers about Redpanda documentation and search API references.

- Trust score: 64/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `docs.redpanda.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-redpanda-docs-mcp/docs.md), [page](https://verifymcp.io/servers/com-redpanda-docs-mcp/docs)

## Channel facts

- Endpoint: `https://docs.redpanda.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2026.803.133`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1281 tokens (~256/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 85% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-redpanda-docs-mcp https://docs.redpanda.com/mcp
```

### Codex

```toml
[mcp_servers.com-redpanda-docs-mcp]
url = "https://docs.redpanda.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-redpanda-docs-mcp": {
      "type": "remote",
      "url": "https://docs.redpanda.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-redpanda-docs-mcp --url https://docs.redpanda.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-redpanda-docs-mcp:
    url: "https://docs.redpanda.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-redpanda-docs-mcp": {
      "type": "http",
      "url": "https://docs.redpanda.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 62, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (5)

### `ask_redpanda_question` (~193 tokens)

Search Redpanda Sources

Search the official Redpanda documentation and return the most relevant sections from it for a user query. Each returned section includes the url and its actual content in markdown. Use this tool for all queries that require Redpanda knowledge. Results are ordered by relevance, with the most relevant result returned first.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `question` (string, required)
- `top_k` (number)

### `list_api_reference_pages` (~349 tokens)

List API Reference Pages

List pages in Redpanda API reference documentation. Returns endpoints, schemas, and topic pages with URL, title, type, and description.

SCOPING (important for accurate results):
\- api="all" or omit: Lists all available APIs
\- api="admin": Cluster management operations (brokers, partitions, configs, users)
\- api="cloud-controlplane": Redpanda Cloud resource management (clusters, networks, namespaces)
\- api="cloud-dataplane": Cloud cluster data operations (topics, ACLs, connectors)
\- api="http-proxy": Kafka operations over HTTP (produce, consume, offsets)
\- api="schema-registry": Schema management (register, retrieve, compatibility)

Use this to browse API structure. For general Redpanda docs, use ask_redpanda_question instead.

Input parameters:

- `api` (string): Which API to list: "all" or omit for overview of all APIs, or a specific API name (admin, cloud-controlplane, cloud-dataplane, http-proxy, schema-registry)
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `url` (string): Specific URL path to list children of (optional, defaults to API root)

### `search_api_reference` (~471 tokens)

Search API Reference

Search Redpanda API reference documentation by keyword. Returns up to 20 matching endpoints, schemas, or topics with URL, title, and text excerpts.

SCOPING (important for accurate results):
\- api="all" or omit: Search across ALL APIs at once - useful when unsure which API contains the endpoint
\- api="admin": Search only cluster management (brokers, partitions, configs, users, maintenance)
\- api="cloud-controlplane": Search only Cloud resource management (clusters, networks, namespaces)
\- api="cloud-dataplane": Search only Cloud data operations (topics, ACLs, connectors)
\- api="http-proxy": Search only HTTP Proxy (produce, consume, offsets over HTTP)
\- api="schema-registry": Search only Schema Registry (register, retrieve, compatibility)

WHEN TO USE WHICH:
\- User asks "broker endpoints" → api="admin" (brokers are cluster management)
\- User asks "create topic API" → api="all" (topics exist in admin AND cloud-dataplane)
\- User asks "Cloud cluster API" → api="cloud-controlplane"
\- User asks about Redpanda APIs generally → api="all" or omit

For general Redpanda questions (not API-specific), use ask_redpanda_question instead.

Input parameters:

- `api` (string): Scope: "all" or omit to search all APIs, or specific API name (admin, cloud-controlplane, cloud-dataplane, http-proxy, schema-registry)
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `query` (string, required): Search keywords (e.g., "broker", "create topic", "ACL")
- `type` (string): Filter by type: operation (endpoints), schema (data types), topic (guides), authentication, webhook

### `get_api_reference_content` (~215 tokens)

Get API Reference Content

Retrieve full content of API reference pages by URL. Returns complete endpoint details including parameters, request/response schemas, and examples.

Use this after finding pages via list_api_reference_pages or search_api_reference. Pass the URLs from those results directly.

Returns up to 10 pages per request. URLs must be from docs.redpanda.com/api/doc/*.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `urls` (array, required): Page URLs to retrieve (max 10). Use URLs from list_api_reference_pages or search_api_reference results.

### `get_more_tools` (~53 tokens)

Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.

Input parameters:

- `context` (string, required): A description of your goal and what kind of tool would help accomplish it.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-redpanda-docs-mcp/docs#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 63
- 2026-08-01: 63
- 2026-07-31: 62
- 2026-07-30: 60
- 2026-07-29: 62
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 60

## Links

- Remote endpoint: https://docs.redpanda.com/mcp
- Repository: https://github.com/redpanda-data/docs-site
- Changelog RSS feed: https://verifymcp.io/servers/com-redpanda-docs-mcp/docs/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-redpanda-docs-mcp/docs/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-redpanda-docs-mcp/docs