CSE Roadmap

Core tier · about 5 hours · 14 parts

Part 12 of 14 · 1 min read

Quick notes

  • MCP turns N times M adapters into N plus M. A host creates one client per server; each server implements its side once, and any host that speaks the protocol can use it, which is also why an MCP server is a larger attack surface than code you wrote yourself.
  • Each primitive has a different decider. Tools are model-controlled and become function schemas; resources are application-driven context; prompts are user-controlled templates. Only tools ever reach the model's own function list.
  • The protocol has two eras, and a real client needs both. The older era opens with a handshake the server remembers; the newer era is stateless, with every request carrying its own version and capabilities. Probe for the modern era first and fall back.
  • A stateless server still keeps state, just behind a handle. A creation tool returns an id; later calls pass it as an ordinary argument. The handle, not the connection, is what carries the state.
  • The host does the jobs the protocol does not: prefix tool names so two servers cannot collide, convert tools to ordinary function schemas, distrust a server's own claims about itself, and keep the conversation in one place the servers never see.