[DOC] List the community SDKs in the reference

[Laurianti]

Description of changes

• Improvements & Bug fixes
  • The reference overview says that the Chroma community maintains open source clients for other languages, but no page lists them since [DOC] IA improvements and getting-started update #6182 removed the introduction page. This adds a Community SDKs section with the community clients that support the v2 API of Chroma 1.x and have been updated since December 2025: C#/.NET, Dart, Go, Java (two clients), PHP, PHP (Laravel) and Ruby.
  • Compared with the list on that page: the Elixir and Clojure clients do not support the v2 API, the R client has had no release since March 2025, phpMyChroma is a web interface rather than a client, and the C#/.NET row links ChromaDotNet/ChromaDB.Client, which continues ssone95/ChromaDB.Client, the client listed before. I maintain the .NET one. The .NET client is also the one the Chroma provider of the AI Community Toolkit is built on, for Microsoft.Extensions.VectorData (Chroma: add the MEVD provider CommunityToolkit/AI#58, merged). The Chroma integration of the Aspire Community Toolkit uses it too (Add Chroma hosting and client integrations CommunityToolkit/Aspire#2219, approved, waiting to be merged), and so does the Chroma module proposed to Testcontainers for .NET (feat: Add Chroma module testcontainers/testcontainers-dotnet#1784).

Test plan

• mint dev renders the section, and every link answers 200.
• For each client, the v2 API is in the source of its default branch, and its last release or commit is from December 2025 or later.

Migration plan

None: documentation only.

Observability plan

None.

Documentation Changes

This PR is a documentation change.

[claude]

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[Copilot]

Copilot review overview

🟢 Approval recommended

The documentation-only addition is accurate, well-scoped, and consistent with the reference page.

Review effort: Balanced
Findings: None

What changed in this PR

Adds a Community SDKs section to restore discoverability of actively maintained, Chroma v2-compatible third-party clients.

Changes:

• Lists community SDKs for seven languages.
• Links directly to each client repository.

File	Description
docs/​mintlify/​reference/​overview.mdx	Adds the community SDK directory to the reference overview.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.