Confluent MCP Server is an open-source Model Context Protocol server that lets AI assistants interact with Confluent Cloud, Confluent Platform, and standalone Apache Kafka through natural language. Its tools cover Kafka, Flink SQL, Schema Registry, connectors, and Tableflow. The catalogue add-ons help agents operate and configure the server.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/confluentinc/mcp-confluent/mcp-docsnpx skills add confluentinc/mcp-confluent --skill mcp-docsgit clone --depth 1 https://github.com/confluentinc/mcp-confluentWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/confluentinc/mcp-confluent/mcp-docs)<a href="https://agentmods.dev/skills/confluentinc/mcp-confluent/mcp-docs"><img src="https://agentmods.dev/badge/skills/confluentinc/mcp-confluent/mcp-docs.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00096 | $0.00549 |
| Opus 5 | $0.00048 | $0.00275 |
| Sonnet 5 | $0.00019 | $0.00110 |
| Haiku 4.5 | $0.00010 | $0.00055 |
Grade A, and why
mcp-docs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
MCP Protocol Documentation Lookup
Look up Model Context Protocol (MCP) documentation from modelcontextprotocol.io.
Instructions
You are looking up MCP protocol documentation to answer a question or guide implementation.
Step 1: Fetch the documentation index
Fetch the machine-readable index at https://modelcontextprotocol.io/llms.txt. This lists all ~90
documentation pages with titles and URLs. Use it to identify which page(s) are relevant to the
question.
Step 2: Fetch the relevant page(s)
Append .md to page URLs for cleaner markdown content. For example:
https://modelcontextprotocol.io/docs/learn/architecture.mdhttps://modelcontextprotocol.io/specification/2025-11-25/server/tools.md
Fetch only the pages needed to answer the question — typically 1-3 pages.
Step 3: Cross-reference with our codebase
When relevant, use Read and Grep to cross-reference the documentation with our implementation in
src/ to provide concrete, project-specific guidance.
Documentation Tiers
Use these categories to prioritize which pages to fetch:
-
Specification (
/specification/2025-11-25/...) — Protocol-level details: transports, lifecycle, tools, resources, prompts, pagination, logging. Prioritize for questions about MCP server implementation, protocol behavior, or message formats. -
Develop guides (
/docs/develop/...) — Building servers/clients, connecting local/remote servers. Prioritize for integration, setup, or "how do I build..." questions. -
Learn (
/docs/learn/...) — Architecture, core concepts, server/client roles. Prioritize for conceptual or "how does MCP work" questions. -
SDK (
/docs/sdk.md) — SDK reference. Relevant when working with@modelcontextprotocol/sdkAPIs. -
Extensions (
/extensions/...) — Auth, application support, client compatibility matrix. Relevant for auth and transport questions.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 63 lines · 96 tokens per session scan A 5b2a4bf518b7
mcp-docs is a skill published in the GitHub repository confluentinc/mcp-confluent (167 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 549 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…