← All guides

Implementation guide

How OpenAPI operations become MCP tools

0mcp imports an OpenAPI 3.x or Swagger 2.0 document, lets the operator select the operations that should be available to agents, and publishes those operations as MCP tools. The API remains the execution and authorization boundary.

Mapping workflow

Treat the imported contract as a starting point, not an automatic permission grant.

  • Validate the specification and security schemes
  • Select only operations intended for agent use
  • Review tool names, descriptions, inputs, timeouts, and safety controls
  • Test against the upstream API before publishing

What remains upstream

The MCP layer does not replace the application behind the API.

  • Business logic and data
  • User authentication and authorization
  • API validation and rate limits
  • Application-level audit records

For complete product instructions, read the 0mcp documentation. Protocol reference: Model Context Protocol specification.

Published and last reviewed: July 13, 2026