diff --git a/_includes/feature-notes/mcp.mdx b/_includes/feature-notes/mcp.mdx
deleted file mode 100644
index 4ba23733..00000000
--- a/_includes/feature-notes/mcp.mdx
+++ /dev/null
@@ -1,3 +0,0 @@
-:::caution Preview — added in `v1.37.1`
-This is a preview feature. The API may change in future releases.
-:::
diff --git "a/_includes/feature-notes/mcp.mdx\342\200\216" "b/_includes/feature-notes/mcp.mdx\342\200\216"
new file mode 100644
index 00000000..fdab4a11
--- /dev/null
+++ "b/_includes/feature-notes/mcp.mdx\342\200\216"
@@ -0,0 +1,2 @@
+:::info Added in `v1.38`
+:::
diff --git a/docs/weaviate/configuration/mcp-server.mdx b/docs/weaviate/configuration/mcp-server.mdx
index d043d8c9..b1ea89b0 100644
--- a/docs/weaviate/configuration/mcp-server.mdx
+++ b/docs/weaviate/configuration/mcp-server.mdx
@@ -5,7 +5,7 @@ image: og/docs/configuration.jpg
 faq:
   - question: Does Weaviate offer an MCP server?
     answer: >-
-      Yes. Weaviate ships a built-in Model Context Protocol (MCP) server (preview, available from v1.37.1). Enable it with the MCP_SERVER_ENABLED=true environment variable; it runs on the same port as the REST API at /v1/mcp.
+      Yes. Weaviate ships a built-in Model Context Protocol (MCP) server (generally available as of v1.38; introduced in v1.37.1). Enable it with the MCP_SERVER_ENABLED=true environment variable; it runs on the same port as the REST API at /v1/mcp.
   - question: Is the MCP server an external library?
     answer: >-
       No — it's built into the Weaviate Server binary, not a separate package you install. Setting MCP_SERVER_ENABLED=true exposes the MCP endpoint on the same port as the REST API; nothing extra to run or deploy. The separate "Weaviate Docs MCP server" (Kapa-powered, serves documentation to LLMs) is a distinct product.