Concepts
Deep dives into how mcpkit implements the MCP protocol — session bring-up, transports, notifications, the request lifecycle, extension surfaces, reverse calls, MRTR, tracing, and events.
Concepts
Nine deep dives into how mcpkit implements the protocol — not API reference, but the "why it works this way" behind each surface. Read them in order for a full tour, or jump to the one you need.
Bring-up
Session establishment: transport, auth, version negotiation, capabilities, and the initialized handshake.
Transport mechanics
How the streamable-HTTP and stdio transports move requests, responses, and server-initiated pushes.
Notifications
The six notification families, their direction and capability gates, and per-session fan-out.
Anatomy of a request
The end-to-end journey of a request through mcpkit's dispatch pipeline, step by step.
Extension mechanisms
The four extension surfaces and how mcpkit organizes core / ext / experimental.
Reverse calls
Server-initiated sampling, elicitation, and roots/list — and how the handler context gates them.
MRTR internals
The InputRequiredResult envelope, signed requestState, and the client auto-loop.
Tracing
W3C trace context across the MCP wire — off by default, zero-overhead when unconfigured.
Events
The experimental cross-replica events bus: push, poll, webhooks, and trace propagation.