| layout | default |
|---|---|
| title | MCP Docs Repo Tutorial |
| nav_order | 178 |
| has_children | true |
| format_version | v2 |
Learn how to use
modelcontextprotocol/docsas an archived reference, map its conceptual guides, and migrate documentation workflows to the canonicalmodelcontextprotocol/modelcontextprotocoldocs location.
MCP documentation has been reorganized over time. The archived docs repository still contains useful conceptual and tutorial material, but active changes now live in the main protocol repository.
This track focuses on:
- understanding archive status and canonical docs migration paths
- extracting enduring concept docs (architecture, tools, resources, transports)
- using quickstart/tutorial content as historical reference
- setting contribution and governance workflows against the active docs source
- repository:
modelcontextprotocol/docs - stars: about 428
- status: archived
flowchart LR
A[Archived docs repo] --> B[concept guides]
A --> C[quickstart/tutorial references]
A --> D[client matrix]
B --> E[canonical docs migration]
C --> E
D --> E
| Chapter | Key Question | Outcome |
|---|---|---|
| 01 - Getting Started and Archive Context | What is this repo’s current role in the MCP docs ecosystem? | Clear scope |
| 02 - Repository Layout and Canonical Migration Path | How should teams navigate archived vs active docs sources? | Better source-of-truth discipline |
| 03 - Quickstart Flows: User, Server, and Client | What practical onboarding flows are still captured here? | Faster onboarding context |
| 04 - Core Concepts: Architecture, Tools, Resources, Prompts | Which conceptual guides remain useful reference material? | Stronger conceptual model |
| 05 - Advanced Concepts: Transports, Sampling, and Roots | How do advanced protocol patterns map to implementation work? | Better design decisions |
| 06 - Tooling Docs: Inspector and Debugging | How do archived tool docs support day-to-day development? | Improved debugging workflows |
| 07 - Tutorial Assets and Client Ecosystem Matrix | How should teams consume ecosystem/client compatibility content? | Better planning signals |
| 08 - Contribution Governance and Documentation Operations | How do teams contribute and maintain docs with the archive/active split? | Sustainable documentation process |
- how to separate historical documentation value from active source-of-truth docs
- how to apply archived concept guides without drifting from current specification
- how to use quickstarts/tutorials/client matrices as compatibility context
- how to set contribution workflows around canonical docs ownership
- Docs Repository README
- Introduction
- Quickstart: Server
- Quickstart: Client
- Quickstart: User
- Architecture Concepts
- Tools Concepts
- Resources Concepts
- Prompts Concepts
- Sampling Concepts
- Transports Concepts
- Inspector Guide
- Debugging Guide
- Client Ecosystem Matrix
- MCP Specification Tutorial
- MCP Quickstart Resources Tutorial
- MCP Inspector Tutorial
- MCP TypeScript SDK Tutorial
Start with Chapter 1: Getting Started and Archive Context.
- Start Here: Chapter 1: Getting Started and Archive Context
- Back to Main Catalog
- Browse A-Z Tutorial Directory
- Search by Intent
- Explore Category Hubs
- Chapter 1: Getting Started and Archive Context
- Chapter 2: Repository Layout and Canonical Migration Path
- Chapter 3: Quickstart Flows: User, Server, and Client
- Chapter 4: Core Concepts: Architecture, Tools, Resources, Prompts
- Chapter 5: Advanced Concepts: Transports, Sampling, and Roots
- Chapter 6: Tooling Docs: Inspector and Debugging
- Chapter 7: Tutorial Assets and Client Ecosystem Matrix
- Chapter 8: Contribution Governance and Documentation Operations
Generated by AI Codebase Knowledge Builder