Zep Cloud Memory MCP Server

Created By
kev-hu10 months ago
MCP Server for Zep Cloud provides a bridge between Claude Desktop and the Zep Cloud API, enabling memory management for AI assistants. Supports user management, collections management, and memory operations with persistent storage across conversations.
Overview

What is Zep Cloud MCP Server?

The Zep Cloud MCP Server provides seamless integration between AI assistants and Zep Cloud's memory management platform. It enables AI applications to maintain persistent memory across conversations and sessions.

Key Features

  • User Management: Complete CRUD operations for user accounts
  • Memory Collections: Organize memories into structured collections
  • Persistent Storage: Store and retrieve memories across sessions
  • Search Capabilities: Semantic search through stored memories
  • Modern Implementation: Built with FastMCP for efficiency
  • Fallback Mode: Graceful handling when Zep Cloud API is unavailable

Perfect For

  • AI coding assistants that remember your preferences
  • Conversational AI with long-term memory
  • Personal AI assistants with contextual awareness
  • Multi-session AI applications requiring persistence

Server Config

{
  "mcpServers": {
    "zep-cloud": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-zep-cloud"
      ],
      "env": {
        "ZEP_CLOUD_API_KEY": "YOUR_ZEP_CLOUD_API_KEY"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
kev-hu
Star
-
Language
-
License
-
Category

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)

5 hours ago
Alloy

2 days ago