MCP is now how agents reach your systems
The Model Context Protocol went from Anthropic side project to Linux Foundation standard with over 10,000 public servers. What the new stateless spec and enterprise auth mean for your stack.
By Saad Alam
MCP
MCP is now how agents reach your systems
In December 2025 Anthropic donated MCP to the Agentic AI Foundation under the Linux Foundation, and adoption followed fast. There are now more than 10,000 public MCP servers, the SDKs see close to 100 million downloads a month, and around 4 in 10 software organisations report MCP servers in production.
The July 2026 specification is the one that matters for enterprises. The protocol core is now stateless, so gateways, load balancers and rate limiters can route MCP traffic like any other API traffic. Tasks, Extensions and a formal deprecation policy landed alongside it.
Enterprise-Managed Authorization is the sleeper feature. Access to MCP servers now flows through your identity provider, the same way SSO gates your SaaS. Asana, Atlassian, Linear, Figma and Supabase already support it.
Our advice to clients: treat every MCP server you expose as production API surface. That means authentication through your IdP, a tool-safety review before anything ships, and the same observability you would demand from a public endpoint. We wire MCP servers into client stacks with exactly that posture.
