loading…
Search for a command to run...
loading…
An MCP Server to connect to your Weaviate collections as a knowledge base as well as using Weaviate as a chat memory store.
An MCP Server to connect to your Weaviate collections as a knowledge base as well as using Weaviate as a chat memory store.
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.
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.
| 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 |
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.
Run in your terminal:
claude mcp add weaviate-mcp-server-weaviate -- npx pro tip
Just installed weaviate/mcp-server-weaviate? Say to Claude: "remember why I installed weaviate/mcp-server-weaviateand what I want to try" — it'll save into your Vault.
how this works →CSA PROJECT - FZCO © 2026 IFZA Business Park, DDP, Premises Number 31174 - 001
Security
Low riskAutomated heuristic from public metadata — not a security guarantee.