Mem0 General

Created By
ryakera year ago
OpenAI just added memory across your chats across your openAI account. But wouldn't it be awesome to have general AI memory across all your interactions with any and all AI tools, IDEs, chatbots.... Now if it supports MCP you can with https://mem0.ai/ Give Claude desktop memory. Give cursor or windsurf memory across sessions or different projects.
Overview

What is Mem0 General?

Mem0 General is a Model Context Protocol (MCP) server that integrates AI assistants with Mem0.ai's persistent memory system, allowing for enhanced memory management across various AI tools and platforms.

How to use Mem0 General?

To use Mem0 General, install the package via pip, configure it in your AI tool's settings, and restart the application to enable memory functionalities.

Key features of Mem0 General?

  • Integration with various AI assistants for memory management
  • Support for different memory types: episodic, semantic, procedural, and short-term
  • Ability to store, retrieve, and search memories with semantic similarity
  • Customizable memory categories and instructions
  • Feedback mechanism for memory quality improvement

Use cases of Mem0 General?

  1. Enhancing AI chatbots with persistent memory for better user interactions.
  2. Managing project-specific memories across different AI tools.
  3. Creating knowledge graphs to visualize relationships between memories.

FAQ from Mem0 General?

  • Can Mem0 General be used with any AI tool?

Yes! Mem0 General is designed to work with any MCP-compatible AI assistant.

  • Is there a cost associated with using Mem0 General?

Mem0 General is open-source and free to use under the MIT License.

  • How does Mem0 General handle memory privacy?

Mem0 General allows users to manage their memories and provides options for selective memory filtering.

Server Config

{
  "mcpServers": {
    "mem0-memory-general": {
      "command": "<PATH TO SERVER>/mcp-mem0-server",
      "args": [],
      "env": {
        "MEM0_API_KEY": "<YOUR MEM0 KEY>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ryaker
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)

2 days ago