← 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 MCP configuration and tool reference (docs.weaviate.io, read 2026-10-13).
  • Standalone mcp-server-weaviate README at 2122c8fc0f4ffdef19b1b24dc71fde69255adca8 (deprecation notice).
  • adapters/handlers/mcp/server.go, auth/auth.go and create/objects_upsert.go in weaviate/weaviate at 69fd5307a49b1e3119915bc4621f17654773b429.
  • LICENSE and LICENSE-BSD at 69fd5307a49b1e3119915bc4621f17654773b429.

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.
  • At this commit LICENSE says code under wl/ is all rights reserved and available only under a separate enterprise licence (it said "Weaviate License" at the previous pin). adapters/handlers/mcp is outside wl, so the MCP handler stays BSD-3-Clause.
  • Four tools: weaviate-collections-get-config, weaviate-tenants-list, weaviate-query-hybrid and weaviate-objects-upsert. Only the write-access flag hides the upsert tool; a call the key may not make returns a tool result with isError true, not HTTP 403.
  • auth.go now also requires the collection’s namespace to be active before authorizing a call (AuthorizeAndRequireActiveNamespace). The docs page says the server was added in v1.38; the standalone README says preview from v1.37.1.
  • configExample is the docs page’s "Standard JSON configuration format" block, read 2026-10-13. It carries no Authorization header; the docs say to send Authorization: Bearer with an API key unless anonymous access is enabled.

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.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "weaviate-local": {
      "url": "http://localhost:8080/v1/mcp",
      "type": "streamable-http"
    }
  }
}

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, configExample

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

    Supports: limitations, review

  3. https://raw.githubusercontent.com/weaviate/weaviate/69fd5307a49b1e3119915bc4621f17654773b429/adapters/handlers/mcp/server.go

    Supports: language, transports, review

  4. https://raw.githubusercontent.com/weaviate/weaviate/69fd5307a49b1e3119915bc4621f17654773b429/adapters/handlers/mcp/auth/auth.go

    Supports: access, review

  5. https://raw.githubusercontent.com/weaviate/weaviate/69fd5307a49b1e3119915bc4621f17654773b429/adapters/handlers/mcp/create/objects_upsert.go

    Supports: access, review

  6. https://raw.githubusercontent.com/weaviate/weaviate/69fd5307a49b1e3119915bc4621f17654773b429/LICENSE

    Supports: license

  7. https://raw.githubusercontent.com/weaviate/weaviate/69fd5307a49b1e3119915bc4621f17654773b429/LICENSE-BSD

    Supports: license

Evidence & Ask