If you've ever built an AI agent or integrated tools, you've likely heard of MCP (Model Context Protocol), and there is some great news. The recently finalized v2.0 update, based on the '2026-07-28' specification, is here. The core change is the shift to a stateless core.

Previously, connecting an MCP server always required an 'initialize/initialized' process to establish a session through a bidirectional handshake. This was fine for simple local use, but it became surprisingly tedious when hosting servers remotely or connecting multiple agents simultaneously, as you had to track and maintain the session ID (Mcp-Session-Id). This complex connection handshake and session header have now been completely removed from the spec! Instead, it has been changed to a much simpler and lighter method where the necessary metadata is included in a _meta object in every request. Thanks to this, you can now attach tools as easily as calling a regular web API without the hassle of state management.

With this major change, the official SDKs for TypeScript and Python have also been updated to v2.0. If you are a TS SDK user, there is one thing to watch out for. The previously unified sdk package has been completely split into a server (@modelcontextprotocol/server) and a client (@modelcontextprotocol/client) package. When integrating the new v2.0 client, you must explicitly specify the versionNegotiation setting in your options so that it automatically works with the new standard without the legacy handshake phase.

Fortunately, the Python SDK automatically handles these versions internally, so it integrates smoothly without needing extra configuration.

For developers who host their own servers and run remote MCP services, you no longer need to worry about 'sticky sessions' that required routing traffic to specific servers. You can now easily host servers behind a standard load balancer for seamless, distributed processing. It feels like the AI agent ecosystem is becoming significantly lighter and more cloud-native. If you've been using MCP to build your own agent environment, be sure to migrate to the new v2.0 SDK and experience the lighter, faster performance for yourself!