← Explore all mcp servers

VECTOR DATA MANAGEMENT / Weaviate

Weaviate built-in MCP

Inspect collections, search vector and keyword data, and optionally upsert objects through Weaviate’s built-in MCP endpoint.

“Weaviate implements this as a Streamable HTTP server that runs on the same port as the main Weaviate REST API.”

01 / THE REASONING

Why this made the selection.

  • Lives in the database server and reuses its authentication and role permissions.
  • Collection and tenant inspection support retrieval against existing Weaviate data.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • Current Weaviate configuration/tool reference and standalone repository migration notice.
  • Pinned Go MCP server, authorization wrapper, config and object-upsert handler.
  • Repository licence location rules and BSD licence.

Our findings

  • The endpoint is /v1/mcp on the REST API host. RBAC is enforced when tools are called, not by hiding every unauthorized tool in tools/list.
  • The inspected MCP source is outside wl and covered by BSD-3-Clause; that does not extend to separately licensed Weaviate features.

Not established by this review

  • Server launch, authenticated tool calls, and release-to-source parity were not tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. Use a Weaviate deployment that includes the built-in server; do not install the deprecated standalone package.
  2. For self-hosting, enable MCP_SERVER_ENABLED and leave write access disabled unless needed. In Cloud, configure Enable MCP Read-Only if the agent should only read.
  3. Connect to the REST host with /v1/mcp and a suitable API key using the official client-specific instructions.

Before you start

  • A supported Weaviate deployment.
  • An API key with appropriate MCP and data permissions; transport-capable client.

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://docs.weaviate.io/weaviate/configuration/mcp-server

    Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review

  2. https://raw.githubusercontent.com/weaviate/mcp-server-weaviate/main/README.md

    Supports: limitations, review

  3. https://raw.githubusercontent.com/weaviate/weaviate/2eda1edd2b5097e151c1f5a60b3c9a22e8d58fe1/adapters/handlers/mcp/server.go

    Supports: language, transports, review

  4. https://raw.githubusercontent.com/weaviate/weaviate/2eda1edd2b5097e151c1f5a60b3c9a22e8d58fe1/adapters/handlers/mcp/auth/auth.go

    Supports: access, review

  5. https://raw.githubusercontent.com/weaviate/weaviate/2eda1edd2b5097e151c1f5a60b3c9a22e8d58fe1/adapters/handlers/mcp/create/objects_upsert.go

    Supports: access, review

  6. https://raw.githubusercontent.com/weaviate/weaviate/2eda1edd2b5097e151c1f5a60b3c9a22e8d58fe1/LICENSE

    Supports: license

  7. https://raw.githubusercontent.com/weaviate/weaviate/2eda1edd2b5097e151c1f5a60b3c9a22e8d58fe1/LICENSE-BSD

    Supports: license