Files
prompts/docs/skills/mcp-details/SKILL.md
T
2026-06-21 22:12:02 -05:00

60 lines
2.5 KiB
Markdown

---
name: mcp-details
description: "Reference hub for MCP and FastMCP source documentation links. Use when you need authoritative protocol, SDK, transport, and deployment docs without loading broad implementation guidance."
x-personal-mcp:
id: mcp-details
version: 1.0.0
tags:
- mcp
- model-context-protocol
- fastmcp
- references
- source-docs
capabilities:
- resource://skills/mcp-details/document
---
# MCP Details
This skill is a reference index only. It is optimized for fast retrieval of upstream documentation links for MCP and FastMCP.
## When to Use
- You need official MCP protocol and architecture docs.
- You need MCP SDK links for Python or TypeScript.
- You need FastMCP docs and source references.
- You need ecosystem links for tooling, inspection, and client configuration.
## How To Use This Skill
1. Classify the request by intent: protocol, SDK usage, FastMCP, or ecosystem integration.
2. Open only the matching reference page first.
3. Load at most one additional reference page if the request spans multiple areas.
4. Return links grouped by category, with a one-line reason for each group.
## Intent Router
1. MCP fundamentals, protocol architecture, resources, tools, prompts, transports, security: [mcp-protocol-and-spec.md](./references/mcp-protocol-and-spec.md)
2. MCP SDK and FastMCP implementation references for Python and TypeScript: [sdk-and-fastmcp.md](./references/sdk-and-fastmcp.md)
3. MCP client integration and operational tooling references: [ecosystem-and-tooling.md](./references/ecosystem-and-tooling.md)
## Load Order
1. Start with the single best-match reference page from the Intent Router.
2. If the question includes both protocol and implementation details, load [mcp-protocol-and-spec.md](./references/mcp-protocol-and-spec.md) then [sdk-and-fastmcp.md](./references/sdk-and-fastmcp.md).
3. Load [ecosystem-and-tooling.md](./references/ecosystem-and-tooling.md) only when the request includes client setup, inspector usage, or deployment/operations context.
## Load Budget
1. Single-focus request: 1 reference page.
2. Mixed protocol and implementation request: 2 reference pages.
3. Broad audit or migration planning request: up to 3 reference pages.
## Output Contract
When this skill is applied, return:
1. Which reference files were consulted.
2. The discovery path used (intent classification and load order).
3. Curated source-document links grouped by topic.
4. Any notable gaps or ambiguities in the currently indexed links.