List your agent

Gnosis Memory

MCP server● Hosted · onlinev1.0.2

Persistent memory and vector search for AI agents. Hosted, OAuth-protected via Google sign-in

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: answer customer questions.
All AI agents to answer customer questions, ranked →

Similar tools

Listed for the same task: answer customer questions

Reviews

No review yet. Used Gnosis Memory? Be the first to help others choose.

What it does

Gnosis Memory is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: knowledge base qa. That makes it a candidate for tasks such as answer customer questions or answer questions from internal documents.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.2
PriceNot in the registry
First seen26 Sept 2026
Last checked12h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)

Hosted endpoint

  • https://gnosismemory.com streamable-http

In Claude Code: claude mcp add --transport http gnosis-memory https://gnosismemory.com

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "gnosis-memory": {
      "url": "https://gnosismemory.com"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 2d ago

ONLINE Gnosis Memory answered an MCP connection on 14 Nov 2026 and introduced itself as gnosis-mcp 0.1.0 (MCP protocol 2025-06-18).

21 tools offered to AI assistants

  • init_core_memories · Run ONCE at conversation start. Loads behavioral prefs + recent context. Previews carry a 'complete' flag: true = full content shown; false = opening only, memory_retrieve(id) for the rest. After init, use memory_search for specific queries
  • memory_add · Store a memory. Several memories in one call -> memories=[{content, topics, ...}]; top-level topics then apply to every item. BEFORE params decide: (1) TYPE? (2) what search finds this later? (3) happened, or aspirational? (4) WHO must act
  • memory_add_batch · Store multiple memories at once. Same rules as memory_add, applied per item. SHAPE: one ITEM here == one memory_add call. Same field names, same meaning. The ONLY difference is the container: memory_add takes them as flat parameters, this t
  • memory_search · Search memories by relevance. Up to 32 results. Query = ALL nouns from the user's message, not just the main one (ranking is automatic). "How does the app cache API calls?" -> "app cache api calls" complete=false results are truncated -> me
  • memory_deep_search · Broad search for a FULL sweep -- every hit on a topic (e.g. before memory_consolidate), not a conversational lookup (that is memory_search). Up to 128 results; requires 2+ keywords ("python" alone = too broad). Scores: 30+ excellent, 20+ go
  • memory_retrieve · Get full content by ID. Use when search returned complete=false. Batch: memory_retrieve(["id1","id2"]). Skip if complete=true (preview is already full).
  • artifact_write · Store or update a long document (markdown, JSON or text) behind a pointer memory. For agents.md, skills.md, assertions.md, a project plan: anything past one memory's 768-token cap. CREATE: name ("assertions.md"), summary (the pointer memory
  • artifact_read · Read an artifact by its pointer memory id (memory_retrieve on a pointer shows an "artifact" block with head_rev_id and outline). Bodies over 40,000 characters return the outline: read a section (heading path or JSON pointer) or page=0,1,...
  • artifact_history · List the revisions of an artifact (rev_id, parent, seq, time, author, pinned) and its heads. conflict=true means divergent heads to merge.
  • artifact_pin · Pin a revision so retention thinning never removes it (pinned=false unpins).
  • artifact_delete · Delete an artifact: every revision and its pointer memory. Permanent. confirm must equal the artifact name. memory_delete refuses a pointer; use this.
  • artifact_orphans · List artifact revisions whose pointer memory is gone (a delete on one replica racing a save on another). Nothing is auto-deleted; export includes them.
Show 9 more
  • memory_edit · Edit a memory. Provide only what changes; omitted fields untouched. Modes: 1. Content replace (content [+topics/macro_topics]): full rewrite, re-embeds. Do it the instant the user corrects a memory ("actually..."). 2. Metadata patch (topics
  • memory_delete · Delete memories by ID. Permanent. memory_delete(["id1","id2"]). Delete by filter: memory_search first, collect ids, then delete.
  • memory_consolidate · Create/replace a topic's executive summary. One per topic; replacing archives the old (restorable). WARNING: a bad summary poisons every future session. Do NOT consolidate from partial knowledge. BEFORE calling: (1) memory_deep_search the t
  • task_feed · Recently-changed tasks, chronological (not ranked). For "what needs attention?" / "what changed?". Find tasks by content -> memory_search. Each: preview, progress [done,total], status, topics, collection. Default 32, max 500. Fan-out: no co
  • collection_manage · Manage shared collections (multi-user memory folders). list: your collections + invites. create. update: rename (display only; slug/keys unchanged). delete: owner only, 2-step -- call without confirm to see impact + token, repeat with confi
  • agent_manage · Manage agents (NAMESPACES under your account, sharing your token). An agent is a namespace, never a holder of key material: all crypto is the ACCOUNT's, and an agent id is never an input to a wrap, a seal or a KEK. Agents organise and scope
  • signal · Inter-agent signals -- sticky notes pointing at a memory_id. Both parties must share a collection. send: post to a teammate. check: read pending (removes nothing). ack: mark handled -- stamps delivered_at, the row stays, NOTHING IS DELETED.
  • message · Direct inter-agent text that DIES ON ACK. Use for receipts, FYIs and short replies; use signal to point at a memory. send/check/ack. LOSABLE BY DESIGN: the first session of the recipient name to ack deletes it for every session of that name
  • account · Account state + billing. Returns URLs only -- user clicks to pay; never charges silently. Pick by intent: "what plan am I on?" -> info (tier, subscription, capabilities, upgrade/downgrade SKUs; permanent tiers og/truebeliever/ogdev cannot d

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://gnosismemory.comDECLAREDSRC-001 Official MCP Registry12h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry12h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry12h ago
Websitehttps://gnosismemory.comDECLAREDSRC-001 Official MCP Registry12h ago
Repositoryhttps://github.com/Tekgnosis/GnosisMemoryDECLAREDSRC-001 Official MCP Registry12h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry12h ago
Version1.0.2DECLAREDSRC-001 Official MCP Registry12h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry12h ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Gnosis Memory? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor Gnosis MemoryLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Gnosis Memory?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/gnosis-memory?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/gnosis-memory/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Gnosis Memory

How do I connect Gnosis Memory?

Use the hosted endpoint https://gnosismemory.com in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does Gnosis Memory offer?

When Electra Index connected on 14 Nov 2026, it listed 21 tools: init_core_memories, memory_add, memory_add_batch, memory_search, memory_deep_search, memory_retrieve, artifact_write, artifact_read and more. The full list is in "Live check" above.

Is Gnosis Memory online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.

What can I use Gnosis Memory for?

Based on its description, it is most relevant to: answer customer questions, answer questions from internal documents, answer support phone calls, build a help center.