MCP-Mem0: Your Gateway to Long-Term Agent Memory 🚀

Created By
yellnutsa year ago
MCP server for long term agent memory with Mem0. Also useful as a template to get you started building your own MCP server with Python!
Overview

What is MCP-Mem0?

MCP-Mem0 is a server designed for managing long-term agent memory using Mem0. It serves as a template for building your own MCP server with Python.

How to use MCP-Mem0?

To use MCP-Mem0, download the latest release from the Releases section, clone the repository, install dependencies, and run the server. Access the API via your web browser at http://localhost:5000.

Key features of MCP-Mem0?

  • Long-term memory management for efficient storage and retrieval.
  • Built with Python for easy customization.
  • Template structure for developing your own MCP server.
  • Lightweight with minimal resource requirements.

Use cases of MCP-Mem0?

  1. Managing memories for AI agents.
  2. Developing custom memory management solutions.
  3. Experimenting with long-term memory in machine learning applications.

FAQ from MCP-Mem0?

  • Can I customize MCP-Mem0?

Yes! MCP-Mem0 is built with Python, allowing for easy customization and extension.

  • Is there documentation available?

Yes! Detailed API documentation is provided in the repository.

  • What are the system requirements?

You need Python 3.6 or higher to run MCP-Mem0.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yellnuts
Star
0
Language
Python
License
MIT 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