MCP Server Weaviate logo

MCP Server Weaviate

by weaviate

Connects MCP clients to Weaviate for schema inspection, tenant listing, hybrid search, and object upserts.

Install MCP Server Weaviate

Pick your client, then add it in one click or paste the config.

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for weaviate/mcp-server-weaviate, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Overview

The weaviate/mcp-server-weaviate MCP server exposes Weaviate collection and data operations through MCP tools. The standalone repository is deprecated; equivalent functionality is now built into the Weaviate binary from v1.37.1 as a preview. Enable the built-in endpoint with MCP_SERVER_ENABLED=true, then access it at /v1/mcp on the same port as the REST API. Use it when an agent needs to inspect schemas, list tenants, search with hybrid retrieval, or create and update Weaviate objects.

Use cases

  • Inspect Weaviate collection schemas
  • List tenants in multi-tenant collections
  • Search knowledge bases with hybrid retrieval
  • Create or update Weaviate objects

Key features

  • Collection schema inspection
  • Multi-tenant collection listing
  • Hybrid vector and keyword search
  • Object creation and updates
  • API-key authentication
  • RBAC-aware access

Tools4

What MCP Server Weaviate lets your agent do. Expand a tool for its parameters.

Self-reported~55 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

13/14 checks healthy over the last 78d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars161Stargazers on the source repository.
Last commit5mo agoMost recent push to the default branch.
Tools exposed4Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Server Weaviate works

What weaviate/mcp-server-weaviate does

The weaviate/mcp-server-weaviate MCP server connects MCP clients to Weaviate collections and exposes a focused set of collection, tenant, search, and object-management operations. Agents can inspect collection schemas, retrieve tenants for multi-tenant collections, run hybrid searches that combine vector and keyword retrieval, and create or update objects.

The repository is no longer the recommended deployment path. Its earlier standalone Go implementation wrapped the Weaviate REST API, but that implementation has been superseded by an MCP server included in the main Weaviate distribution.

How it works

The current implementation runs inside the Weaviate weaviate/weaviate binary rather than as a separate process from this repository. Weaviate exposes the MCP endpoint at /v1/mcp, using the same port as its REST API. Authentication uses Weaviate's existing API-key flow, and the endpoint observes Weaviate RBAC controls.

The built-in server is available as a preview beginning with Weaviate v1.37.1. MCP clients connect to the endpoint, and the server performs the corresponding operations against the configured Weaviate instance and collections.

Setup and configuration

Use the built-in Weaviate MCP server instead of installing or running this standalone repository. Enable it by setting the following environment variable for the Weaviate process:

sh
MCP_SERVER_ENABLED=true

After enabling the feature, connect to the /v1/mcp endpoint on the Weaviate REST API port. API-key authentication and RBAC are inherited from Weaviate, so access depends on the credentials and permissions configured for that instance. The repository excerpt points to Weaviate's MCP documentation for detailed setup, environment-variable, RBAC, and per-tool reference information.

Tools and capabilities

The weaviate/mcp-server-weaviate MCP server provides four documented tools:

  • weaviate-collections-get-config inspects collection schemas and configuration.
  • weaviate-tenants-list lists tenants belonging to a multi-tenant collection.
  • weaviate-query-hybrid performs hybrid retrieval using vector and keyword search.
  • weaviate-objects-upsert creates new objects or updates existing objects.

Together, these tools support basic agent access to a Weaviate-backed knowledge base and object writes. The documented tool list does not describe broader administration, deletion, or collection-creation operations.

Limitations and notes

The standalone repository is deprecated and is no longer maintained. There is nothing to install or run separately from this repository for the current implementation. Use a Weaviate release that includes the preview MCP server and enable it in the main binary instead.

The endpoint also depends on Weaviate's existing authentication and RBAC behavior, so an MCP connection does not bypass those controls. The repository history remains available for reference, but earlier standalone source should not be treated as the current implementation.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Server Weaviate

weaviate/mcp-server-weaviate is an MCP server that connects MCP clients to Weaviate collections. Its main tools inspect collection schemas, list tenants, run hybrid vector-and-keyword searches, and create or update objects. The standalone repository is deprecated; these capabilities now run inside the Weaviate binary.

Do not install the standalone repository; enable the built-in server in Weaviate instead. Use a Weaviate version with the preview MCP server, beginning with v1.37.1, and set MCP_SERVER_ENABLED=true for the Weaviate process.

It provides four documented tools: collection configuration inspection, tenant listing, hybrid vector-and-keyword search, and object upsert. Their names are weaviate-collections-get-config, weaviate-tenants-list, weaviate-query-hybrid, and weaviate-objects-upsert.

It uses Weaviate's existing API-key authentication and respects RBAC. Connect through the /v1/mcp endpoint on the same port as the Weaviate REST API, using credentials and permissions configured for that Weaviate instance.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Server Weaviate AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/weaviate-mcp-server-weaviate?style=directory)](https://allmcps.com/mcp/weaviate-mcp-server-weaviate)
HTML Embed
<a href="https://allmcps.com/mcp/weaviate-mcp-server-weaviate"><img src="https://allmcps.com/api/badge/weaviate-mcp-server-weaviate?style=directory" alt="MCP Server Weaviate on AllMCPs" /></a>