Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions _includes/feature-notes/mcp.mdx

This file was deleted.

2 changes: 2 additions & 0 deletions _includes/feature-notes/mcp.mdx‎
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
:::info Added in `v1.38`
:::
2 changes: 1 addition & 1 deletion docs/weaviate/configuration/mcp-server.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading