mcp-docs

Estrelas164

Forks57

Atualizado29 de abril de 2026 às 20:19

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".

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

confluentinc

confluentinc/mcp-confluent

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Outras ocupações de informáticaInformática e Matemática·SOC 15-1299

SKILL.md

readonly

Mais deste repositório

mesmo repositório

pr-review

confluentinc/mcp-confluent

Reviews pull requests for the Confluent MCP server. Use when reviewing PRs, doing self-review before sharing with the team, or when the user mentions "review PR", "help with PR", "review changes", "self-review", "review local changes", or "check my PR". Focuses on MCP tool wiring, OpenAPI/type coupling, ESM stubbability, transport security, and project-specific patterns.

2026-06-15164

vitest

confluentinc/mcp-confluent

Use when the user asks about Vitest mocking, spies, stubs, fake timers, config, or test runner behavior. Triggers on questions like "vi.fn", "vi.spyOn", "vi.mocked", "Mocked<T>", "mockResolvedValue", "restoreMocks", "vitest mock", "createMockInstance", "useFakeTimers", or how to accomplish test double patterns with Vitest.

2026-04-27164

name	mcp-docs
description	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".
allowed-tools	["WebFetch","WebSearch","Read","Grep"]

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.