Weaviate MCP Server

Name: Weaviate MCP Server
Author: weaviate

@weaviate

Repository Homepage

About Weaviate MCP Server

MCP (Model Context Protocol) server for Weaviate

Basic information

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Weaviate MCP Server?

The Weaviate MCP Server is a built-in Model Context Protocol server inside the Weaviate vector database binary, available as a preview from version 1.37.1. It exposes tools to inspect collection schemas, list tenants, perform hybrid search, and upsert objects, authenticating via the existing API-key flow and respecting RBAC.

How to use Weaviate MCP Server?

Enable it by setting the environment variable MCP_SERVER_ENABLED=true. The server listens on the same port as the Weaviate REST API at /v1/mcp. No separate installation is required.

Key features of Weaviate MCP Server

Built directly into the Weaviate binary (no separate process).
Authenticates via existing API key flow.
Respects RBAC permissions.
Exposes four tools: hybrid search, object upsert, collection config, tenant list.
Listens on the same port as the REST API.

Use cases of Weaviate MCP Server

Inspect collection schemas using the weaviate-collections-get-config tool.
List tenants in a multi-tenant collection with the weaviate-tenants-list tool.
Perform hybrid (vector + keyword) search via the weaviate-query-hybrid tool.
Create or update objects using the weaviate-objects-upsert tool.

FAQ from Weaviate MCP Server

Do I need to install anything separately to use the MCP server?

No. The MCP server is built into the Weaviate binary from version 1.37.1 onward. Just enable it with the MCP_SERVER_ENABLED=true environment variable.

What are the runtime requirements?

It requires Weaviate version 1.37.1 or later. No other dependencies are needed.

How does authentication work?

The server authenticates requests using the same API-key flow already configured for your Weaviate instance, and it respects RBAC.

Where does the MCP server listen?

It listens on the same port as the Weaviate REST API, at the path /v1/mcp.

Is this feature stable?

The built-in MCP server is currently available as a preview feature. For detailed setup, environment variables, RBAC permissions, and per-tool reference, see the Weaviate documentation.