MCP Memory with Redis Graph

Created By
samwang0723a year ago
MCP Server for long term memory graph
Overview

What is MCP Memory?

MCP Memory is a server that implements a memory system for long-term storage of conversations with large language models (LLMs) using Redis Graph as the backend.

How to use MCP Memory?

To use MCP Memory, set up the environment by installing Docker and Node.js, then run the Redis container and the application using Docker Compose and npm commands.

Key features of MCP Memory?

  • Store various types of memories (conversations, projects, tasks, etc.)
  • Create relationships between memories to form a knowledge graph
  • Search and retrieve memories based on different criteria
  • Update and delete memories as needed

Use cases of MCP Memory?

  1. Storing and retrieving project details and configurations.
  2. Managing tasks and to-do items for better organization.
  3. Recording and handling issues or bugs in software development.
  4. Providing personal finance advice and tracking financial information.

FAQ from MCP Memory?

  • What types of memories can be stored?

MCP Memory supports various types including conversations, projects, tasks, issues, configurations, finance, and todos.

  • How do I connect to Redis?

The application connects to Redis using the default configuration in src/index.ts, which can be modified as needed.

  • Is there a way to visualize the memory graph?

Yes, you can use the provided Redis CLI helper to inspect the graph and view relationships between memories.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
samwang0723
Star
0
Language
TypeScript
License
-
Tags

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)

20 hours ago
Gpt Scrambler

2 days ago