Anthropic buys Stainless, expands SDK control

Anthropic’s purchase of Stainless is a control-plane deal before it is a model deal. On May 18, Anthropic said it was acquiring Stainless, a company it described as a leader in SDKs and MCP server tooling, and said Stainless had powered every official Anthropic SDK since the earliest days of the Claude API. (anthropic.com) That matters because SDKs decide how developers actually touch a model in production. (anthropic.com) Stainless sits in the layer that turns APIs into maintained client libraries and server tooling, which means Anthropic is buying more of the machinery that shapes how Claude connects to tools, data and external systems. Anthropic framed the acquisition around agent reach, saying agents are only as capable as the systems they can reach. (sailpoint.com) ### Why does an SDK company matter this much? Stainless is not a consumer brand, but it is close to the developer path between model providers and enterprise applications. Anthropic said Stainless has shaped how developers experience the Claude API from the start, and that the company’s work spans SDKs and MCP server tooling. (anthropic.com) TechCrunch reported that Stainless software was also widely used by rival AI labs, including OpenAI and Google, as well as Cloudflare. That makes the acquisition notable beyond Anthropic’s own stack, because it puts a vendor at the center of tooling previously used across multiple ecosystems. (anthropic.com) ### Where does MCP fit into this? Anthropic’s announcement explicitly tied Stainless to MCP server tooling. MCP, or Model Context Protocol, is Anthropic’s standard for connecting models to tools and data sources, and Anthropic said the Stainless deal would extend Claude’s reach further into those systems. (anthropic.com) In practice, that pushes Anthropic deeper into the layer where agent systems are assembled. Models may generate the output, but protocols, SDKs and connectors determine whether those systems can reliably call tools, fetch data and complete multi-step work. Anthropic’s own language in the announcement focused on that connectivity rather than on benchmark gains or model upgrades. (techcrunch.com) ### Why are SailPoint and Relativity part of the same story? May 21 brought a second signal from the Claude ecosystem: compliance data is moving closer to runtime operations. SailPoint said its new connector with the Claude Compliance API gives Claude Enterprise organizations visibility and governance over access to and usage of AI platforms across the enterprise. (anthropic.com) Relativity said the same day that it had integrated the Claude Compliance API into RelativityOne to collect Claude Enterprise activity. The company said RelativityOne now supports native collection from ChatGPT Enterprise, Gemini Enterprise and Claude Enterprise. (anthropic.com) ### What does the Compliance API add? Anthropic’s help documentation says the Compliance API now includes audit log events, giving administrators a fuller view across Claude deployments. The company says Claude Platform admins can enable the Compliance API from the platform, and the documentation points users to audit-log access for recorded events. (sailpoint.com) That means the same ecosystem now has two parallel moves: Anthropic is taking tighter ownership of the SDK and MCP layer through Stainless, while partners are plugging Claude activity into identity, legal and audit systems through the Compliance API. SailPoint cast its connector as identity security for AI platforms; Relativity positioned its integration as collection for legal work. (relativity.com) ### What should readers watch next? Anthropic did not disclose deal terms in its announcement on May 18. The next concrete markers are product ones: how Anthropic incorporates Stainless into its SDK and MCP roadmap, and how broadly enterprises adopt Compliance API integrations now that audit log events are available to Claude customers. (support.claude.com) (anthropic.com) (sailpoint.com)