← Sokie compared
Moving from Stainless’s MCP server
Stainless joined Anthropic on 18 May 2026 and no longer takes new projects. If Stainless generated an MCP server from your OpenAPI spec, the same spec makes a Sokie server: hosted at its own address, with no package to publish.
Works with any API that has an OpenAPI, Swagger or GraphQL spec, whatever it’s built in. There’s no generated server code for you to keep: change the spec, redeploy, and each tool follows it.
Checked against Stainless’s own pages on 17 November 2026. Sources
What stays the same
- Your OpenAPI spec is the input.
- Endpoints you left out stay out: delete their tool files, or mark them x-mcp: false.
- Each person uses their own API key.
What changes
- No npm package: the server is hosted, and clients add it by its address.
- Every server is remote, with OAuth 2.1 sign-in, so there’s nothing of yours to deploy it to.
- Each person adds their key once, on a Sokie page, instead of in each client’s settings.
- A preview server for every pull request.
Move in four steps
- Take the OpenAPI spec you gave Stainless.
- Run sokie init with it: each endpoint becomes a tool file.
- Bring over the descriptions you wrote, and delete the tools you had left out.
- Run sokie deploy --create, then add the address to your clients.
sokie init openapi.yaml my-api cd my-api sokie login sokie deploy --create
Side by side
| Topic | Sokie | Stainless (as it was) |
|---|---|---|
| Starts from | OpenAPI 3.0, 3.1 or 3.2, Swagger 2, or a GraphQL schema | Your OpenAPI spec, in the Stainless dashboard |
| What you get | A hosted server at its own address | An npm package beside your TypeScript SDK, run with npx |
| Remote use | Every server is remote, with OAuth 2.1 for every client | You deployed it to a host of your own, with OAuth |
| Choosing endpoints | A file per tool: delete one to leave it out | mcp: true per endpoint, and filters when it starts |
| Your API’s credentials | Each caller’s own key, one shared key, or OAuth to your API, per person or shared | An API key in each client’s environment |
| Previews | A preview server for every pull request | Not mentioned on their pages |
| MCP protocol updates | Every server gets a new MCP version or feature on its next deploy, with nothing to change | Not mentioned on their pages |
| Price | Hobby: 100,000 tool calls a month and 3 servers, no card | Free while it was experimental |
| Today | Taking new servers | No new projects since 18 May 2026 |
What Stainless did well
- The generated code was yours to keep, change and run anywhere.
- It handled large APIs and client limits, like a cap on how many tools a client takes.
- It brought code mode to MCP servers made from SDKs.
Try it on your own spec
Free for 100,000 tool calls a month. Bring your own agent; there are no AI credits to buy.
Sources
Where Stainless’s pages don’t say, the table says so. Spotted something out of date? Tell us and we’ll correct it.