Weaviate MCP server

What the model can do

Weaviate vector database (self-hosted or Weaviate Cloud): collections with their properties, objects listed, read by id or searched by keyword, hybrid or meaning (properties only, never vectors), object counts per collection, tenants and aliases; and creating, updating or deleting objects singly or in listed batches, creating or deleting collections, adding properties, cross-references, tenants and aliases.

Reads

• weaviate_list_collectionsThe collections in Weaviate: name, description, vectoriser, whether multi-tenant, and their properties with data types.
• weaviate_list_objectsObjects in one Weaviate collection with their properties (text cut short, no vectors), in UUID order.
• weaviate_get_objectOne Weaviate object by collection and UUID, with its properties (no vector) and when it was created and last updated.
• weaviate_count_objectsHow many objects each Weaviate collection holds, summed over the cluster's nodes and shards, with each node's status and version.
• weaviate_searchSearch one Weaviate collection: "keyword" (BM25), "hybrid" (keyword and vector blended; alpha 1 is pure vector, 0 pure keyword) or "semantic"…
• weaviate_list_tenantsThe tenants of a multi-tenant Weaviate collection, with each one's activity status (ACTIVE, INACTIVE, OFFLOADED).
• weaviate_list_aliasesWeaviate aliases (alternative names that point at a collection), optionally only those of one collection.

Acts, when you ask

These change something in Weaviate. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• weaviate_create_objectCreates one object in a Weaviate collection with the given properties; Weaviate assigns its id.
• weaviate_update_objectUpdates one Weaviate object's properties by collection and id (a merge): each property given OVERWRITES that property's current value…
• weaviate_delete_objectDeletes one object from a Weaviate collection by id: its properties and vector are gone.
• weaviate_batch_create_objectsCreates up to 100 objects in one Weaviate collection in one call; Weaviate assigns each id.
• weaviate_delete_objectsDeletes up to 100 objects from one Weaviate collection, by the ids listed (never by a filter, never "all"): their properties and vectors are gone…
• weaviate_create_collectionCreates a new Weaviate collection (class) with the given properties.
• weaviate_add_propertyAdds a property to an existing Weaviate collection.
• weaviate_delete_collectionDeletes a whole Weaviate collection: its definition and EVERY object in it, across all tenants.
• weaviate_add_referenceLinks one Weaviate object to another through a cross-reference property of the source object's collection…
• weaviate_delete_referenceRemoves one cross-reference from a Weaviate object's reference property; both objects stay.
• weaviate_create_tenantsCreates tenants in a multi-tenant Weaviate collection, ACTIVE unless INACTIVE is given.
• weaviate_update_tenantsChanges the activity status of the listed tenants: ACTIVE (searchable), INACTIVE (kept on disk, not searchable) or OFFLOADED…
• weaviate_delete_tenantsDeletes the listed tenants of a Weaviate collection and ALL their objects.
• weaviate_create_aliasCreates an alias, a second name that queries can use for a collection.
• weaviate_update_aliasRepoints an existing alias to a different collection.

Connect it

First connect Weaviate on Dashboard → Connections, then add Memtro to your client once. The Weaviate tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Weaviate connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › What collections do we have, and which vectoriser does each use?
• › How many objects are in the Article collection?
• › Show me the properties of object 7c1e in Product
• › Which nodes are in the cluster, and what version are they on?
• › Delete that duplicate object from the Article collection

Questions

Is this an official Weaviate MCP server?

No. It is Memtro's MCP server with Memtro's Weaviate connector behind it: the connector reads Weaviate through its API with the credentials you connect on Dashboard → Connections, and Weaviate publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Weaviate?

Only when you ask, and only what it has been granted: create an object in a collection; update properties of an object (overwrites the properties given); delete an object; create up to 100 objects in a collection in one call; delete up to 100 listed objects by id (permanent); create a collection with its properties; add a property to a collection (cannot be removed afterwards); delete a collection and every object in it (permanent); add or remove a cross-reference between two objects; create tenants in a multi-tenant collection; activate, deactivate or offload tenants; delete tenants and all their data (permanent); create an alias for a collection, or repoint an alias to another collection. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Databases and warehouses

• Postgres MCP server
• MySQL and MariaDB MCP server
• SQL Server MCP server
• BigQuery MCP server
• Snowflake MCP server
• AWS Athena MCP server