insert_memoryLABSCO SUMMARY
Recall in three steps, so a lookup does not dump the whole chunk.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
Build from source — git clone https://github.com/Marsmanleo/MarsNMe.git
USE CASES
01
Carrying context between different AI tools
One gateway URL added to each client means what you decided in one tool is readable in the next, without re-explaining the project.
02
Looking something up without flooding the context
Start with previews, widen to a summary on the ones that look right, and only fetch a full chunk when it earns the space.
03
Ending a session cleanly
Closing summarises the session and automatically promotes short-term memories that were about to expire, so nothing useful ages out silently.
04
Checking the memory is healthy
Coverage, expiry and conflict diagnostics in one call, with provenance available per memory when something looks wrong.
16 tools
Listed in project docs. Your client may show a different list.
list_memoriessearch_memoriesrecallget_summaryget_fullmemory_ingestdream_ingestsession_bootsession_closehealth_checkreload_source_registrydemote_memorysoft_forgetexplain_memorybatch_promoteBEFORE YOU INSTALL
What to know first
Tools you get
16 tools named in the project's documentation. The five PRD tools (save_prd, get_prd, list_prds, score_prd, spawn_to_linear) were removed in v0.3.0, so older listings show more. An older server card in the repo, stamped version 0.2.2, still lists 14 tools.
Requires
- Node.js 20 or later
- A Supabase project (SUPABASE_BASE_URL and SUPABASE_SERVICE_ROLE_KEY) with the vector extension enabled
- A Jina API key (JINA_API_KEY) — free tier available at https://jina.ai/api-key/
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/Marsmanleo/MarsNMe.git
cd MarsNMe
cp .env.example .envFill SUPABASE_BASE_URL, SUPABASE_SERVICE_ROLE_KEY, JINA_API_KEY in .env
In your Supabase project, enable the vector extension first (Database → Extensions), then run the migrations with the Postgres connection string from Project Settings → Database → Connection string:
TERMINAL
npx supabase db push --db-url "<YOUR_DB_URL>"Start the gateway and keep it running — every client below connects to it at http://127.0.0.1:18790/mcp:
TERMINAL
MCP_PROFILE=profile-a PORT=18790 npx @marsnme/mcp-gateway
curl -sS http://127.0.0.1:18790/healthMCP Clients
Cursor
How: Cursor Settings -> search for MCP -> Add a new server
Name: marsnme-cf
URL: http://127.0.0.1:18790/mcp
Headers: optional bearer header if enabled
Warp
How: Settings > Agents > MCP servers
URL: http://127.0.0.1:18790/mcp
Perplexity
PERPLEXITY · URL
http://127.0.0.1:18790/mcpAny MCP client — HTTP
ANY MCP CLIENT — HTTP · JSON
{
"mcpServers": {
"marsnme-cf": {
"url": "http://127.0.0.1:18790/mcp"
}
}
}
