🧠 Memory MCP Server

Created By
Sinhan88a year ago
A MCP (Model Context Protocol) server providing long-term memory for LLMs
Overview

What is Memory MCP Server?

Memory MCP Server is a server that implements the Model Context Protocol (MCP) to provide long-term memory for Large Language Models (LLMs), enabling them to retain information over extended interactions.

How to use Memory MCP Server?

To use the Memory MCP Server, clone the repository, install the dependencies, and run the server. You can then interact with it using API endpoints to store and retrieve memory.

Key features of Memory MCP Server?

  • Long-term memory storage and retrieval for LLMs.
  • Adherence to the Model Context Protocol for seamless integration.
  • User-friendly API for easy integration into applications.
  • Scalability to handle multiple requests.

Use cases of Memory MCP Server?

  1. Enhancing conversational AI by retaining user context.
  2. Improving personalized recommendations in AI applications.
  3. Supporting complex interactions in AI-driven customer service.

FAQ from Memory MCP Server?

  • Can I use Memory MCP Server with any LLM?

Yes! It is designed to work with various LLM architectures that adhere to the MCP standards.

  • Is there a cost to use Memory MCP Server?

No, it is open-source and free to use.

  • How do I contribute to the project?

You can contribute by forking the repository, making changes, and submitting a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Sinhan88
Star
1
Language
-
License
MIT license

Recommend Servers

View All
Alloy

2 days 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)

12 hours ago
Crevio

a day ago