MarsNMe

io.github.MarsmanleoPublished by GitHub account Marsmanleov0.3.2Updated Oct 24, 2026

Agent-agnostic memory backend that preserves continuity between humans and AI over time.

VerifiedSTDIODesktop onlyDatabasesKnowledge & Memory

Overview

AI-generated overview

A local MCP gateway that gives an AI assistant a persistent memory backend, storing and recalling context across sessions through a Supabase database.

What you can do
Store and recall memory entries for a named profile, keeping continuity between conversations over time (tools are not listed in the manifest). Serve memory tools over a local streamable HTTP endpoint at POST /mcp, with a health check at GET /health. Use Jina embeddings for semantic memory search. Separate memory data per profile ID, with optional bearer-token or OAuth protection on MCP calls.
When to use it
Use it when you want an assistant to remember people, preferences or prior context across sessions and you are willing to run a local gateway backed by your own Supabase project. It suits desktop setups where a single user or a few named profiles share one memory store.
Requirements
Node.js 20 or later, run via npx. A Supabase project with the required schema migrations applied, plus SUPABASE_BASE_URL and SUPABASE_SERVICE_ROLE_KEY. A Jina API key in JINA_API_KEY for embedding-based search. MCP_PROFILE is required; PORT is optional. Desktop only.
Before you install
The Supabase service role key bypasses row-level security, so keep it private and point it only at a database you control. Memory content is sent to Supabase and, for embeddings, to Jina. The gateway writes to your database, and upgrades require running migrations with a DDL-capable role. Bearer or OAuth protection is optional and off unless configured.

Installation

In SourceWeft

  1. Open MarsNMe in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@marsnme/mcp-gateway

[MarsNMe demo]

MarsNMe MCP Gateway for memory tools over streamable HTTP transport.

This package runs an MCP server at POST /mcp and exposes health status at GET /health.

Requirements

  • Node.js >=20
  • Supabase project with required schema migrations applied
  • Jina API key for embedding-based memory search

Quick start (npx)

bash
MCP_PROFILE=coco \SUPABASE_BASE_URL=https://<your-project-ref>.supabase.co \SUPABASE_SERVICE_ROLE_KEY=<your-service-role-key> \JINA_API_KEY=<your-jina-api-key> \npx -y @marsnme/mcp-gateway

After startup:

  • Health: http://127.0.0.1:18790/health
  • MCP endpoint: http://127.0.0.1:18790/mcp

Required environment variables

  • MCP_PROFILE
    • Any lowercase profile ID matching ^[a-z][a-z0-9_-]*$ (for example: coco, toto, my-agent)
    • Legacy built-in IDs: coco and toto
  • SUPABASE_BASE_URL
    • Your Supabase REST project URL
  • SUPABASE_SERVICE_ROLE_KEY (recommended) or SUPABASE_SERVICE_KEY
    • Service role key used for database operations
  • JINA_API_KEY
    • Required for semantic search / embedding features

Common optional environment variables

  • PORT
    • Overrides the HTTP port used by the gateway
    • If omitted, the gateway resolves a profile-based default:
      • coco → 18790
      • toto → 18791
      • other profile IDs → deterministic port in 20000-29999
  • MCP_REQUIRE_BEARER
    • Set true to require Authorization: Bearer <token> on MCP calls
  • MCP_OAUTH_ENABLED
    • OAuth endpoints are enabled by default (set false to disable)
  • MCP_CLIENT_ID and MCP_CLIENT_SECRET
    • Optional static OAuth client credentials

Minimal validation

Check service health:

bash
curl -sS http://127.0.0.1:18790/health

List tools:

bash
curl -sS http://127.0.0.1:18790/mcp \  -H 'content-type: application/json' \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Deployment safety gate (before restart)

For upgrades, run database migrations with an explicit DDL-capable role and gate schema compatibility before restarting services.

Recommended role guidance:

  • Use a role that can execute DDL on target schemas.
  • On Supabase-hosted Postgres this is typically supabase_admin (not postgres).

Schema gate command:

bash
bash deploy/phase2/pre_deploy_schema_gate.sh \  --db-url "<postgres://supabase_admin:<password>@<host>:5432/postgres>" \  --profiles coco,toto \  --expected-role supabase_admin
  • If gate exits non-zero, stop deployment and do not restart services.

Database setup and full onboarding

For migrations and full setup details:

Source: marsnme-supabase/README.md at commit cf67212

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.3.2LatestOct 18, 2026
  2. v0.3.0Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts