MCP servers generated by Stainless now includes a docs search tool that lets LLMs query up-to-date documentation for your Stainless-generated SDKs. The documentation is served in Markdown optimized for model consumption, based on your latest OpenAPI spec and Stainless Config.

See docs for more details.

We now support choosing “CLI” (command line interface) as a target for SDK generation. This lets you automatically generate a command line tool for your SDK.

This feature is still experimental and we may introduce breaking changes to how command line arguments are parsed. See docs for more information.

Preview builds let you see how changes to your OpenAPI spec and Stainless config will affect your SDKs.

Pull requests to your GitHub repository that update the OpenAPI spec will build your SDKs and make a comment on the pull request with the results.

See our documentation on automating builds for more information and setup instructions.

If you participated in the beta by using build-sdk-action, we encourage you to migrate. See the build-sdk-action README for migration details.

Stainless now supports generating methods to parse incoming webhooks into types defined in your OpenAPI specification and verify standard webhook signatures.

app.post('/webhook', async (req, res) => {
  const event: MyWebhookEvent = client.webhooks.unwrap(
    req.body.toString(),
    req.headers,
  );
  ...
});

See docs for more details.

The Stainless generator now automatically retrieves, manages, and refreshes access_tokens for APIs using OAuth client credentials.

const client = new Client({
  clientId: '…',
  clientSecret: '…',
})

client.todos.create()

You can now generate a PHP SDK for your API using Stainless. Create and configure your project to get started.
For any feedback or feature requests, ping hao@.

You can now generate a C# SDK for your API using Stainless. Create and configure your project to get started.

For any feedback or feature requests, ping tomer@.

Although the generated Java/Kotlin SDKs use reflection, they can be made usable in GraalVM by publishing them with reachability metadata. This can be enabled by setting targets.{java,kotlin}.publish.graalvm_metadata to true.

GraalVM should automatically detect and use the published metadata, but manual configuration is also available for end-users.

The generated Java/Kotlin SDKs can now include an automatically generated Spring Boot starter package to simplify configuration for users who use Spring Boot.

This can be enabled by setting targets.{java,kotlin}.publish.spring_boot_starter to true in the Stainless config.

For TypeScript and Python SDKs, we now enable you to download a built artifact of your SDK prior to release, after any build. In TypeScript this is a tarball with your compiled JavaScript files. In Python this is a wheel file. This allows you to inspect, manually test and distribute your SDKs prior to release.