Merge pull request #147 from jlowin/openapi

Support openapi 3.0 and 3.1

Author: jlowin

docs/patterns/openapi.mdx

@@ -7,6 +7,8 @@ icon: code-branch
 
 If you have existing REST APIs documented with the OpenAPI Specification (OAS), FastMCP can automatically generate MCP tools, resources, and resource templates directly from that specification. This provides a quick way to make your existing HTTP APIs accessible to MCP clients and LLMs.
 
+FastMCP supports both OpenAPI 3.0 and 3.1 specifications for maximum compatibility with existing API definitions.
+
 ## The Goal: API -> MCP Server
 
 The core idea is to map OpenAPI paths and operations (like `GET /users/{id}` or `POST /orders`) to their corresponding MCP components: