Turn your API into a hosted MCP server

Connect an OpenAPI document, REST API, or Postman collection,
choose what AI clients can access, and publish a managed MCP endpoint in minutes.

Create a server · Quick start · Pricing · Support

What is 0mcp?

0mcp turns an existing API into a hosted Model Context Protocol server. Start with an OpenAPI 3.x or Swagger 2.0 document, configure REST operations directly, or import a Postman Collection v2 document. Select the operations you want to expose, and 0mcp converts them into tools that compatible AI clients can discover and call.

You do not need to change your API or maintain a separate MCP service. Your API remains responsible for its data, business logic, authentication, and authorization.

flowchart LR
    A[OpenAPI document] -->|Import| B[0mcp]
    B -->|Publish| C[Hosted MCP server]
    D[AI client] -->|MCP request| C
    C -->|HTTP request| E[Your API]
    E -->|Response| C
    C --> D

Loading

From API to MCP in six steps

Step	What you do
1. Create	Sign in to the 0mcp dashboard and create a server.
2. Connect	Import an OpenAPI or Swagger document, configure REST operations directly, or import a Postman collection.
3. Choose	Select the operations that should become MCP tools. Rename them or improve their descriptions when needed.
4. Publish	Publish a version to make the server available at its hosted endpoint.
5. Test	Use the Playground to test read-only tools and verify authentication before allowing write operations.
6. Connect	Copy the generated setup for your AI client, add credentials securely, and reconnect the client.

For the complete walkthrough, follow the quick start.

What you can build

Tools - let AI clients perform actions through your API

Each selected API operation becomes an MCP tool with a name, description, inputs, request schema, response schema, and authentication requirements. You can disable sensitive operations, set timeouts and response-size limits, and control redirects without changing the upstream API.

Learn about tools

Resources - provide stable, read-only context

Share documentation, policies, FAQs, pricing information, or other reference content through stable resource URIs. Resources can contain text, Markdown, JSON, YAML, or base64-encoded file data.

Learn about resources

Prompts - give clients reusable instructions

Create prompt templates for repeatable workflows such as summarizing support cases, drafting replies, reviewing logs, or generating release notes. Arguments let clients reuse one prompt with different values.

Learn about prompts

Built for controlled releases

• Draft safely. Changes stay private until you publish a version.
• Test before release. The Playground runs the currently published tools, resources, and prompts.
• Roll back quickly. Publish an earlier version to restore a known configuration.
• Pause serving. Stop incoming requests without deleting the server or changing its published version.
• Monitor usage. Analytics show trends, while logs help you investigate individual events.
• Use your own domain. Point a stable hostname such as mcp.example.com to your server.

Explore operations guides

• Playground
• Versioning and rollback
• Analytics
• Logs and privacy
• Custom domains

Connect your preferred AI client

0mcp works with any MCP client that supports remote Streamable HTTP. Your server is not tied to a specific AI application, editor, or agent framework.

To connect a compatible client:

1. Publish a version of your MCP server.
2. Copy the hosted endpoint from your server's Setup page.
3. Add the endpoint to your client's MCP configuration.
4. Configure any authentication headers or environment variables required by your upstream API.
5. Reconnect the client so it can discover your published tools, resources, and prompts.

The Setup page provides ready-to-use configuration for popular clients. You can use the same endpoint with any other MCP-compatible client that supports the transport and authentication requirements. See the client setup overview for details.

For current protocol-era behavior, see MCP 2026-07-28 compatibility.

Your credentials stay with the caller

0mcp uses pass-through authentication. The MCP client supplies the Bearer token or API key required by your API, and 0mcp forwards it for that request. Your upstream API makes the final authorization decision.

0mcp does not store:

• Bearer tokens, API keys, or authentication headers
• Request bodies or response bodies
• Playground credentials as activity data

Operational records contain only the details needed to understand usage and failures, such as timestamps, capability names, status codes, response times, and data sizes.

Warning

Review tools that create, update, delete, send, or charge data before publishing them. Test with limited credentials and keep secrets out of shared configuration files.

Supported API sources

Source	Availability	Next step
OpenAPI 3.x	Available	Prepare an OpenAPI document
Swagger 2.0	Available	Review import requirements
Direct REST API conversion	Available	Configure REST operations
Postman Collection v2 import	Available	Import a Postman collection
GraphQL-to-MCP conversion	Coming soon	Review GraphQL status

Find your path

I am new to MCP

1. Read What is MCP?.
2. See how 0mcp connects a client to your API.
3. Follow the quick start with one or two read-only operations.

I am preparing my first production server

1. Give every imported operation a clear, unique operationId.
2. Expose only the operations clients need.
3. Verify the authentication model.
4. Test with limited credentials in the Playground.
5. Publish a version and reconnect your client.
6. Watch Analytics and Logs after release.

Something is not working

• Import rejected? Check Invalid OpenAPI.
• Client cannot connect? Follow MCP connection issues.
• Requests return 401 or 403? Review Authentication errors.
• Server connects but tools are missing? Check Tool discovery problems.

Frequently asked questions

Do I need to change my existing API?

No. 0mcp provides an MCP-compatible interface over your API. Your existing endpoints, business rules, and authorization remain in place.

Can I expose only selected endpoints?

Yes. You decide which imported operations become tools, and you can disable a tool later. Leave internal, administrative, payment, and other sensitive operations out unless clients need them.

When do my changes become live?

Only when you publish a version. Draft edits do not change the live endpoint. Clients may need to reconnect before they discover an updated capability list.

Can I try 0mcp without a credit card?

Yes. You can explore 0mcp without a credit card. Visit the pricing page for current plans, allowances, and prices.

Read the complete FAQ for answers about servers, clients, security, usage, and billing.

Get started

Create your first hosted MCP server at 0mcp.io, or begin with the quick-start guide.

Need help? Email hello@0mcp.io.