
Gnosis Memory
com.gnosismemoryPublished by gnosismemory.comOfficial publisherv1.0.2Updated Oct 24, 2026
Persistent memory and vector search for AI agents. Hosted, OAuth-protected via Google sign-in.
Overview
A hosted, OAuth-protected memory service that gives AI assistants persistent memory and vector search across sessions.
- What you can do
- Store information in a persistent memory that survives across conversations, so an assistant can recall earlier context instead of starting fresh each time. Retrieve relevant memories through vector search, letting the assistant pull back items by semantic similarity rather than exact keywords. Access is through a hosted remote endpoint rather than a local process, so the assistant connects directly to the service.
- When to use it
- Worth adding when you want an assistant to remember facts, preferences or prior work across separate sessions and to look them up semantically. Less useful for one-off conversations where nothing needs to persist.
- Requirements
- A remote connection to the hosted endpoint at gnosismemory.com. OAuth authentication is required, with sign-in through a Google account. No local runtime, packages, environment variables or headers are declared.
Installation
In SourceWeft
- Open Gnosis Memory in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.gnosismemory%2Fmemory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"gnosis-memory": {
"type": "http",
"url": "https://gnosismemory.com/"
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.0.2LatestSep 16, 2026
Score
60% 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 daysRequired25 pts
- Auth declaredRequired10 pts
- 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.