RRepoGEO

REPOGEO REPORT · LITE

chroma-core/chroma-mcp

Default branch main · commit 98ff6758 · scanned 6/14/2026, 4:01:19 PM

GitHub: 563 stars · 112 forks

AI VISIBILITY SCORE
28 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 warn · 0 fail
Objective metadata checks
AI knows your name
2 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface chroma-core/chroma-mcp, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Reposition README opening to clarify role as Chroma's server

    Why:

    COPY-PASTE FIX
    Add a sentence immediately after the `# Chroma MCP Server` heading: "This repository provides the self-hosted server implementation for Chroma, the open-source embedding database, enabling robust data retrieval capabilities for LLM applications via the Model Context Protocol (MCP)."
  • hightopics#2
    Add specific topics to improve categorization

    Why:

    COPY-PASTE FIX
    vector-database, embedding-database, llm, ai, machine-learning, server, model-context-protocol, chroma, self-hosted
  • mediumhomepage#3
    Add main Chroma homepage to repo metadata

    Why:

    COPY-PASTE FIX
    https://www.trychroma.com/

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface chroma-core/chroma-mcp
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Weaviate
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Weaviate · recommended 2×
  2. Qdrant · recommended 2×
  3. Chroma · recommended 2×
  4. Pinecone · recommended 1×
  5. Faiss · recommended 1×
  • CATEGORY QUERY
    How can I efficiently store and retrieve context for large language models?
    you: not recommended
    AI recommended (in order):
    1. Pinecone
    2. Weaviate
    3. Qdrant
    4. Chroma
    5. Faiss
    6. Redis with Redis Stack
    7. Elasticsearch

    AI recommended 7 alternatives but never named chroma-core/chroma-mcp. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for a self-hosted open-source vector database for AI application memory.
    you: not recommended
    AI recommended (in order):
    1. Qdrant
    2. Weaviate
    3. Milvus
    4. Chroma
    5. PGVector

    AI recommended 5 alternatives but never named chroma-core/chroma-mcp. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    warn

    Suggestion:

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of chroma-core/chroma-mcp?
    pass
    AI did not name chroma-core/chroma-mcp — likely talking about a different project

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts chroma-core/chroma-mcp in production, what risks or prerequisites should they evaluate first?
    pass
    AI named chroma-core/chroma-mcp explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo chroma-core/chroma-mcp solve, and who is the primary audience?
    pass
    AI named chroma-core/chroma-mcp explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of chroma-core/chroma-mcp. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/chroma-core/chroma-mcp.svg)](https://repogeo.com/en/r/chroma-core/chroma-mcp)
HTML
<a href="https://repogeo.com/en/r/chroma-core/chroma-mcp"><img src="https://repogeo.com/badge/chroma-core/chroma-mcp.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

chroma-core/chroma-mcp — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite