Anthropic Acquires Stainless: What It Means for Developers Building on Claude
Anthropic has acquired Stainless, the startup behind every official Claude SDK and MCP server generator, in a deal reportedly worth over $300M.
Anthropic has acquired Stainless, the New York-based startup that generates SDKs, CLIs, and MCP servers from API specifications. The deal, reported by The Information as valued at above $300 million, was announced on 18 May 2026. If you have ever used an official Anthropic SDK in Python, TypeScript, Go, Java, or Kotlin, you have already used something Stainless built.
What Stainless Actually Does
Founded in 2022 by former Stripe engineer Alex Rattray and Mark McGranaghan, Stainless solves a genuinely tedious problem. When an API company updates its API, someone has to update the client libraries in every language that developers use. Do it manually and things go out of sync fast. Stainless automated that: give it an OpenAPI spec, and it generates production-ready SDKs across TypeScript, Python, Go, Java, Kotlin, Ruby, C#, and PHP. Each one handles authentication, streaming, webhooks, async patterns, and unit tests, and is written to feel native in its language rather than like a mechanical translation.
Beyond SDKs, Stainless also generates MCP servers, the connectors that let AI agents talk to external APIs. It generates CLI tools and Terraform providers from the same spec. Stainless estimated that roughly a quarter of the world’s professional software developers have used an SDK or visited a docs site it produced.
Notable customers included OpenAI, Google, Cloudflare, Replicate, and Runway, alongside Anthropic itself.
What Changes Now
The short answer for most Stainless customers: the hosted product is going away.
From the day of the announcement, new signups, new projects, and new SDK generation are no longer available on the Stainless platform. Existing customers keep full rights to the SDKs they have already generated (published under Apache 2.0), but the platform that would generate updates as their APIs evolve is being wound down. Companies that relied on Stainless to keep their SDKs current will need to find alternatives or build the capability in-house.
For Anthropic’s own developers, the effect runs in the opposite direction. SDK and MCP server development now sits inside the same organisation as the model itself, which means tighter coordination between API changes and the libraries developers use to build on them.
What This Means for You
If you build on Claude’s API, this is broadly good news. Having the SDK tooling under the same roof as the model means you should see faster library updates when the API changes, fewer gaps between what the API supports and what the official libraries expose, and more coherent MCP server support as agent use cases expand. The team that knows exactly what’s changing in the model will also be managing the tools developers use to connect to it.
If you were a Stainless customer, the practical question is how to maintain your SDKs going forward. You own what you have, but keeping those libraries up to date as your API evolves now requires either a replacement service or internal tooling. The Hacker News discussion around the announcement flagged a few emerging alternatives, so that space is worth watching.
If you use Claude through an enterprise integration, the governance point is worth noting. MCP servers make it easy to connect AI agents to external APIs at scale. That speed is useful, but it can also create endpoints that lack proper authentication, monitoring, or clear ownership. The Stainless acquisition accelerates MCP adoption inside Anthropic’s ecosystem, which makes having clear internal policies around agent connectivity more important, not less.
The Bigger Picture
This is Anthropic’s fourth acquisition in six months, following Bun (the JavaScript runtime Claude Code ships as), Vercept (computer operations), and Coefficient Bio (AI biotech). The pattern is consistent: Anthropic is buying infrastructure its products depend on, and in some cases, infrastructure its competitors also depend on.
Stainless fits both descriptions. It was already powering every official Anthropic SDK. It was also powering SDKs for OpenAI, Google, and Cloudflare. Those companies now need to solve the SDK generation problem another way.
This reflects a broader shift in how AI companies compete. Model performance differences between the leading providers have narrowed considerably. Differentiation increasingly comes from the quality of the developer experience, the reliability of the tooling, and how smoothly agents can connect to external systems. Acquiring the team that built the best SDK generator in the market addresses all three, while removing it from the table for competitors.
Anthropic also created and maintains the Model Context Protocol, which has become the default standard for connecting AI agents to tools and data. Even OpenAI now uses it. Having the team that generates MCP servers sitting inside Anthropic, working directly with the people who define the protocol, puts Anthropic in a strong position as agent connectivity becomes central to how enterprises use AI.
The Stainless team is small but experienced, drawing on backgrounds from Stripe, Heroku, and Twilio. They raised around $35 million total, including a $25 million Series A led by a16z with participation from Sequoia, Felicis, and others. At a reported $300 million plus, the acquisition represents a significant return and a clear signal about how Anthropic values developer tooling infrastructure.