MCP servers and agent tools for Weaviate
AgentSidekick indexes 3 DER agent products that mention Weaviate; 3 of them have a full profile and are listed below. The most-starred tools that are their own repository are recipes (952 stars) and weaviate-mcp (0 stars) SRC. Figures as of 2026-11-21.
Weaviate tools with a full profile
Search the directoryRanked by GitHub stars of the product's own repository. Products that live in a subfolder of a larger repository (marked “repo”) show that whole repository's stars and are ranked after them; products without a public repository come last.
| # | Product | Type | Hosting | Licence | Stars | Last push | Publisher | Save and compare |
|---|---|---|---|---|---|---|---|---|
| 1 | recipesThis repository shares end-to-end notebooks on how to use various Weaviate features and integrations! | Infrastructure | — | — | 952 | 1mo ago | weaviate | |
| 2 | weaviate-mcpMCP server for Weaviate: collections, objects, GraphQL search. Works with any instance. | MCP server | Local | — | 0 | 1d ago | mrfentmen | |
| 3 | hunt-rag-vectorHunt vector-store / embedding-layer weaknesses in RAG pipelines (OWASP LLM08 Vector and Embedding Weaknesses) — persistent corpus poisoning that survives across sessions and users (distinct from one-shot indirect prompt injection, which is owned by hunt-llm-ai), cross-tenant vector-database IDOR (unauthenticated or unscoped queries against Pinecone/Weaviate/Chroma/Milvus/Qdrant/pgvector), source-text/metadata leakage in similarity-search results, and retrieval-hijack via adversarial embedding proximity ('SEO poisoning' for RAG). Targets: any app with a shared knowledge base, document upload feeding a chatbot, or a directly reachable vector-DB port. Validate: a second, clean session/account must inherit a poisoned result, or a cross-tenant artifact must be independently verifiable — confabulation is not a finding, same bar as hunt-llm-ai. Use when target is RAG-backed, exposes a vector-DB port, or lets users upload documents that other users' queries later retrieve. | Agent skill | Local | MIT | — | today | elementalsouls |
Hosting across all 3 profiled: 0 remote, 2 local, 0 both, 1 not declared. DER
From the vendor's own organisation vs the communityDER
1 of 3 profiled products are published by an account matching Weaviate's own name; the other 2 are from other publishers.
| Product | Publisher | Why it counts as the vendor's | Stars |
|---|---|---|---|
| recipes | weaviate | Matched on publisher name “weaviate” | 952 |
How this was determined: the publisher name, its GitHub owner, the repository owner and (for MCP Registry DNS namespaces) the domain's main label were compared with weaviate
. A vendor publishing under a differently named account (for example a parent company) is counted as community; a same-named account is not proof of official status.
Product-type mix
Which forms the tools take. Indexed covers every matching record; profiled only those with a page.
| Type | Indexed | Share | Profiled |
|---|---|---|---|
| MCP servers | 1 | 33.3% | 1 |
| Infrastructure | 1 | 33.3% | 1 |
| Agent skills | 1 | 33.3% | 1 |
What these tools do
Most common capabilities among the profiled tools, matched from their descriptions by keyword rules.
Capabilities of Weaviate toolsDER
Profiled products mentioning Weaviate, by capability, top 10. A product can have several. As of 2026-11-21.
Show the data as a table
| profiled products | |
|---|---|
| Vector Databases | 3 |
| Vector Storage | 2 |
| Retrieval-Augmented Generation | 2 |
| Tool Use & Function Calling | 1 |
| Security Review | 1 |
| Agent Threat Protection | 1 |
| Prompt Injection Defense | 1 |
| Knowledge Bases & Wikis | 1 |
| SEO Research | 1 |
| API Tooling | 1 |
Demand signal
How often developers discuss this integration alongside MCP in public GitHub issues.
73 SRC public GitHub issues contain the phrase Weaviate mcp
(search run 2026-11-21). Run the same search on GitHub.
This measures developer discussion, not buyers or revenue: an issue may be a bug report, a feature request or a passing mention. The count is GitHub's own estimate for the query "Weaviate mcp" in:title,body is:issue.
Segment statisticsDER
All 3 indexed products, not only profiled ones. Calculated 2026-11-21.
- Launches
- 1 in the last 90 days, 0 in the 90 days before (+100%)DER
- Products with a repository
- 2 of 3 have whole-repository star countsDER
- Combined stars
- 952DER
- Median stars
- 476DER
- Largest project's share
- 100% of all stars in the segmentDER
- Concentration (HHI)
- 1.000, as concentrated as about 1 equally starred projectDER
- Open-source share
- 33%DER
- Label
- ThinDER
How the label is set: size is this integration's percentile among all 111 integrations by indexed products (80th or above is crowded, 30th or below is thin). Momentum compares the ratio of launches in the last 90 days to the 90 before with the same ratio for the whole catalogue, so a booming ecosystem does not make every segment look like it is accelerating; it needs at least 5 launches across both windows. A segment can launch more products than last quarter and still be labelled slowing if the catalogue grew faster.
Vendor API
Weaviate has a public API CUR. API docs (as recorded) The link has not been checked since it was recorded.
Weaviate is not recorded as primarily a paid business product.
Opportunity score
Better agent tooling for Weaviate scores 45.7 HEU of 100 (demand component 6, gap 69; competition low, confidence low; calculated 2026-11-21). Scores rank integrations against each other; they do not predict revenue.
How products are matched, and the limits
A product is counted when its name, description or repository topics contain one of these aliases (case-insensitive, whole words): weaviate
. A product named exactly “Weaviate” is skipped, since it is the service itself.
Which alias matched, across the 3 indexed records: weaviate
3.
Keyword matching over-counts tools that only mention Weaviate in passing (for example as where their code is hosted) and misses tools that integrate with it without naming it. Treat the counts as an upper bound on dedicated tools and a lower bound on everything that touches Weaviate.
Sources
- GitHub issue search: github.com (external)checked
- API documentation (as recorded, unverified): weaviate.io (external)check date not recorded
Product records come from the official MCP Registry, GitHub, Open VSX and plugin marketplaces; each profile lists its own sources. Methodology
Page data last updated .