How do I install the MCP Docs skill?

Run npx skillmds@latest add confluentinc/mcp-docs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is MCP Docs safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with MCP Docs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is MCP Docs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published MCP Docs?

confluentinc (@confluentinc) published this skill. Their other Agent Skills are listed on their SkillMD profile.

MCP Docs by confluentinc — Agent Skill

Name: MCP Docs
Rating: 4.2 (5 reviews)
Author: confluentinc

MCP Docs

Use when the user asks about Model Context Protocol details (protocol spec, transports, authorization, tools/resources/prompts, sampling/elicitation/roots, server/client concepts, extensions, or SDK usage). Triggers on phrases like "MCP spec", "MCP transport", "streamable HTTP", "MCP authorization", "list_tools", "initialize handshake", "MCP SDK", "@modelcontextprotocol/sdk", or "how does MCP X".

confluentinc 720fedd 2.3 KB Updated Sep 10, 2026

File contents

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.md
https://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/sdk APIs.
Extensions (/extensions/...) — Auth, application support, client compatibility matrix. Relevant for auth and transport questions.

---name: mcp-docsdescription: Use when the user asks about Model Context Protocol details (protocol spec, transports, authorization, tools/resources/prompts, sampling/elicitation/roots, server/client concepts, extensions, or SDK usage). Triggers on phrases like "MCP spec", "MCP transport", "streamable HTTP", "MCP authorization", "list_tools", "initialize handshake", "MCP SDK", "@modelcontextprotocol/sdk", or "how does MCP X".---# MCP Protocol Documentation LookupLook up Model Context Protocol (MCP) documentation from modelcontextprotocol.io.## InstructionsYou are looking up MCP protocol documentation to answer a question or guide implementation.### Step 1: Fetch the documentation indexFetch the machine-readable index at `https://modelcontextprotocol.io/llms.txt`. This lists all ~90documentation pages with titles and URLs. Use it to identify which page(s) are relevant to thequestion.### Step 2: Fetch the relevant page(s)Append `.md` to page URLs for cleaner markdown content. For example:- `https://modelcontextprotocol.io/docs/learn/architecture.md`- `https://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 codebaseWhen relevant, use Read and Grep to cross-reference the documentation with our implementation in`src/` to provide concrete, project-specific guidance.## Documentation TiersUse 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/sdk` APIs.- **Extensions** (`/extensions/...`) — Auth, application support, client compatibility matrix. Relevant for auth and transport questions.

Frequently asked questions