MarsNMe is an MCP-compatible memory backend that stores short-term and long-term memories in a Supabase database and supports semantic recall via Jina embeddings. It lets multiple AI clients share continuity across sessions using isolated profiles selected by `MCP_PROFILE`.
From the registry: Agent-agnostic memory backend that preserves continuity between humans and AI over time.

$ curl -fsSL https://marsnme.com/install.sh | bashhttps://marsnme.com/install.sh/$ npx supabase db push --db-url "<your-supabase-db-connection-string>"Please install the `marsnme` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install MarsNMe gateway** — Install the MarsNMe gateway using the recommended one-line installer. Run: `curl -fsSL https://marsnme.com/install.sh | bash` (https://marsnme.com/install.sh/)
- **Create a Supabase project** — Create a Supabase project and collect the project URL for SUPABASE_BASE_URL and the service_role key for SUPABASE_SERVICE_ROLE_KEY. Keep the service role key private. (https://supabase.com/dashboard/new)
- **Create a Jina API key** — Create a Jina API key for semantic search embeddings. (https://jina.ai/api-key/)
- **Run Supabase migrations** — Before first start, apply the required database migrations to your Supabase Postgres database. The recommended method is Supabase CLI with a DDL-capable database role. Run: `npx supabase db push --db-url "<your-supabase-db-connection-string>"`
Canonical MCP server config (HTTP transport):
- url: `http://127.0.0.1:<your-port>/mcp`
- headers:
- `Authorization`: `Bearer <your-token>`
Note: MarsNMe exposes an HTTP MCP endpoint, not stdio. Start the gateway with: MCP_PROFILE=<your-profile> PORT=<your-port> npx @marsnme/mcp-gateway. Required runtime environment variables: MCP_PROFILE, SUPABASE_BASE_URL, SUPABASE_SERVICE_ROLE_KEY, JINA_API_KEY. PORT is optional; if omitted, a deterministic profile-based port is used. Optional auth/security variables: MCP_REQUIRE_BEARER, MCP_CLIENT_ID, MCP_CLIENT_SECRET. Optional headers are only needed when bearer auth is enabled (MCP_REQUIRE_BEARER=true).
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.SUPABASE_BASE_URLrequiredSupabase project URL used to connect to the database/APISUPABASE_SERVICE_ROLE_KEYrequiredSupabase service role key used for database access and migrationsJINA_API_KEYrequiredAPI key for Jina semantic embeddings/searchMCP_PROFILESelects the memory profile/namespace for a given agent or use caseMCP server for interacting with the Supabase platform