mcpmint

Convert OpenAPI and Swagger to an MCP server

Import an API contract, choose tools, and export a TypeScript or Python Model Context Protocol server with mcpmint.

What mcpmint generates

mcpmint turns an API contract into source code for a Model Context Protocol (MCP) server. MCP lets compatible AI clients discover tools and call them through a standard interface. Your generated server translates tool arguments into upstream HTTP requests; the upstream API remains responsible for its own authorization and business rules.

Import OpenAPI 3.x or Swagger 2.0 as JSON or YAML. mcpmint normalizes operations, parameters, request bodies, responses and authentication information. Feature support varies by operation: inspect the capabilities panel and validation warnings before using generated code.

From contract to source code

Files and pasted specifications are processed locally in a dedicated browser worker. URL import asks the mcpmint server to fetch the URL you provide. External references are never fetched automatically; bundle referenced documents into a single specification first.

  1. Open Import and choose a JSON/YAML file, paste a contract, or enter a public specification URL.
  2. Review the import warnings and select the endpoints you want to expose as tools. The recommended preset favors supported read operations.
  3. Choose TypeScript with the MCP TypeScript SDK or Python with FastMCP. Configure the server name, upstream authentication and MCP transport.
  4. Inspect a generated preview and the Trust Scan. A red scan requires explicit acknowledgement before download.
  5. Download the ZIP, inspect the generated README and source, install dependencies, and configure credentials locally.

Review schema and authentication details

Recursive local references are retained as finite schema references. Complex schemas, content negotiation and unsupported authentication combinations may require manual changes. A successful import or a green scan is not a promise that every upstream request is correct.

Upstream API authentication and access to your MCP server are separate settings. Do not embed API keys in a specification, tool description or portable project file. Supply real credentials to the generated server through its documented environment variables.