← Sokie compared
Sokie vs Zuplo
Zuplo is an API gateway that can also serve its routes as MCP tools, so your API runs behind it. Sokie isn’t a gateway: it reads your spec and calls your API where it already runs.
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 Zuplo’s own pages on 17 November 2026. Sources
Choose Sokie if
- You don’t want to move your API behind a gateway.
- Each person who connects should bring their own API key, today.
- You’ll make more than 1,000 tool calls a month before paying: Sokie’s free plan has 100,000.
- Your spec is Swagger 2 or OpenAPI 3.2.
Choose Zuplo if
- You want a full API gateway in front of your API anyway: rate limits, policies, analytics and a developer portal.
- Your code lives on GitLab, Bitbucket or Azure DevOps.
- You need dedicated or self-hosted infrastructure.
Side by side
| Topic | Sokie | Zuplo |
|---|---|---|
| Starts from | OpenAPI 3.0, 3.1 or 3.2, Swagger 2, or a GraphQL schema | Routes on your Zuplo gateway, described in OpenAPI 3.1 (3.0 works too), and GraphQL routes |
| What you maintain | The spec, and a short file per tool with the description agents read | Your gateway project’s routes, with MCP settings per route; custom tools are routes with handlers you write |
| Where it runs | Hosted at its own address on sokie.cloud, or on your domain from Pro up | Your gateway, on Zuplo’s edge or dedicated hosting, or self-hosted |
| How MCP clients sign in | OAuth 2.1, with each person approving their own connection; or a public server with no sign-in | An OAuth 2.1 server on every plan, or your own; API keys through a workaround |
| Your API’s credentials | Each caller’s own key, one shared key, or OAuth to your API, per person or shared | Each person’s OAuth, one shared grant, or a shared key. Each person’s own key is on their roadmap. |
| Deploys | From the CLI, the app, or every push to a linked GitHub repository; restore any earlier deploy | From Git: the default branch is production |
| Previews | A preview server for every pull request | A preview environment for every branch, on GitHub, GitLab, Bitbucket or Azure DevOps |
| MCP protocol updates | Every server gets a new MCP version or feature on its next deploy, with nothing to change | 2024-10-07 to 2025-11-25 on every project; 2026-07-28 once you raise the project’s compatibility date to 2026-11-06 |
| Free plan | Hobby: 100,000 tool calls a month and 3 servers, no card | 1,000 tool calls and 100,000 requests a month |
| Paid plans | Pro: $19 a seat a month; $2 per 100,000 calls past your plan | Builder: $25 a month, with 10,000 tool calls. Enterprise by contract. |
| Source | The CLI is Apache-2.0; the service isn’t open source | Not stated on their pages |
What Zuplo does well
- A complete API gateway, so the same policies guard REST calls and tool calls.
- An OAuth 2.1 server included on every plan.
- Previews on four Git hosts, not only GitHub.
- Explicit support for each MCP protocol version.
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 Zuplo’s pages don’t say, the table says so. Spotted something out of date? Tell us and we’ll correct it.