--- title: "Weaviate built-in MCP: review, setup & limitations · Undominated.ai" canonical: https://undominated.ai/mcp-servers/weaviate/ description: "Inspect collections, search vector and keyword data, and optionally upsert objects through Weaviate’s built-in MCP endpoint." --- # Weaviate built-in MCP: review, setup & limitations · Undominated.ai > Inspect collections, search vector and keyword data, and optionally upsert objects through Weaviate’s built-in MCP endpoint. [← Explore all mcp servers](/mcp-servers/) VECTOR DATA MANAGEMENT / Weaviate # Weaviate built-in MCP Inspect collections, search vector and keyword data, and optionally upsert objects through Weaviate’s built-in MCP endpoint. See setup guidance ↓Original source ↗ SOURCE REVIEW Reviewed 2026-09-21 Evidence 7 linked sources Publisher Weaviate Licence BSD-3-Clause (built-in MCP source outside wl) ↗ Revision 2eda1edd2b50 Read what was—and wasn’t—checked ↓ “Weaviate implements this as a Streamable HTTP server that runs on the same port as the main Weaviate REST API.” Weaviate · upstream description ↗ Our analysis follows below. 01 / THE REASONING ## Why this made the selection. - Lives in the database server and reuses its authentication and role permissions. - Collection and tenant inspection support retrieval against existing Weaviate data. ### A good fit for - Query a Weaviate collection from an agent. - Perform explicitly approved object updates with a restricted database identity. ### Weigh up before choosing - The old standalone MCP repository is deprecated; this entry covers the built-in server. - Self-hosted MCP is disabled initially and defaults to read-only when enabled; Weaviate Cloud enables MCP and write access by default. - Upsert replaces objects rather than merging properties, and auto-schema can create fields or collections. Review full objects before writing. 02 / THE REVIEW RECORD ## What we actually inspected. Source review has boundaries. A clear record is more useful than a “safe” badge. ### Material inspected - Current Weaviate configuration/tool reference and standalone repository migration notice. - Pinned Go MCP server, authorization wrapper, config and object-upsert handler. - Repository licence location rules and BSD licence. ### Our findings - The endpoint is /v1/mcp on the REST API host. RBAC is enforced when tools are called, not by hiding every unauthorized tool in tools/list. - The inspected MCP source is outside wl and covered by BSD-3-Clause; that does not extend to separately licensed Weaviate features. ### Not established by this review - Server launch, authenticated tool calls, and release-to-source parity were not tested. The review applies to the material and revision named here. A newer upstream release can change its behavior. 03 / PUT IT TO WORK ## Connect a server deliberately. Upstream setup instructions ↗ - Use a Weaviate deployment that includes the built-in server; do not install the deprecated standalone package. - For self-hosting, enable MCP_SERVER_ENABLED and leave write access disabled unless needed. In Cloud, configure Enable MCP Read-Only if the agent should only read. - Connect to the REST host with /v1/mcp and a suitable API key using the official client-specific instructions. ### Before you start - A supported Weaviate deployment. - An API key with appropriate MCP and data permissions; transport-capable client. ### Compatibility Claude Code · Cursor · VS Code · Streamable HTTP clients ### Implementation Go ### Transports Streamable HTTP ### Database API key and RBAC - Reads collection configuration, tenant metadata and search results. - Upserts objects when write access and the key’s permissions allow it; auto-schema can extend the schema. ### Cost model Self-hosting or Weaviate Cloud usage, embedding services and the AI client have separate costs. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - Weaviate built-in MCP setup and scope ↗ Checked 2026-09-21 https://docs.weaviate.io/weaviate/configuration/mcp-server Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review - Deprecated standalone Weaviate server notice ↗ Checked 2026-09-21 https://raw.githubusercontent.com/weaviate/mcp-server-weaviate/main/README.md Supports: limitations, review - Built-in Weaviate MCP server ↗ Checked 2026-09-21 https://raw.githubusercontent.com/weaviate/weaviate/2eda1edd2b5097e151c1f5a60b3c9a22e8d58fe1/adapters/handlers/mcp/server.go Supports: language, transports, review - Weaviate MCP authorization ↗ Checked 2026-09-21 https://raw.githubusercontent.com/weaviate/weaviate/2eda1edd2b5097e151c1f5a60b3c9a22e8d58fe1/adapters/handlers/mcp/auth/auth.go Supports: access, review - Weaviate object upsert handler ↗ Checked 2026-09-21 https://raw.githubusercontent.com/weaviate/weaviate/2eda1edd2b5097e151c1f5a60b3c9a22e8d58fe1/adapters/handlers/mcp/create/objects_upsert.go Supports: access, review - Weaviate licence scope by path ↗ Checked 2026-09-21 https://raw.githubusercontent.com/weaviate/weaviate/2eda1edd2b5097e151c1f5a60b3c9a22e8d58fe1/LICENSE Supports: license - BSD terms for built-in MCP source ↗ Checked 2026-09-21 https://raw.githubusercontent.com/weaviate/weaviate/2eda1edd2b5097e151c1f5a60b3c9a22e8d58fe1/LICENSE-BSD Supports: license KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### Pinecone MCP ↗ Search Pinecone documentation and manage or query indexes that use integrated embeddings.](/mcp-servers/pinecone/)[### Chroma MCP ↗ Lets an assistant create and query Chroma collections through local, HTTP or Chroma Cloud database connections.](/mcp-servers/chroma/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)