Skip to main content

mem0-tcvectordb

mem0-tcvectordb adds Tencent Cloud’s TCVectorDB as a first-class vector store provider for mem0. Install it next to mem0ai to unlock Tencent Cloud hosting without patching the upstream library.

Highlights

  • Registers a tcvectordb provider that works with Memory/AsyncMemory.
  • Re-exports the configuration schema so you get validation and editor hints.
  • Keeps close parity with the implementation that ships in the upstream mem0 repo.

Installation

pip install mem0-tcvectordb

Usage

import mem0_tcvectordb  # noqa: F401 - registers the provider with mem0
from mem0 import Memory

config = {
    "vector_store": {
        "provider": "tcvectordb",
        "config": {
            "collection_name": "memories",
            "database_name": "mem0",
            "embedding_model_dims": 1536,
            "url": "https://<instance-id>.ap-singapore.tcvdb.tencentcs.com",
            "username": "root",
            "api_key": "tcvdb_api_key",
        }
    }
}

memory = Memory.from_config(config)
memory.add("Alice loves sci-fi movies", user_id="alice")

Configuration Reference

Parameter Description Default
collection_name Collection where memories are stored mem0
database_name Database that owns the collection mem0
embedding_model_dims Embedding dimension produced by mem0 1536
url TCVectorDB HTTP endpoint required
username Account username required
api_key API key required
password Optional password; defaults to api_key None
read_consistency EVENTUAL_CONSISTENCY or STRONG_CONSISTENCY EVENTUAL_CONSISTENCY
shards Number of shards 1
replicas Number of replicas 1
metric_type Distance metric (COSINE, IP, L2, HAMMING) COSINE
index_type Index type (e.g., HNSW, FLAT) HNSW
pool_size HTTP connection pool size 10
proxies Optional proxy configuration None
client Pre-built VectorDBClient instance None

mem0 ships embeddings, so TCVectorDB never runs an embedding model. Ensure embedding_model_dims matches the mem0 embedding size configured for your deployment.

Troubleshooting

  • ValueError: TCVectorDB requires url, username, and api_key: supply credentials in the vector_store.config block or pass an authenticated VectorDBClient.
  • VectorStoreError: ... failed: verify the Tencent Cloud endpoint is reachable from your runtime and that read_consistency, metric_type, and filters use values supported by TCVectorDB.

Metadata

Release files for mem0-tcvectordb 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mem0-tcvectordb 0.1.0
File Size Uploaded
mem0_tcvectordb-0.1.0.tar.gz 16.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for mem0-tcvectordb 0.1.0
File Interpreter ABI Platform
mem0_tcvectordb-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 35.1 kB

Release files / mem0_tcvectordb-0.1.0.tar.gz

Download URL mem0_tcvectordb-0.1.0.tar.gz
Size 16.2 kB
Tags Source
SHA-256 checksum
How to use checksums
0db187860d9f490f4a125c493d0d2424fd95fb8ce72279ba78433cb95ed40633
BLAKE2b-256 checksum
How to use checksums
4782baf430ca837d68825dc07e20944c409b9aaa62628a3c9e10e7db893e4162
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2025.

Transparency log

Release files / mem0_tcvectordb-0.1.0-py3-none-any.whl

Download URL mem0_tcvectordb-0.1.0-py3-none-any.whl
Size 18.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9c8205f3731e440ccde20a3aef597ba7f1b81f8c42392acdf396f0b143d36dd6
BLAKE2b-256 checksum
How to use checksums
0d02a644b3a6a86f277d05c005cd173df3190e56780dee150adc77ae078fbdd5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page