We’ve removed all MCP tool schemes except for “Code Mode," a scheme that exposes just two tools to agents. These include the “docs-search tool” and an “execute-code tool," which allows agents to execute code against your TypeScript SDK on your behalf.

We now will no longer generate or offer other tool schemes such as regular/dynamic tools. Other options such as hosting/publishing your server with Stainless will remain unchanged.

You can find out more about Code Mode and its advantages in our MCP docs.

Stainless can now host your MCP server for you with just one click from the studio. This means you can access your MCP server without having to download anything or fight with other hosting services.

Learn more about Stainless hosted servers in our docs.

The MCP docs search tool now uses semantic search, which delivers more accurate matches than BM25 and reduces the number of results needed in the context window. This allows both coding agents and our code execution tool to understand and use your Stainless-generated SDKs more effectively.

Users can now launch a remote MCP server using Streamable HTTP transport.

When you pass --transport=http, the server uses the Streamable HTTP transport instead of stdio, allowing it to run remotely (e.g., on EC2, Fly.io, or Kubernetes). You can optionally specify the port with --port.

npx -y my-org-mcp --transport=http

# if you publish your server via Docker Hub, run it from the image:
docker run --rm -i myorg/my-api-mcp --transport

Learn more about remote MCP servers in docs.