Ch 10 — Production & Ecosystem — Under the Hood

Deployment internals, Docker configs, observability, and protocol evolution
Index← High Level
Under the Hood
-
Click play or press Space to begin...
Step- / 10
ADeployment InternalsWhat happens when a host connects to your server
1
settings
Host ConfigReads mcp.json
parses entries
spawns
terminal
Processfork + exec or
HTTP connect
then
2
handshake
Handshakeinitialize →
initialized
ready
check_circle
ConnectedServer added to
host's tool pool
3
arrow_downward Docker and containerized deployment
BContainerized DeploymentDockerfile, compose, and container patterns
description
DockerfileMulti-stage build
minimal image
builds
deployed_code
ImageIsolated runtime
reproducible
runs
4
dns
Containerstdio via -i flag
or HTTP on port
5
arrow_downward Remote HTTP deployment architecture
CRemote HTTP ArchitectureLoad balancing, sessions, and scaling
dns
Load BalancerRoutes by
Mcp-Session-Id
routes
cloud
Server InstanceStateful session
per client
+
6
storage
Session StoreRedis / DB for
shared state
7
arrow_downward Observability and structured logging
DObservability StackLogging, metrics, tracing, and alerting
article
Structured LogsJSON logs with
request context
+
monitoring
MetricsCounters, histograms
Prometheus/OTel
+
8
timeline
TracingRequest spans
across services
9
arrow_downward Security hardening for production
EProduction Security HardeningDefense in depth for deployed servers
shield
Input SanitizePath traversal
SQL injection
+
speed
Rate LimitsPer-client
per-tool limits
+
lock
SandboxingProcess isolation
filesystem limits
10
arrow_downward Protocol evolution and the specification
FProtocol Evolution & SpecificationHow MCP evolves and where to go next
history
VersioningDate-based versions
backward compat
+
menu_book
Specificationspec.modelcontextprotocol.io
the source of truth
+
rocket_launch
What's NextRegistry, streaming
agent-to-agent
1
Detail