Documentation index

The docs are organized by how people actually read product documentation: overview first, then concepts, implementation guides, examples, and strict reference pages.

Start with introduction Protocol reference

Overview

Start here if you need the project shape, compatibility promise, and the first deployment choices.

What ZCP is, how it relates to MCP, and how to choose your first path.

Introduction And Getting StartedThe best first page if you already know MCP and need to understand the ZCP split quickly.

Concepts

The object model and runtime features that define how a ZCP server should be designed.

Tools, resources, prompts, sampling, elicitation, progress, roots, and tasks.

Core Concepts: Tools, Resources, Templates, And PromptsThe core object model behind most ZCP and MCP-compatible server design decisions.Core Concepts: Sampling, Elicitation, Roots, Logging, Progress, And TasksThe guide for workflows that move beyond synchronous tool calling.

Guides

Topic-focused implementation guidance for transport, auth, clients, and servers.

The pages you should rely on while building and deploying.

Transport GuideUse this before you lock in your transport, reconnect, and replay assumptions.Authorization GuideThe current auth story, including production boundaries and deployment guidance.Server GuideThe main implementation guide for `FastZCP`, ASGI hosting, stdio, and server policy.Client GuideThe page to read before you design client retries, notifications, and long-running task handling.Semantic Workflow ProfileThe dedicated explanation page for `semantic-workflow`, workflow-tagged tools, and native discovery.

Examples

Scenario-driven pages for adoption, migration, and compatibility planning.

Use cases and FAQ material for real-world rollout questions.

Examples And Use CasesScenario-driven reading for real adoption paths instead of isolated API snippets.FAQA fast way to check the current claim boundary without reading the full reference stack.

Reference

Exact protocol, parity, API, benchmark, and gap-tracking material.

The strict source of truth for what is implemented and how to verify it.

Protocol ReferenceWhat ZCP serves on `/mcp`, how it maps runtime behavior to MCP, and which notes still matter.SDK APIServer APIs, session APIs, transport helpers, auth types, and configuration types.Capability MatrixImplemented versus covered versus still incomplete, with ZCP-native advantages called out directly.Migration GuideRollout order, compatibility strategy, and where native ZCP should and should not be introduced first.Benchmark MethodologyThe benchmark source of truth lives in the Python SDK repo and should stay reproducible.MCP Gap And TODOAuth-client interop, task coverage, transport soak tests, output validation, and docs convergence gaps.