Releases: Jartan-LLC/memcp
Releases · Jartan-LLC/memcp
v0.1.1
v0.1.0 — initial release
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
0.1.0 — 2026-06-14
Initial release.
Added
- MCP tools: add_memory, search_memory, delete_memory, delete_all_memories, memory_status, export_memories, import_memories, get_memory, update_memory, list_memories, memory_history, memory_entities
- Backend-agnostic architecture with
MemoryBackendProtocol - mem0 REST API adapter with tenant isolation (fetch-then-verify ownership)
- In-memory backend for dev/testing (
MEMCP_BACKEND=in_memory) - Multi-tenant auth via
MEMCP_AUTH_TOKENS(token:user_id mapping) - Pluggable auth via Resolver Protocol (static tokens now, DB/JWT planned)
- Import with dedup and conflict resolution (
on_conflict: skip, overwrite, duplicate) - Export with truncation for large memory pools
- Input validation: content/query length, limit bounds, threshold range, scope key/type/size
- Canonical error objects with retry semantics and standard error codes
/healthendpoint (pings backend, returns 200/503)- Structured JSON/plain logging with per-request tenant context
- Constant-time token comparison, scope injection protection, non-ASCII token handling
- Multi-stage Dockerfile + docker-compose
- CI pipeline with ruff, pyright, pytest, Docker build verification
- PyPI and Docker image publish workflows (on tag push)
- Backend selection via
MEMCP_BACKEND(mem0, in_memory) - Server config:
MEMCP_HOST,MEMCP_PORT,MEMCP_LOG_LEVEL,MEMCP_LOG_FORMAT