memory-mcp-server

Created By
ta-tomschella year ago
A long-term memory storage system for LLMs using the Model Context Protocol (MCP) standard. This system helps LLMs remember the context of work done over the entire history of a project, even across multiple sessions. It uses semantic search with embeddings to provide relevant context from past interactions and development decisions.
Overview

what is memory-mcp-server?

Memory-mcp-server is a long-term memory storage system designed for Large Language Models (LLMs) that utilizes the Model Context Protocol (MCP) standard. It enables LLMs to retain the context of work done throughout the entire history of a project, even across multiple sessions.

how to use memory-mcp-server?

To use memory-mcp-server, integrate it with your LLM application by following the setup instructions provided in the GitHub repository. Once integrated, the system will automatically manage context retention and retrieval based on past interactions.

key features of memory-mcp-server?

  • Long-term memory storage for LLMs
  • Context retention across multiple sessions
  • Semantic search capabilities using embeddings for relevant context retrieval

use cases of memory-mcp-server?

  1. Enhancing LLMs with the ability to remember user preferences over time.
  2. Supporting complex projects where context from previous sessions is crucial for continuity.
  3. Improving user interactions by providing relevant historical context during conversations.

FAQ from memory-mcp-server?

  • How does memory-mcp-server ensure data privacy?

Memory-mcp-server is designed with privacy in mind, ensuring that all stored data is handled securely and in compliance with data protection standards.

  • Can memory-mcp-server be used with any LLM?

Yes! Memory-mcp-server is compatible with various LLMs that support the Model Context Protocol (MCP).

  • Is there a limit to the amount of context that can be stored?

The storage capacity depends on the implementation and resources allocated to the memory-mcp-server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ta-tomschell
Star
0
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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