About Weaviate MCP Server
The standalone Weaviate MCP server is deprecated and superseded by the MCP server built into Weaviate itself. Setting MCP_SERVER_ENABLED=true exposes it at /v1/mcp on the REST API port, using the existing API-key authentication and RBAC.
Key features
- 01Built into the Weaviate binary
- 02Enabled through a single environment variable
- 03Shares the REST API port and API-key authentication
- 04Respects RBAC permissions
Use cases
- 01Inspecting collection schema configuration
- 02Listing tenants in a multi-tenant collection
- 03Running hybrid vector and keyword search
- 04Creating or updating objects
MCP support
This is Weaviate's built-in MCP server, exposing tools for collection config inspection, tenant listing, hybrid search and object upsert to MCP clients.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEWeaviate MCP server
This standalone server is deprecated. The Weaviate Model Context Protocol (MCP) server is now built into Weaviate itself — there is nothing to install or run separately.
Use the built-in MCP server
Weaviate ships an MCP server inside the main weaviate/weaviate binary, available as a preview from v1.37.1 onward. Enable it with a single environment variable:
MCP_SERVER_ENABLED=true
It listens on the same port as the Weaviate REST API at /v1/mcp, authenticates via the existing API-key flow, and respects RBAC.
Tools exposed
| Tool | Purpose |
|---|---|
weaviate-collections-get-config | Inspect collection schemas |
weaviate-tenants-list | List tenants in a multi-tenant collection |
weaviate-query-hybrid | Hybrid (vector + keyword) search |
weaviate-objects-upsert | Create or update objects |
Documentation
- Setup, environment variables, RBAC permissions, and per-tool reference: docs.weaviate.io/weaviate/configuration/mcp-server
- The MCP standard: modelcontextprotocol.io
- Weaviate repo (issues, feature requests): github.com/weaviate/weaviate
About this repository
Earlier versions of this repo contained a standalone Go implementation of an MCP server that wrapped the Weaviate REST API. That implementation has been superseded by the built-in server and is no longer maintained. The history is preserved in git for reference; for the previous source, see the commits before this notice.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.