Memento

Created By
gannonha year ago
Overview

What is Memento?

Memento is a scalable knowledge graph memory system designed for large language models (LLMs) that provides persistent ontological memory with advanced relation management and semantic search capabilities.

How to use Memento?

To use Memento, set up a Neo4j database and configure it with the required environment variables. You can then interact with the system through the Model Context Protocol (MCP) to manage entities and relations.

Key features of Memento?

  • Scalable knowledge graph with semantic search capabilities.
  • Temporal awareness for tracking changes over time.
  • Advanced relation management with confidence decay.
  • Support for multiple embedding models for semantic search.

Use cases of Memento?

  1. Enhancing LLMs with persistent memory for improved context retention.
  2. Semantic search for retrieving related entities based on meaning.
  3. Temporal analysis of knowledge evolution over time.

FAQ from Memento?

  • What is the storage backend for Memento?

Memento uses Neo4j as its storage backend for both graph and vector search capabilities.

  • How do I set up Memento?

You can set up Memento by installing Neo4j and configuring the necessary environment variables as outlined in the documentation.

  • Can Memento be integrated with other LLMs?

Yes, Memento is designed to work with any LLM client that supports the model context protocol.

Server Config

{
  "mcpServers": {
    "memento": {
      "command": "npx",
      "args": [
        "-y",
        "@gannonh/memento-mcp"
      ],
      "env": {
        "MEMORY_STORAGE_TYPE": "neo4j",
        "NEO4J_URI": "bolt://127.0.0.1:7687",
        "NEO4J_USERNAME": "neo4j",
        "NEO4J_PASSWORD": "memento_password",
        "NEO4J_DATABASE": "neo4j",
        "NEO4J_VECTOR_INDEX": "entity_embeddings",
        "NEO4J_VECTOR_DIMENSIONS": "1536",
        "NEO4J_SIMILARITY_FUNCTION": "cosine",
        "OPENAI_API_KEY": "your-openai-api-key",
        "OPENAI_EMBEDDING_MODEL": "text-embedding-3-small"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gannonh
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago