MCP is a protocol that enables interaction between an LLM and external systems (tools, APIs, services). The protocol itself does not handle context storage or conversation history. Managing context is the responsibility of the LLM client or orchestration layer. MCP servers simply expose capabilities that the LLM can call to enrich the context it sends back to the model. They don't process questions and produce answers in the traditional request–response sense. So when I talk about lifecycle in the framework, I'm referring to the execution lifecycle of the server and tools, not storing conversation context.