The short answer
0mcp and Smithery both help teams connect AI clients to MCP servers, but they start at different points in the workflow. 0mcp is positioned around turning an existing API definition into a hosted MCP server. Smithery is currently centered on publishing, discovering, connecting to, and observing MCP servers that already exist, with managed authentication and connection infrastructure around them.
That distinction matters for SaaS teams. If the source of truth is an OpenAPI or Postman definition and the team wants the MCP layer generated and operated for them, 0mcp is the more direct workflow. If the team already has MCP server code, a public MCP endpoint, or an MCPB bundle and wants distribution, managed OAuth, client connectivity, or a registry presence, Smithery may be a better fit. Smithery's publishing documentation and server publish API do not publicly confirm a first-party OpenAPI, Swagger, or Postman importer, so that capability should not be assumed.
Quick comparison
| Capability | 0mcp | Smithery |
|---|---|---|
| MCP server creation | Create a hosted MCP server from an API definition. | Publish an existing MCP server, URL, hosted module, or MCPB bundle. |
| API or OpenAPI import | Swagger 2.0, OpenAPI 3.0/3.1, and Postman collections are supported inputs. | OpenAPI, Swagger, and Postman import are Not publicly confirmed in current first-party materials. |
| Managed MCP hosting | Managed hosted infrastructure for the generated server. | Hosted JavaScript module releases are documented; URL publishing is bring-your-own hosting, and MCPB is local distribution. |
| Ongoing maintenance | 0mcp manages the generated server configuration, hosting, versions, logs, and analytics; the source API remains the customer's responsibility. | Smithery manages Gateway, connection/auth surfaces, release and runtime observability; the customer maintains an upstream server for the external-URL path. |
| Custom MCP domain | Custom subdomains are documented for eligible paid plans. | Custom customer domains, DNS mapping, and white-label endpoints are Not publicly confirmed. |
| Authentication | API key, Bearer token, and OAuth pass-through to the upstream API. | Managed OAuth, configuration values through headers/query parameters, encrypted write-only credentials, and scoped service tokens. |
| Versioning | Version history with review and restore behavior. | Release history, release logs, and resume operations; explicit rollback is Not publicly confirmed. |
| Logs and analytics | Usage logs and analytics for hosted MCP activity. | Runtime logs, release logs, tool-call/usage analytics, and a public status surface. |
| White-label branding | MCP name and domain controls; logo customization is not currently available. | Server metadata and icons are supported; white-label branding and Smithery-brand removal are Not publicly confirmed. |
| Pricing model | 14-day free trial followed by Starter/Pro quota-based plans. | Hobby free, Pay as you Go at $10/month with RPC credits, and Custom pricing with custom limits, SLA, and Slack support. |
What is Smithery?
Smithery describes itself as an MCP catalog and platform for publishing integrations so users can discover, try, and connect to them. Its introduction targets chatbots, background agents, and AI copilots; its publishing overview and Connect documentation describe managed OAuth, token refresh, encrypted write-only credentials, persistent connections, service tokens, and a CLI.
Its current publish paths are a public Streamable HTTP URL that Smithery Gateway proxies, a local MCPB bundle for client execution, or a hosted JavaScript module release through the API. The API example returns a Smithery endpoint such as https://slug.run.tools.
Smithery's documentation index exposes APIs for servers, releases, namespaces, organizations, connections, tokens, runtime logs, and health checks. Its homepage says it is now part of Arcade.dev. The privacy notice identifies Clavia, Inc. doing business as Smithery and was last updated June 20, 2025; the current contracting entity and post-change legal terms are Not publicly confirmed.
What is 0mcp?
0mcp is an API-to-MCP platform for SaaS teams. Its documentation covers Swagger 2.0, OpenAPI 3.0/3.1, and Postman collections, while the OpenAPI guide describes selecting and exposing API operations as MCP tools, resources, and prompts. The resulting server is hosted over Streamable HTTP, with authentication pass-through, versioning, playground testing, logs, analytics, and custom subdomains documented in the current product baseline.
0mcp's comparison advantage is the path from an API definition to a managed MCP endpoint, rather than the breadth of a public MCP catalog.
0mcp vs Smithery: MCP server creation
The creation workflow is the clearest difference. In 0mcp, the customer begins with an API definition. The OpenAPI guide and Postman guide document validation, operation selection, and shaping the generated MCP capabilities.
Smithery's current publish workflow begins later. The customer supplies a working MCP server URL, a local MCPB bundle, or—through the publish API—a hosted JavaScript module. Smithery scans a published server to extract tools, prompts, and resources for its server page and connection experience. That is a publishing and distribution workflow, not proof of API-to-MCP generation.
Smithery also provides configuration plumbing: its Session Configuration documentation shows how a prebuilt server can define a schema, receive a generated form, and map values to headers or query parameters, including an upstream Authorization header. This helps configure an existing MCP server; it is not an API importer.
0mcp documents a playground for testing tools, resources, and prompts. Smithery documents registry-server mock mode in its Create connection API, while a 2025 Smithery MCP explainer mentions a server-page tool playground; current parity is Not publicly confirmed.
Hosting and deployment comparison
0mcp manages hosting for the generated MCP server; the customer remains responsible for the underlying API and its availability.
Smithery has deployment modes with different ownership boundaries:
| Smithery path | Who supplies the runtime? | What Smithery documents | What remains unknown |
|---|---|---|---|
| Hosted JavaScript module | The customer supplies the module/release. | The API accepts a hosted module release and returns a Smithery endpoint. | Runtime isolation, regions, autoscaling, dependency policy, and operational SLA details are Not publicly confirmed. |
| External Streamable HTTP URL | Customer-hosted upstream server. | Smithery Gateway proxies the upstream server and handles publishing/metadata/authentication surfaces. | The customer's hosting, uptime, dependencies, and API behavior remain their responsibility. |
| MCPB bundle | Client/local environment. | Smithery distributes a local stdio bundle for clients to download and run. | Centralized production hosting and managed uptime for the local process are not implied. |
| Uplink | Customer's local machine or development host. | Smithery CLI maintains a secure tunnel and forwards requests. | Smithery explicitly describes Uplink as dependent on the host's availability, not as a production hosting solution. |
Smithery's Publish API example uses the run.tools domain. A customer-owned endpoint, CNAME/TXT setup, or custom certificate workflow is Not publicly confirmed; publishing an already-hosted URL is different from attaching a customer domain to Smithery infrastructure, as the Uplink documentation also makes clear.
MCP server maintenance comparison
After deployment, 0mcp's managed model is designed to keep the generated server aligned with the selected API definition while exposing version history, logs, and analytics. The customer's main ongoing responsibility is the source API: its availability, authentication policy, schema quality, and business behavior.
Smithery documents maintenance surfaces rather than a broad managed API-maintenance contract: Gateway behavior, metadata scanning, connection lifecycle, OAuth UI/refresh, credential storage, runtime logs, release logs, and analytics. For an external URL, the customer maintains the upstream server and hosting. Automatic dependency updates, API-drift monitoring, security patching, rollback guarantees, backup/DR commitments, and a general maintenance SLA are Not publicly confirmed.
Smithery does provide release history and streaming release logs. Its API also has a resume operation for paused releases. That is useful operational control, but an explicit rollback action is Not publicly confirmed. The Custom pricing card lists an uptime SLA, but the public page does not state the percentage, exclusions, or response commitments.
Custom domain and branding comparison
0mcp documents custom MCP subdomains using DNS verification, CNAME/TXT records, and automatic HTTPS/SSL after activation in its Custom Domain guide. Custom domains are paid-plan functionality: the current product baseline is Starter with zero custom domains and Pro with unlimited custom domains. 0mcp currently controls the MCP name and domain; logo customization is not available.
Smithery documents Smithery-owned endpoint formats and server metadata controls in its Update a server API. A server owner can update display name, description, homepage, repository URL, backlink, license, icon URL, and listed/unlisted visibility. Those controls support a recognizable server page, but they are not the same as white-labeling. Custom domains, customer DNS mapping, custom SSL, dashboard/login domains, custom colors, and removal of Smithery branding are Not publicly confirmed.
Authentication and security comparison
0mcp supports API-key, Bearer-token, and OAuth pass-through to the upstream API, with its Authentication Model and Trust & Data Handling pages describing the model and retention. Its public positioning does not claim formal SOC 2 certification or a contractual uptime SLA.
Smithery emphasizes managed connection security. Its Connect documentation describes OAuth flows, token refresh, encrypted write-only credentials, and service tokens; Token Scoping covers namespaces, resources, operations, metadata, and TTL. Uplink documents end-to-end TLS between Smithery and the CLI. Smithery's configuration system can forward values to upstream headers, including an Authorization header, but a general upstream Bearer-token pass-through guarantee is Not publicly confirmed as a separate product feature.
Smithery's privacy notice says it may collect customer content, server-related content, account/contact information, usage/device information, and support data. An MCP-specific retention schedule, data residency commitment, SSO/SAML/SCIM, private networking, formal administrative audit logs, and SOC 2/ISO certification are Not publicly confirmed in the reviewed first-party materials. The public Smithery status page is useful for operational visibility, but its rolling uptime display should not be read as a contractual SLA.
Pricing comparison
The Smithery pricing page uses RPCs as its usage unit. 0mcp uses quota-based Starter and Pro plans; these units should not be treated as equivalent without testing a real workload.
| Pricing dimension | 0mcp | Smithery |
|---|---|---|
| Free entry | 14-day free trial | Hobby: free |
| Paid plans | Starter and Pro quota-based plans | Pay as you Go: $10/month; Custom: contact sales |
| Usage unit | Request-capacity quotas | RPCs: 50K/month on Hobby; 100K/month on Pay as you Go; after the $10 credits, $0.10 per 1,000 RPCs |
| Namespaces / workspace limits | Plan-based limits; verify the current pricing page for exact values | 3 namespaces on Hobby; 100 on Pay as you Go; Custom rate limits on Custom |
| Custom domains | Starter: 0; Pro: unlimited | Not publicly confirmed |
| Support / SLA | Public documentation and support contact; no formal SLA in the current baseline | Custom includes Slack Support and an uptime SLA; details are Not publicly confirmed |
| Users / server caps | Plan-based limits; exact current user/server caps should be verified | Not publicly confirmed on the public pricing page |
| Annual, refund, and cancellation terms | Not publicly confirmed in this comparison | Not publicly confirmed on the public pricing page |
The 0mcp pricing page and Smithery's public pricing page should be checked together against expected tool calls, server count, persistent connections, namespaces, log retention, and domain requirements. Headline prices alone are not a like-for-like comparison.
Feature comparison table
| MCP-relevant feature | 0mcp | Smithery |
|---|---|---|
| Existing API definition input | Swagger 2.0, OpenAPI 3.0/3.1, Postman. | Not publicly confirmed as a first-party import path. |
| Existing MCP server input | Not the primary creation workflow. | Public URL, hosted module release, or MCPB bundle. |
| Generated tools/resources/prompts | Generated from selected API operations. | Scanned or supplied as metadata from the published MCP server. |
| Remote transport | Streamable HTTP. | Streamable HTTP for URL publishing; hosted endpoints documented; Uplink supports local HTTP. |
| Local stdio | Not the current hosting model. | MCPB local distribution and Uplink support. |
| OAuth | Upstream pass-through. | Managed OAuth and token refresh. |
| API-key configuration | Pass-through to the upstream API. | Configuration values through headers/query parameters; encrypted write-only credentials. |
| Playground/testing | Documented playground. | Mock/try flows; current dedicated playground scope not publicly confirmed. |
| Release/version control | Version review and restore documented. | Release history/logs; rollback not publicly confirmed. |
| Runtime logs | Documented. | Documented with filters and invocation grouping. |
| Analytics | Documented usage analytics. | Tool-call and usage analytics documented. |
| Custom domain | Eligible paid plans; DNS verification and TLS. | Not publicly confirmed. |
| White-label | Logo customization not currently available. | Icon/metadata controls; white-label not publicly confirmed. |
| Integrations | API-definition workflow and client-neutral MCP endpoint. | CLI, REST/API, TypeScript SDK, Vercel AI SDK, and generic MCP clients. |
| Support | Public documentation and support contact. | Documentation/Discord; Custom lists Slack Support. |
Where 0mcp may be a better fit
0mcp may be a better fit when:
- The team has a reliable Swagger, OpenAPI, or Postman definition and wants it to remain the source of truth for a hosted MCP server without first implementing MCP code.
- Custom MCP subdomains, DNS verification, and automatic TLS are part of the customer-facing product experience.
- The team needs version review/restore, a playground, usage logs, analytics, and pass-through authentication to the original API.
Where Smithery may be a better fit
Smithery may be a better fit when:
- The team owns an MCP server, public Streamable HTTP endpoint, or MCPB bundle and values catalog distribution.
- Managed OAuth, persistent connections, service tokens, a CLI, namespaces, or local Uplink/MCPB workflows are central requirements.
- The team wants to publish an existing server while retaining control of its upstream hosting for the external-URL path.
Verify domains, compliance, retention, RBAC, and hosted-release export before buying.
Which platform should you choose?
- Choose 0mcp if your starting point is an API specification and you want a hosted API-to-MCP workflow with custom subdomains, versioning, playground testing, and operational analytics.
- Choose Smithery if your starting point is already-built MCP code or a bundle and you want catalog distribution, managed connections/OAuth, client tooling, or Uplink/local MCP support.
- Consider building in-house if you need networking, data residency, source ownership, runtime isolation, compliance controls, or migration guarantees that neither public comparison set confirms in full.
Migration and switching considerations
Moving from 0mcp to Smithery requires an MCP server, a compatible Streamable HTTP endpoint or MCPB bundle, recreated metadata/configuration, and mapped OAuth/API-key behavior; an API definition alone is not the same migration asset.
Moving from Smithery to 0mcp requires the underlying API definition. A customer-hosted external URL preserves the upstream API/code, but hosted JavaScript source/configuration export and self-host migration are Not publicly confirmed. Smithery documents namespace transfer and MCPB bundle download for the latest successful stdio release, which is partial portability.
Before switching, verify the contract entity, retention, export, rollback, networking, SSO, domains, support, and RPC billing.
Final recommendation
The choice should follow the starting asset. For an API-first SaaS product that wants to expose existing operations as a hosted MCP server, 0mcp provides the more direct documented path. For a team that already has MCP code or a bundle and wants discovery, distribution, managed OAuth, connection handling, or local tooling, Smithery may be the better fit.
Validate domains, security, support, rollback, export, and usage limits before production.
Start with 0mcp
If your product already has an API definition, start with 0mcp's 14-day free trial and test the import, generated capabilities, authentication, playground, hosted endpoint, logs, and domain workflow against a representative API.