# 0mcp

0mcp converts an existing API contract into a hosted Model Context Protocol (MCP) server. The upstream API remains the source of truth for business data and authorization.

## How it works

1. Import an OpenAPI 3.x or Swagger 2.0 specification.
2. Choose and configure the operations that should become MCP tools.
3. Test the tools and publish an immutable server revision.
4. Connect an MCP-compatible AI client to the hosted Streamable HTTP endpoint.

## Core capabilities

- **Import OpenAPI:** Generate MCP tools from an OpenAPI 3.x or Swagger 2.0 API specification.
- **Interactive testing:** Test tools with live requests before making them available to AI clients.
- **Authentication pass-through:** Keep authentication, users, permissions, and authorization in the upstream API.
- **Isolated MCP servers:** Create separate servers for products, customers, partners, or internal teams.
- **Production observability:** Monitor health, latency, failures, operational activity, and usage.
- **Versioned publishing:** Publish immutable revisions, roll back, and pause serving independently of configuration changes.

## Security and data handling

- API credentials are relayed ephemerally and are not persisted by 0mcp.
- API request and response payloads are not stored.
- The upstream API continues to enforce its own authentication and authorization.
- Operational metadata such as request status, latency, route, errors, and usage may be retained for reliability and metering.
- Tool-level controls include risk labels, sensitive-input markers, timeouts, response-size limits, and redirect limits.

## Supported MCP capabilities

Published server revisions can expose tools, static text resources, and parameterized text prompts over Streamable HTTP.

Canonical source: https://0mcp.io/
