v1.3.0 — MCP SDK v2, iterative recall, complete action reference

Highlights

• MCP SDK v2 / protocol 2026-07-28: the stdio adapter now negotiates the protocol era per connection — modern clients get the 2026-07-28 revision, current hosts keep the classic initialize handshake with zero configuration. Remote OAuth MCP audited against the 2026-07-28 spec (no SSE or DCR surface; posture in docs/REMOTE_MCP.md).
• Migration 0008 — iterative HNSW scans: namespace-filtered vector recall stays complete as namespaces multiply (pgvector ≥0.8; guarded no-op below; safe for non-superuser migration roles). Numbers 0006/0007 are intentionally reserved.
• docs/ACTIONS.md: complete HTTPS reference for all 27 actions — any language, no source-reading required.
• Optional keepalive workflow for free-tier pause mitigation (opt-in via KEEPALIVE_ENABLED variable + token secrets).
• Toolchain: TypeScript 7, zod 4, MCP SDK packages 2.0, Node 24 CI.

Upgrade from 1.2.0

Additive only: pull, npm ci, apply migration 0008 through your controlled migration process, redeploy the memory (and optional mcp) Edge Functions, and confirm health reports release 1.3.0. No schema rewrites, no breaking API changes; protocol remains v1.

Ai-Memory-Free v1.2.0 — Modular Agent Memory

Ai-Memory-Free v1.2.0 turns the secure v0.2 core into a backwards-compatible, modular memory platform for any AI agent.

Highlights:

• protocol v1 capability discovery with eight modules and 27 actions
• portable checksummed export/import with lifecycle restoration
• pluggable embedding profiles with free gte-small as the default
• idempotent batch memory and an append-only agent activity journal
• provenance, freshness, evidence, contradiction, and document modules
• deterministic multi-namespace context bundles with strict character budgets
• optional remote MCP protected by Supabase Auth OAuth 2.1
• comprehensive AI-agent install and v0.2 upgrade contracts

Security:

• caller tokens remain SHA-256 hashed
• recoverable secrets remain encrypted with Supabase Vault
• all new tables are RLS-locked and service-role-only
• remote MCP rejects scoped/bootstrap tokens and never exposes secret tools
• portable files exclude secrets, credentials, OAuth grants, embeddings, audits, and rate limits

Upgrade:
Read docs/UPGRADE_V1_2.md and migration 0005 before applying. The migration is additive and every v0.2 action remains compatible.

Created by Kristian Peter — https://kristianpeter.com