Skip to directory

About Weaviate MCP

A built-in Weaviate MCP server that exposes collection configuration, tenant listing, hybrid vector/keyword search, and optionally object upserts through the database's REST API host.

What you can use it for

  • Inspect collection schemas
  • List tenants for multi-tenant collections
  • Search data with hybrid vector and BM25 ranking
  • Upsert objects when write access and permissions are enabled
Connection and setup
Hosting
Remote hosted (Weaviate Cloud) or self-hosted database
Transport
Streamable HTTP
Endpoint
https://<your-cluster-host>/v1/mcp (Cloud); http://localhost:8080/v1/mcp (default self-hosted)
Authentication
Bearer API key when anonymous access is disabled. RBAC roles must include read_mcp and relevant collection/data/tenant permissions; upsert additionally needs create_mcp/update_mcp and data permissions. Weaviate Cloud can require X-Weaviate-Cluster-Url for Weaviate Embeddings.

Requirements

  • Weaviate Cloud cluster or self-hosted Weaviate v1.38+
  • Self-hosted: enable MCP_SERVER_ENABLED=true; disabled by default
  • API key and relevant RBAC permissions unless anonymous access is configured

Setup steps

  1. Cloud: in the Weaviate Cloud console, open the cluster's How to connect > MCP tab and use the generated Streamable HTTP endpoint/config. Append /v1/mcp to the cluster REST endpoint and configure Authorization: Bearer <API_KEY>.
  2. Self-hosted: configure MCP_SERVER_ENABLED=true and connect to the Weaviate REST host at /v1/mcp. Write access is disabled by default; set MCP_SERVER_WRITE_ACCESS_ENABLED=true only if upserts are intended.
  3. For least privilege, use a viewer API key for read-only access. For Weaviate Embeddings, include X-Weaviate-Cluster-Url as documented.
  4. Verify using weaviate-collections-get-config or another read-only query. Do not use upsert for a connection test.
Tools 4

The built-in instance server documents four tools. weaviate-objects-upsert is omitted from tools/list when write access is disabled. The hosted Query Agent MCP is a separate service and is not included.

  • weaviate-collections-get-config

    Retrieve collection schema configuration.

    01
  • weaviate-tenants-list

    List tenants in a multi-tenant collection.

    02
  • weaviate-query-hybrid

    Search a collection with vector similarity and BM25 keyword matching.

    03
  • weaviate-objects-upsert

    Batch insert or update objects; conditional on write access.

    04
Limitations and notes
  • Self-hosted MCP is disabled by default and requires Weaviate v1.38 or newer.
  • Cloud exposes write access by default unless the Enable MCP Read-Only option is on; use a viewer key to constrain a specific client.
  • Upsert may alter schema when auto-schema is enabled; mistyped collection names can create collections.
  • Cloud requests lasting about 60 seconds may be cut off; large upserts should be batched.
  • Weaviate's separate Docs MCP server is a different implementation and is not merged here.
Original sources
  • official tool reference

    Weaviate documents four instance-server tools; write-upsert visibility depends on write-access configuration. The hosted Query Agent is a separate MCP server and is not merged into this record.

  • official documentation

    Weaviate documents four instance-server tools; write-upsert visibility depends on write-access configuration. The hosted Query Agent is a separate MCP server and is not merged into this record.

Documentation checked 2026-10-28T12:35:00.000Z. Connection has not been runtime tested.

Similar tools