recall returns previews, get_summary widens, get_full commits — you spend context only on the chunk that turned out to be relevant. Because the store is your own Supabase project, moving off it later is an export rather than a negotiation.
A memory gateway backed by your own Supabase project. Short-term memories expire; long-term chunks are recalled by semantic search over Jina embeddings. The data sits in a database you own.
- 16 tools
- Short-term memory written, listed and searched semantically — insert_memory, list_memories, search_memories
- Long-term recall in three widening steps: roughly 80-character previews, then a roughly 300-character excerpt, then the complete chunk — recall, get_summary, get_full
- Long-term ingestion, including a dream-mode variant — memory_ingest, dream_ingest
- Sessions opened with context pre-loaded and closed with a summary, which also promotes soon-expiring memories — session_boot, session_close
- Lifecycle control — demote_memory, soft_forget, batch_promote, explain_memory for provenance, and health_check for coverage, expiry and conflicts
- reload_source_registry to refresh the source whitelist without restarting
- Unlimited isolated profiles through MCP_PROFILE, so one deployment can hold several separate memories
Node.js 20 or later, a Supabase project and a Jina API key. SUPABASE_BASE_URL, SUPABASE_SERVICE_ROLE_KEY, JINA_API_KEY and MCP_PROFILE are required, and the SQL migrations must be run — with the vector extension enabled first — before the first start. npx @marsnme/mcp-gateway serves Streamable HTTP at http://127.0.0.1:18790/mcp. A hosted setup wizard at mcp.marsnme.com/setup issues a personal URL instead.
One command plus a key — npx @marsnme/mcp-gateway, then supply credentials