From 99a5eb136dbed1903d08edab279600c9b44bee5a Mon Sep 17 00:00:00 2001
From: Jeremiah Lowin <153965+jlowin@users.noreply.github.com>
Date: Sun, 13 Apr 2025 22:39:59 -0400
Subject: [PATCH] Update openapi.mdx

---
 docs/patterns/openapi.mdx | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/patterns/openapi.mdx b/docs/patterns/openapi.mdx
index 166b5d89a..1767700c2 100644
--- a/docs/patterns/openapi.mdx
+++ b/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: