Niches · Retrieval & vector search

Let an agent query an index through MCP without writing code

One company's docs show a full fit.

1companies, full fit
10companies, fit with a limit
18companies carry the tag
6share of the category's work
5first-hand accounts

What counts as done

The agent lists collections and their fields, sends a text query with a filter on a real field, and gets results, without building a vector or guessing a field name, using read-only credentials.

Measured, for our own tests: the first useful result arrives within three tool calls. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: search the vector store for X, what collections are there, find records where status is open about Y

Does the job 1

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Weaviate API + MCP C
Weaviate B.V.
weaviate-collections-get-config shows property names, weaviate-tenants-list lists tenants, and weaviate-query-hybrid takes text and filters; a viewer-role key or the read-only switch keeps it read-only. source

Does the job, with a limit 10

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Chroma API + MCP D
Chroma Inc.
chroma-mcp lists collections with paging, returns collection info and runs text queries with filters, but it has no read-only mode, so read-only credentials depend on the client used. source
Cloudflare AI Search BB
Cloudflare, Inc.
The per-instance MCP endpoint exposes one search tool, so the agent cannot list instances or fields, and the endpoint is public once enabled unless something like Cloudflare Access sits in front. source
Elasticsearch C
Elasticsearch B.V.
The Agent Builder MCP server exposes built-in and custom tools, limited by the authorising user's permissions, but it needs Kibana Agent Builder (Elastic Cloud or 9.2 and later) and some built-in tools are unavailable over MCP. source
Meilisearch A
Meili SAS
The built-in MCP route has four read-only tools, including searchInIndexes with filters and hybrid, but it is experimental and off by default, and describeIndex returns five sample documents rather than a field list. source
Milvus and Zilliz Cloud API + MCP B
Zilliz Inc.
The MCP server lists collections, returns schema with milvus_get_collection_info and runs text search with filter_expr, but it has no read-only mode and also has create, load, release and delete tools. source
OpenSearch BB
OpenSearch Software Foundation, a project of The Linux Foundation
Core MCP tools list indices, return mappings and run DSL searches, but the GenericOpenSearchApiTool can call any endpoint, #43 shows a wrong field returning an empty result the model trusted, and #203 filters ignored in multi mode. source
Pinecone API + MCP A
Pinecone Systems Inc.
MCP tools list and describe indexes and search with text and metadata filters, but only on legacy integrated-embedding indexes, and no read-only mode was found. source
Qdrant API + MCP BB
Qdrant Solutions GmbH
The MCP server takes text queries and has QDRANT_READ_ONLY, but its two tools cannot list collections or fields, and filters need extra configuration. source
Typesense API + MCP BB
Typesense, Inc.
The Typesense Cloud MCP server runs keyword and hybrid searches with permissions chosen at connect, but first connect is a browser consent page, so a headless agent cannot start alone. source
Upstash Vector API + MCP B
Upstash, Inc.
The hosted MCP server lists indexes and namespaces, runs vector_query with server-side embedding, and a read-only OAuth grant or key removes write tools, but no tool lists metadata field names. source

Doesn't do this job 3

Listings in the category that do something else, with the reason.

ListingWhy
Epsilla Vector Database E
Epsilla, Inc.
No MCP server found in the docs index. source
LanceDB B
LanceDB Systems, Inc.
No official MCP server or hosted endpoint for an agent to call without an Enterprise deployment. source
Vespa BB
Vespa.ai AS
No official public MCP server; an MCP endpoint must be built into the user's own application. source

What stops agents finishing

  • data tools need a browser sign-in so a headless agent gets cluster tools only
  • MCP server lags the engine (no hybrid, no filters without extra flags)

Around it

After: vector-search.rag-over-docs.

Where this comes from

Weight 6 of 100 in Retrieval & vector search: 5 of 37 accounts on MCP servers (Milvus, OpenSearch, Meilisearch, Chroma, Pinecone)

The same as data: /api/v1/use-cases/vector-search.agent-query-tool.json, or the MCP tool get_use_case with id vector-search.agent-query-tool. Other jobs in this category: /api/v1/niches?category=vector-search.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.