Weaviate MCP Server for Claude

Overview

The Weaviate MCP Server lets Claude work with a Weaviate vector database over the Model Context Protocol. As of Weaviate v1.37.1, the MCP server is built into Weaviate itself (the earlier standalone server is deprecated): enable it on your instance and Claude connects to the /v1/mcp endpoint to run hybrid search, inspect collection configuration, list tenants, and upsert objects.

Key capabilities

The built-in server exposes four tools:

• weaviate-query-hybrid — run a hybrid (vector + keyword) query over a collection.
• weaviate-collections-get-config — read a collection's configuration.
• weaviate-tenants-list — list tenants for a multi-tenant collection.
• weaviate-objects-upsert — insert or update objects in a collection.

How it compares

Several vector-database MCP servers give Claude retrieval over embeddings; they differ in how they are deployed and connected:

Choose the Weaviate server when your vectors already live in Weaviate and you want native hybrid search; the Pinecone and Qdrant servers cover their own stores.

Installation

First enable the MCP server on your Weaviate instance (v1.37.1+) by setting the environment variable MCP_SERVER_ENABLED=true. It is then served at /v1/mcp on the same port as the Weaviate REST API.

Claude Code

claude mcp add --transport http weaviate https://<your-weaviate-host>/v1/mcp

Claude Desktop

{
  "mcpServers": {
    "weaviate": {
      "url": "https://<your-weaviate-host>/v1/mcp",
      "type": "http"
    }
  }
}

Requirements

• A Weaviate instance on v1.37.1 or later (self-hosted or Weaviate Cloud).
• MCP_SERVER_ENABLED=true set on that instance.
• A Weaviate API key whose RBAC role covers the collections Claude should access.
• An MCP client (Claude Code or Claude Desktop).

Security

• The server runs inside Weaviate and honors its existing API-key authentication and RBAC.
• Scope the API key to least privilege — read-only where Claude only needs to query.
• The weaviate-objects-upsert tool writes data; restrict write access accordingly.
• Treat the endpoint URL and API key as secrets.

Source Verification Notes

Verified on 2026-06-17:

• Weaviate's documentation (docs.weaviate.io/weaviate/configuration/mcp-server) describes the built-in MCP server, the MCP_SERVER_ENABLED flag, the /v1/mcp endpoint, API-key/RBAC auth, and the four tools listed above.
• The former standalone repository github.com/weaviate/mcp-server-weaviate states it is deprecated in favor of the built-in server.
• Claude Code's MCP documentation describes the HTTP connector setup used here.