Apiosk Connect vs Sezzlee OpenAPI
Apiosk Connect is an MCP server published by obcraft. Marketplaces we read that list it: 1 (Official MCP Registry). Sezzlee OpenAPI is an MCP server published by sezzlee. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Apiosk Connect |  Sezzlee OpenAPI |
|---|---|---|
| Official MCP Registry | Listed Version: 1.7.0 Downloads/month (npm): 377 Downloads/week (npm): 34 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 Downloads/month (npm): 897 Downloads/week (npm): 897 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Apiosk Connect | Sezzlee OpenAPI |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Remote server (mcp.apiosk.com/mcp) | On your machine (@sezzlee/openapi-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 2 | 1, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/obcraft/apiosk-mcp | github.com/sezzlee/mcp |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
| Endpoint at the last check (differs) | Responded 34 h ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Apiosk Connect
Discover, pay for, execute, and publish APIs through Apiosk.
Sezzlee OpenAPI
Expose an OpenAPI document to agents as a search-first tool catalog over your existing API.
How to run each
Apiosk Connect As a remote MCP server
claude mcp add --transport http apiosk-mcp https://mcp.apiosk.com/mcpRequires: APIOSK_CONNECT_TOKEN (secret), APIOSK_PRIVATE_KEY (secret)
Sezzlee OpenAPI As a local MCP server: npm package
claude mcp add --env "SEZZLEE_OPENAPI_CONFIG=<YOUR_SEZZLEE_OPENAPI_CONFIG>" --transport stdio openapi -- npx -y @sezzlee/openapi-mcpRequires: SEZZLEE_OPENAPI_CONFIG
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Apiosk Connect has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Apiosk Connect asks for
APIOSK_CONNECT_TOKEN (secret)APIOSK_PRIVATE_KEY (secret)
Only Sezzlee OpenAPI asks for
SEZZLEE_OPENAPI_CONFIG
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Apiosk Connect · What it can do: Sezzlee OpenAPI · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.