docs-mcp server
com.redpanda/docs-mcpredpanda.comstreamable-httpv2026.907.213Scanned
Get authoritative answers about Redpanda documentation and search API references.
11 tools: 1 change things and 10 only read.
- Reads private data · 3
- Reads text others write · 5
- Can send data out · 2
- 22 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the docs-mcp server can do
The docs-mcp server is published by redpanda.com, a domain the MCP Registry verified. It has 11 tools. It can create or change data (1 tool: give_feedback), but cannot delete data. 10 tools only read.
3 tools read private data (get_config_property, get_rpk_command and list_rpk_commands); 5 tools bring in text other people can write (list_api_reference_pages, get_api_reference_content, give_feedback and 2 more); 2 tools can send data out of your system (list_api_reference_pages and get_api_reference_content). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 22 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 2026.907.213.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
11 tools
Changes things 1Claude Code: ask
give_feedbackReport a concrete problem to the Redpanda docs team: documentation that is missing, unclear, outdated, or wrong, a docs tool that returned something wrong or unhelpful, or a Redpan…Reads text others write2 findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...the user's name or email: never include credentials, tokens, or personal data."
- Info
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
Description, as the server wrote it Report a concrete problem to the Redpanda docs team: documentation that is missing, unclear, outdated, or wrong, a docs tool that returned something wrong or unhelpful, or a Redpanda product issue you ran into. Call it when you notice the problem, with enough detail to fix it, including the page URL when you know it. Do not call it to test the tool. It records the report and returns a short confirmation; it does not return documentation. Reports do not include the user's name or email: never include credentials, tokens, or personal data.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
Only reads 10Show 10 read-only tools
ask_redpanda_questionSearch the official Redpanda documentation and return the most relevant sections from it for a user query.2 findings
Why it is in this group
- The description's first verb is "search": a word for reading.
Findings
- Info
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
- Info
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
Description, as the server wrote it 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. If you know the user's deployment platform, pass "platform" so results from the other platform's docs are excluded. Note that "platform" filters the sections already retrieved rather than re-running the search, so it can return substantially fewer sections: on a broker-level question where most matches come from the other platform's docs, it can cut a 15-section response to 1 or 2. Omit "platform" if you would rather have more context and judge platform relevance yourself from each section's url. If you know which Redpanda version the user runs, pass "version" (use 'current' for the latest release; its release number is also accepted). Unlike "platform", "version" is applied during retrieval, so it does not shrink the result set: it stops the same page being returned once per indexed version, which is otherwise most of the response. Version-neutral docs (Cloud, Connect, Agentic Data Plane, API reference) are always included. Omitting "version" searches the latest release.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_api_reference_contentRetrieve full content of API reference pages by URL.Reads text others writeCan send data out2 findings
Why it is in this group
- The name "get_api_reference_content" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "retrieve" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.urls), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.urls): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Findings
- Info
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
- Info
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
Description, as the server wrote it 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/*.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_config_propertyLook up one Redpanda configuration property (cluster, broker, or topic) by exact name and return its documented type, default, description, restart and enterprise flags, Redpanda C…Reads private dataReads text others write2 findings
Why it is in this group
- The name "get_config_property" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "doc": it reads documents.
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Findings
- Info
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
- Info
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
Description, as the server wrote it Look up one Redpanda configuration property (cluster, broker, or topic) by exact name and return its documented type, default, description, restart and enterprise flags, Redpanda Cloud availability, related properties, and docs URL. Deterministic: it reads the generated property dataset for the requested docs version, so a property that does not exist returns found=false with close-name suggestions instead of a guess, and no LLM or search is involved. Use this before ask_redpanda_question for any question about a specific property's default, type, or availability. Pass platform='cloud' to learn whether the property is supported or editable in Redpanda Cloud.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_connect_componentLook up one Redpanda Connect component (input, output, processor, cache, buffer, rate_limit, metric, tracer, scanner) by type and name.2 findings
Why it is in this group
- The name "get_connect_component" says "get": a word for reading.
Findings
- Info
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
- Info
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
Description, as the server wrote it Look up one Redpanda Connect component (input, output, processor, cache, buffer, rate_limit, metric, tracer, scanner) by type and name. Returns its status, summary, description, categories, Redpanda Cloud support, docs URL, and every configuration field as a row (path, type, default, one-line summary, advanced/optional/deprecated flags). Pass field to get one field in full: description, examples, options, child fields. Deterministic and read from the generated component schema for the published Connect release: a name that does not exist returns found=false and says whether the same name exists under another type (the redpanda input vs the redpanda output). Use this before ask_redpanda_question for any question about a specific component or field.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_rpk_commandLook up one rpk CLI command by its full name (for example 'rpk topic create') and return its usage, help text, flags with types and defaults, aliases, subcommands, platform and Red…Reads private dataReads text others write2 findings
Why it is in this group
- The name "get_rpk_command" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "doc": it reads documents.
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Findings
- Info
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
- Info
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
Description, as the server wrote it Look up one rpk CLI command by its full name (for example 'rpk topic create') and return its usage, help text, flags with types and defaults, aliases, subcommands, platform and Redpanda Cloud scoping, the plugin and release it ships with, and the docs page URL. Deterministic: it reads the published rpk command tree for the requested docs version (the same data the rpk reference pages are rendered from), so a command that does not exist returns found=false with close-name suggestions instead of a guess, and no LLM or search is involved. The name may omit the leading 'rpk', use command aliases at any level ('rpk topic ls', 'rpk sr schema list'), or be the page name ('rpk-topic-create'). A deprecated command returns its deprecation note and replacement, even when it is hidden and not found. Use this before ask_redpanda_question for any question about a specific rpk command's flags, defaults, or existence in a release.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_api_reference_pagesList pages in Redpanda API reference documentation.Reads text others writeCan send data out2 findings
Why it is in this group
- The name "list_api_reference_pages" says "list": a word for reading.
What it can reach
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Findings
- Info
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
- Info
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_config_propertiesSearch Redpanda configuration properties by a keyword in their name or description, and filter by scope (cluster, broker, topic), platform, or enterprise flag.2 findings
Why it is in this group
- The name "list_config_properties" says "list": a word for reading.
Findings
- Info
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
- Info
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
Description, as the server wrote it Search Redpanda configuration properties by a keyword in their name or description, and filter by scope (cluster, broker, topic), platform, or enterprise flag. Returns compact rows: name, scope, type, default, one-line summary, Cloud support, docs URL. Name matches rank above description matches; deprecated properties are hidden unless include_deprecated is true. Use it to find the right property name before get_config_property, or to answer 'which properties control X'. total=0 means nothing matches in that version; it never falls back to a guess.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_connect_componentsList or search Redpanda Connect components by type, keyword (matched against name, categories, and summary), status, or Redpanda Cloud support.2 findings
Why it is in this group
- The name "list_connect_components" says "list": a word for reading.
Findings
- Info
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
- Info
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
Description, as the server wrote it List or search Redpanda Connect components by type, keyword (matched against name, categories, and summary), status, or Redpanda Cloud support. Returns compact rows with docs URLs. Name matches rank above category and summary matches. Use it to discover what exists (for example every 'Services' input, or every output available in Cloud) before get_connect_component. total=0 means nothing matches.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_rpk_commandsList or search rpk CLI commands for a docs version.Reads private data2 findings
Why it is in this group
- The name "list_rpk_commands" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "doc": it reads documents.
Findings
- Info
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
- Info
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
Description, as the server wrote it List or search rpk CLI commands for a docs version. Filter by a keyword matched against command names and help text, by parent command (for example parent='rpk topic' lists its direct subcommands), or by plugin (connect, ai, k8s, check). Returns compact rows: name, usage, one-line summary, subcommand and flag counts, Cloud scoping, plugin, docs URL. Name matches rank above help-text matches; deprecated commands are hidden unless include_deprecated is true. Use it to find the right command name before get_rpk_command, or to answer 'which rpk commands do X'. total=0 means nothing matches in that version; it never falls back to a guess.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
search_api_referenceSearch Redpanda API reference documentation by keyword.2 findings
Why it is in this group
- The name "search_api_reference" says "search": a word for reading.
Findings
- Info
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
- Info
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
30 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__docs__get_api_reference_content",
"mcp__docs__list_api_reference_pages"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:45 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://docs.redpanda.com/.well-known/oauth-protected-resource
- Authorization servers
- https://docs.redpanda.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://docs.redpanda.com/mcp: tools/list returned 12 tools to an anonymous client, including give_feedback (write)
Findings
Matches of fixed checks, with the text they matched.
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
Show 16 more findingsShow fewer
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
- Infogive_feedback
The description mentions "credentials".
What this check looks forMatched text
description: "...the user's name or email: never include credentials, tokens, or personal data."
- Infogive_feedback
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
- Infoget_rpk_command
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
- Infoget_rpk_command
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
The input schema at properties.context.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.context.description: "...plish with this request. Do not include credentials, tokens, personal data, or verbatim sec..."
The input schema at properties.session_goal.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.session_goal.description: "...nly if the goal changes. Do not include credentials, tokens, personal data, or verbatim sec..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 added.+2 addedView diff
- Added:get_rpk_commandOnly reads
- Added:list_rpk_commandsOnly reads
Tools5 added, 1 removed, 4 changed.+5 added−1 removed~4 changedView diff
- Added:get_config_propertyOnly reads
- Added:get_connect_componentOnly reads
- Added:give_feedbackChanges things
- Added:list_config_propertiesOnly reads
- Added:list_connect_componentsOnly reads
- Removed:submit_documentation_feedback
- Changed:ask_redpanda_questionOnly readsinputSchema
- Changed:get_api_reference_contentOnly readsinputSchema
- Changed:list_api_reference_pagesOnly readsinputSchema
- Changed:search_api_referenceOnly readsinputSchema
Install
Pinned to version 2026.907.213. Values in angle brackets are yours to fill in.
claude mcp add --transport http docs https://docs.redpanda.com/mcpclaude mcp add --transport http docs https://docs.redpanda.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__docs__ask_redpanda_question",
"mcp__docs__search_api_reference",
"mcp__docs__get_config_property",
"mcp__docs__list_config_properties",
"mcp__docs__get_connect_component",
"mcp__docs__list_connect_components",
"mcp__docs__get_rpk_command",
"mcp__docs__list_rpk_commands"
],
"ask": [
"mcp__docs__list_api_reference_pages",
"mcp__docs__get_api_reference_content",
"mcp__docs__give_feedback"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as docs. Review it before you use it.
Capability tags behind 6 rules
- mcp__docs__list_api_reference_pages untrusted-input, outbound
- mcp__docs__get_api_reference_content untrusted-input, outbound
- mcp__docs__give_feedback untrusted-input
- mcp__docs__get_config_property private-data, untrusted-input
- mcp__docs__get_rpk_command private-data, untrusted-input
- mcp__docs__list_rpk_commands private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.redpanda/docs-mcp/verify?hash=42ef9756c6b8995872d4796ab27de642b1b4bb1f83a6d8a13dd2d0a071c887a2" | jq -e '.changed == false'Pinned hash 42ef9756c6b8, from Nov 11, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.redpanda/docs-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.redpanda/docs-mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:01 UTC.
docs-mcp server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the docs-mcp server safe?
- No scan can promise that. What its definitions show: 11 tools, 1 of which can change, send or delete something, and 22 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the docs-mcp server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the docs-mcp server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the docs-mcp server have?
- 11 tools: 1 write, 10 read. give_feedback, ask_redpanda_question, list_api_reference_pages, search_api_reference, get_api_reference_content, get_config_property, list_config_properties, get_connect_component and 3 more.
Does the docs-mcp server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the docs-mcp server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): list_api_reference_pages and get_api_reference_content.
Has the docs-mcp server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.