better-mem0-mcp 1.1.0b20__tar.gz → 1.1.0b21__tar.gz

{better_mem0_mcp-1.1.0b20 → better_mem0_mcp-1.1.0b21}/.github/workflows/cd.yml

@@ -71,7 +71,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v6
         with:
-          node-version: "22"
+          node-version: "24"
 
       - name: Install uv (for toml-cli)
         uses: astral-sh/setup-uv@v5

{better_mem0_mcp-1.1.0b20 → better_mem0_mcp-1.1.0b21}/.mise.toml

@@ -5,7 +5,7 @@
 
 [tools]
 python = "3.13"
-node = "22"
+node = "24"
 uv = "latest"
 
 [settings]

{better_mem0_mcp-1.1.0b20 → better_mem0_mcp-1.1.0b21}/CHANGELOG.md

@@ -1,3 +1,10 @@
+# [1.1.0-beta.21](https://github.com/n24q02m/better-mem0-mcp/compare/v1.1.0-beta.20...v1.1.0-beta.21) (2026-01-12)
+
+
+### Bug Fixes
+
+* update Node.js version to 24 in CI/CD configuration and Mise setup ([92ab0a9](https://github.com/n24q02m/better-mem0-mcp/commit/92ab0a96cd30643b9ecf927c68b46cde6472d732))
+
 # [1.1.0-beta.20](https://github.com/n24q02m/better-mem0-mcp/compare/v1.1.0-beta.19...v1.1.0-beta.20) (2026-01-05)
 
 

better_mem0_mcp-1.1.0b21/CODE_OF_CONDUCT.md

@@ -0,0 +1,82 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at quangminh2402.dev@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

{better_mem0_mcp-1.1.0b20 → better_mem0_mcp-1.1.0b21}/CONTRIBUTING.md

@@ -84,6 +84,8 @@ We use [Conventional Commits](https://www.conventionalcommits.org/):
 - `perf`: Performance improvements
 - `test`: Adding or updating tests
 - `chore`: Maintenance tasks
+- `ci`: CI/CD changes
+- `build`: Build system changes
 
 ### Examples
 
@@ -93,6 +95,44 @@ fix: handle database connection timeout
 docs: update configuration examples
 ```
 
+## Release Process
+
+Releases are automated using **Semantic Release**. We strictly follow the **Conventional Commits** specification to determine version bumps and generate changelogs automatically.
+
+### How to Release
+
+1. Create a Pull Request with your changes.
+2. Ensure your commit messages follow the convention above.
+3. Merge the PR to `main`.
+4. The CI pipeline will automatically:
+   - Analyze the new commits
+   - Determine the next version number
+   - Generate release notes
+   - Update `CHANGELOG.md`
+   - Publish to PyPI
+   - Create a GitHub Release
+   - Build and push Docker images
+
+You do **not** need to create manual tags or changelog entries.
+
+## Pull Request Guidelines
+
+- Keep PRs focused on a single feature or fix
+- Update documentation if needed
+- Add tests for new functionality
+- Ensure all checks pass
+
+### PR Checklist
+
+Before submitting your PR, ensure:
+
+- [ ] Code follows Python best practices
+- [ ] All tests pass (`uv run pytest`)
+- [ ] Linting passes (`uv run ruff check .`)
+- [ ] Formatting is correct (`uv run ruff format --check .`)
+- [ ] Commit messages follow **Conventional Commits**
+- [ ] Documentation updated (if needed)
+
 ## Code Style
 
 This project uses **Ruff** for formatting and linting.
@@ -126,6 +166,15 @@ better-mem0-mcp/
 └── README.md
 ```
 
+## Questions?
+
+Feel free to open an issue for:
+
+- Bug reports
+- Feature requests
+- Questions about the codebase
+- Discussion about architecture
+
 ## License
 
 By contributing, you agree that your contributions will be licensed under the MIT License.

{better_mem0_mcp-1.1.0b20 → better_mem0_mcp-1.1.0b21}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: better-mem0-mcp
-Version: 1.1.0b20
+Version: 1.1.0b21
 Summary: Zero-setup MCP Server for AI memory - works with Neon/Supabase
 Project-URL: Homepage, https://github.com/n24q02m/better-mem0-mcp
 Project-URL: Repository, https://github.com/n24q02m/better-mem0-mcp.git
@@ -29,16 +29,28 @@ Description-Content-Type: text/markdown
 
 # better-mem0-mcp
 
-**Zero-setup** MCP Server for AI memory. Works with Neon/Supabase free tier.
+**Self-hosted MCP Server for AI memory with PostgreSQL (pgvector).**
 
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![PyPI](https://img.shields.io/pypi/v/better-mem0-mcp)](https://pypi.org/project/better-mem0-mcp/)
+[![Docker](https://img.shields.io/docker/v/n24q02m/better-mem0-mcp?label=docker)](https://hub.docker.com/r/n24q02m/better-mem0-mcp)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
+
+## Features
+
+- **Self-hosted PostgreSQL** - Your data stays with you (Neon/Supabase free tier supported)
+- **Graph Memory** - SQL-based relationship tracking alongside vector memory
+- **Multi-provider LLM** - Gemini, OpenAI, Anthropic, Groq, DeepSeek, Mistral
+- **Fallback chains** - Multi-key per provider + multi-model fallback
+- **Zero manual setup** - Just `DATABASE_URL` + `API_KEYS`
+
+---
 
 ## Quick Start
 
 ### 1. Get Prerequisites
 
-- **Database**: [Neon](https://neon.tech) or [Supabase](https://supabase.com) (free tier)
-- **API Key**: [Google AI Studio](https://aistudio.google.com/apikey) (free tier)
+- **Database**: [Neon](https://neon.tech) or [Supabase](https://supabase.com) (free tier works)
+- **API Key**: Any supported provider ([Google AI Studio](https://aistudio.google.com/apikey) is free)
 
 ### 2. Add to mcp.json
 
@@ -78,7 +90,7 @@ Description-Content-Type: text/markdown
 
 ### 3. Done!
 
-Ask Claude: "Remember that I prefer dark mode and use FastAPI"
+Ask your AI: "Remember that I prefer dark mode and use FastAPI"
 
 ---
 
@@ -86,22 +98,26 @@ Ask Claude: "Remember that I prefer dark mode and use FastAPI"
 
 | Variable | Required | Description |
 |----------|----------|-------------|
-| `DATABASE_URL` | Yes | PostgreSQL connection string |
-| `API_KEYS` | Yes | `provider:key,...` (multi-key per provider OK) |
-| `LLM_MODELS` | No | `provider/model,...` (fallback chain) |
-| `EMBEDDER_MODELS` | No | `provider/model,...` (fallback chain) |
+| `DATABASE_URL` | Yes | PostgreSQL with pgvector extension |
+| `API_KEYS` | Yes | `provider:key` pairs, comma-separated |
+| `LLM_MODELS` | No | Model fallback chain |
+| `EMBEDDER_MODELS` | No | Embedding model chain |
+
+### Supported Providers
+
+`gemini`, `openai`, `anthropic`, `groq`, `deepseek`, `mistral`
 
 ### Examples
 
-**Minimal (Gemini only):**
-```
+**Single provider:**
+```bash
 API_KEYS=gemini:AIza...
 ```
 
 **Multi-key with fallback:**
-```
+```bash
 API_KEYS=gemini:AIza-1,gemini:AIza-2,openai:sk-xxx
-LLM_MODELS=gemini/gemini-2.5-flash,openai/gpt-4o-mini
+LLM_MODELS=gemini/gemini-3-flash-preview,openai/gpt-4o-mini
 EMBEDDER_MODELS=gemini/gemini-embedding-001,openai/text-embedding-3-small
 ```
 
@@ -109,7 +125,7 @@ EMBEDDER_MODELS=gemini/gemini-embedding-001,openai/text-embedding-3-small
 
 | Setting | Default |
 |---------|---------|
-| `LLM_MODELS` | `gemini/gemini-2.5-flash` |
+| `LLM_MODELS` | `gemini/gemini-3-flash-preview` |
 | `EMBEDDER_MODELS` | `gemini/gemini-embedding-001` |
 
 ---
@@ -118,32 +134,41 @@ EMBEDDER_MODELS=gemini/gemini-embedding-001,openai/text-embedding-3-small
 
 | Tool | Description |
 |------|-------------|
-| `memory` | `action`: add, search, list, delete |
-| `help` | Detailed documentation |
+| `memory` | Memory operations: `add`, `search`, `list`, `delete` |
+| `help` | Get full documentation for tools |
 
-### Usage
+### Usage Examples
 
 ```json
 {"action": "add", "content": "I prefer TypeScript over JavaScript"}
-{"action": "search", "query": "preferences"}
+{"action": "search", "query": "programming preferences"}
 {"action": "list"}
 {"action": "delete", "memory_id": "abc123"}
 ```
 
 ---
 
-## Why better-mem0-mcp?
+## Build from Source
+
+```bash
+git clone https://github.com/n24q02m/better-mem0-mcp
+cd better-mem0-mcp
 
-| Feature | Official mem0-mcp | better-mem0-mcp |
-|---------|-------------------|-----------------|
-| Storage | Mem0 Cloud | **Self-hosted PostgreSQL** |
-| Graph Memory | No | **Yes (SQL-based)** |
-| LLM Provider | OpenAI only | **Any (Gemini/OpenAI/Ollama/...)** |
-| Fallback | No | **Yes (multi-key + multi-model)** |
-| Setup | API Key | **DATABASE_URL + API_KEYS** |
+# Setup (requires mise: https://mise.jdx.dev/)
+mise run setup
+
+# Run
+uv run better-mem0-mcp
+```
+
+**Requirements:** Python 3.13+
 
 ---
 
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md)
+
 ## License
 
-MIT
+MIT - See [LICENSE](LICENSE)

better_mem0_mcp-1.1.0b21/README.md

@@ -0,0 +1,145 @@
+# better-mem0-mcp
+
+**Self-hosted MCP Server for AI memory with PostgreSQL (pgvector).**
+
+[![PyPI](https://img.shields.io/pypi/v/better-mem0-mcp)](https://pypi.org/project/better-mem0-mcp/)
+[![Docker](https://img.shields.io/docker/v/n24q02m/better-mem0-mcp?label=docker)](https://hub.docker.com/r/n24q02m/better-mem0-mcp)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
+
+## Features
+
+- **Self-hosted PostgreSQL** - Your data stays with you (Neon/Supabase free tier supported)
+- **Graph Memory** - SQL-based relationship tracking alongside vector memory
+- **Multi-provider LLM** - Gemini, OpenAI, Anthropic, Groq, DeepSeek, Mistral
+- **Fallback chains** - Multi-key per provider + multi-model fallback
+- **Zero manual setup** - Just `DATABASE_URL` + `API_KEYS`
+
+---
+
+## Quick Start
+
+### 1. Get Prerequisites
+
+- **Database**: [Neon](https://neon.tech) or [Supabase](https://supabase.com) (free tier works)
+- **API Key**: Any supported provider ([Google AI Studio](https://aistudio.google.com/apikey) is free)
+
+### 2. Add to mcp.json
+
+#### uvx (Recommended)
+
+```json
+{
+  "mcpServers": {
+    "better-mem0": {
+      "command": "uvx",
+      "args": ["better-mem0-mcp@latest"],
+      "env": {
+        "DATABASE_URL": "postgresql://user:pass@xxx.neon.tech/neondb?sslmode=require",
+        "API_KEYS": "gemini:AIza..."
+      }
+    }
+  }
+}
+```
+
+#### Docker
+
+```json
+{
+  "mcpServers": {
+    "better-mem0": {
+      "command": "docker",
+      "args": ["run", "-i", "--rm", "-e", "DATABASE_URL", "-e", "API_KEYS", "n24q02m/better-mem0-mcp:latest"],
+      "env": {
+        "DATABASE_URL": "postgresql://...",
+        "API_KEYS": "gemini:AIza..."
+      }
+    }
+  }
+}
+```
+
+### 3. Done!
+
+Ask your AI: "Remember that I prefer dark mode and use FastAPI"
+
+---
+
+## Configuration
+
+| Variable | Required | Description |
+|----------|----------|-------------|
+| `DATABASE_URL` | Yes | PostgreSQL with pgvector extension |
+| `API_KEYS` | Yes | `provider:key` pairs, comma-separated |
+| `LLM_MODELS` | No | Model fallback chain |
+| `EMBEDDER_MODELS` | No | Embedding model chain |
+
+### Supported Providers
+
+`gemini`, `openai`, `anthropic`, `groq`, `deepseek`, `mistral`
+
+### Examples
+
+**Single provider:**
+```bash
+API_KEYS=gemini:AIza...
+```
+
+**Multi-key with fallback:**
+```bash
+API_KEYS=gemini:AIza-1,gemini:AIza-2,openai:sk-xxx
+LLM_MODELS=gemini/gemini-3-flash-preview,openai/gpt-4o-mini
+EMBEDDER_MODELS=gemini/gemini-embedding-001,openai/text-embedding-3-small
+```
+
+### Defaults
+
+| Setting | Default |
+|---------|---------|
+| `LLM_MODELS` | `gemini/gemini-3-flash-preview` |
+| `EMBEDDER_MODELS` | `gemini/gemini-embedding-001` |
+
+---
+
+## Tools
+
+| Tool | Description |
+|------|-------------|
+| `memory` | Memory operations: `add`, `search`, `list`, `delete` |
+| `help` | Get full documentation for tools |
+
+### Usage Examples
+
+```json
+{"action": "add", "content": "I prefer TypeScript over JavaScript"}
+{"action": "search", "query": "programming preferences"}
+{"action": "list"}
+{"action": "delete", "memory_id": "abc123"}
+```
+
+---
+
+## Build from Source
+
+```bash
+git clone https://github.com/n24q02m/better-mem0-mcp
+cd better-mem0-mcp
+
+# Setup (requires mise: https://mise.jdx.dev/)
+mise run setup
+
+# Run
+uv run better-mem0-mcp
+```
+
+**Requirements:** Python 3.13+
+
+---
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md)
+
+## License
+
+MIT - See [LICENSE](LICENSE)

better_mem0_mcp-1.1.0b21/SECURITY.md

@@ -0,0 +1,32 @@
+# Security Policy
+
+## Supported Versions
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 1.x.x   | :white_check_mark: |
+| < 1.0   | :x:                |
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability, please **DO NOT** create a public issue.
+
+Instead, please email: **quangminh2402.dev@gmail.com**
+
+Include:
+
+1. Detailed description of the vulnerability
+2. Steps to reproduce
+3. Potential impact
+4. Suggested fix (if any)
+
+You will receive acknowledgment within 48 hours.
+
+## Security Best Practices
+
+When using better-mem0-mcp:
+
+- **Never commit API keys** to version control
+- Use environment variables or secure secret management
+- Keep dependencies updated
+- Use `sslmode=require` for production database connections

{better_mem0_mcp-1.1.0b20 → better_mem0_mcp-1.1.0b21}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "better-mem0-mcp"
-version = "1.1.0-beta.20"
+version = "1.1.0-beta.21"
 description = "Zero-setup MCP Server for AI memory - works with Neon/Supabase"
 readme = "README.md"
 license = { text = "MIT" }

better_mem0_mcp-1.1.0b20/README.md

@@ -1,120 +0,0 @@
-# better-mem0-mcp
-
-**Zero-setup** MCP Server for AI memory. Works with Neon/Supabase free tier.
-
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
-
-## Quick Start
-
-### 1. Get Prerequisites
-
-- **Database**: [Neon](https://neon.tech) or [Supabase](https://supabase.com) (free tier)
-- **API Key**: [Google AI Studio](https://aistudio.google.com/apikey) (free tier)
-
-### 2. Add to mcp.json
-
-#### uvx (Recommended)
-
-```json
-{
-  "mcpServers": {
-    "better-mem0": {
-      "command": "uvx",
-      "args": ["better-mem0-mcp@latest"],
-      "env": {
-        "DATABASE_URL": "postgresql://user:pass@xxx.neon.tech/neondb?sslmode=require",
-        "API_KEYS": "gemini:AIza..."
-      }
-    }
-  }
-}
-```
-
-#### Docker
-
-```json
-{
-  "mcpServers": {
-    "better-mem0": {
-      "command": "docker",
-      "args": ["run", "-i", "--rm", "-e", "DATABASE_URL", "-e", "API_KEYS", "n24q02m/better-mem0-mcp:latest"],
-      "env": {
-        "DATABASE_URL": "postgresql://...",
-        "API_KEYS": "gemini:AIza..."
-      }
-    }
-  }
-}
-```
-
-### 3. Done!
-
-Ask Claude: "Remember that I prefer dark mode and use FastAPI"
-
----
-
-## Configuration
-
-| Variable | Required | Description |
-|----------|----------|-------------|
-| `DATABASE_URL` | Yes | PostgreSQL connection string |
-| `API_KEYS` | Yes | `provider:key,...` (multi-key per provider OK) |
-| `LLM_MODELS` | No | `provider/model,...` (fallback chain) |
-| `EMBEDDER_MODELS` | No | `provider/model,...` (fallback chain) |
-
-### Examples
-
-**Minimal (Gemini only):**
-```
-API_KEYS=gemini:AIza...
-```
-
-**Multi-key with fallback:**
-```
-API_KEYS=gemini:AIza-1,gemini:AIza-2,openai:sk-xxx
-LLM_MODELS=gemini/gemini-2.5-flash,openai/gpt-4o-mini
-EMBEDDER_MODELS=gemini/gemini-embedding-001,openai/text-embedding-3-small
-```
-
-### Defaults
-
-| Setting | Default |
-|---------|---------|
-| `LLM_MODELS` | `gemini/gemini-2.5-flash` |
-| `EMBEDDER_MODELS` | `gemini/gemini-embedding-001` |
-
----
-
-## Tools
-
-| Tool | Description |
-|------|-------------|
-| `memory` | `action`: add, search, list, delete |
-| `help` | Detailed documentation |
-
-### Usage
-
-```json
-{"action": "add", "content": "I prefer TypeScript over JavaScript"}
-{"action": "search", "query": "preferences"}
-{"action": "list"}
-{"action": "delete", "memory_id": "abc123"}
-```
-
----
-
-## Why better-mem0-mcp?
-
-| Feature | Official mem0-mcp | better-mem0-mcp |
-|---------|-------------------|-----------------|
-| Storage | Mem0 Cloud | **Self-hosted PostgreSQL** |
-| Graph Memory | No | **Yes (SQL-based)** |
-| LLM Provider | OpenAI only | **Any (Gemini/OpenAI/Ollama/...)** |
-| Fallback | No | **Yes (multi-key + multi-model)** |
-| Setup | API Key | **DATABASE_URL + API_KEYS** |
-
----
-
-## License
-
-MIT

better_mem0_mcp-1.1.0b20/SECURITY.md

@@ -1,27 +0,0 @@
-# Security Policy
-
-## Supported Versions
-
-| Version | Supported          |
-| ------- | ------------------ |
-| 0.x.x   | :white_check_mark: |
-
-## Reporting a Vulnerability
-
-If you discover a security vulnerability, please report it by:
-
-1. **Do NOT** create a public GitHub issue
-2. Email the maintainer directly or use GitHub's private vulnerability reporting
-3. Include detailed steps to reproduce the issue
-4. Allow reasonable time for a fix before public disclosure
-
-We take security seriously and will respond promptly to valid reports.
-
-## Security Best Practices
-
-When using better-mem0-mcp:
-
-- **Never commit API keys** to version control
-- Use environment variables or secure secret management
-- Keep dependencies updated
-- Use `sslmode=require` for production database connections