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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago