MCP Server Zep Cloud

🚀 Zep Cloud MCP Server

The Zep Cloud MCP Server serves as a bridge between Claude Desktop and the Zep Cloud API, enabling memory management for AI assistants.

🚀 Quick Start

Installation and Configuration

1. Clone the repository

git clone [your-repository-url]
cd mcp-server

2. Create and activate a virtual environment (recommended)

python -m venv venv
source venv/bin/activate  # On Windows, use `venv\Scripts\activate`
pip install -r requirements.txt

3. Configure environment variables

• Copy .env.example to .env and add your API key:

  cp .env.example .env
  nano .env
  

  Update the following content:

  ZEPCLOUD_API_KEY=your_api_key_here
  

4. Start the server

python core/zep_cloud_server.py

Usage Instructions

Access the tool via the terminal

• Visit http://localhost:5000 and log in with your Zep Cloud API key.
• Browse the available tools and use them as needed.

Configure Claude Desktop

1. Copy claude_desktop_config.json.example to claude_desktop_config.json:

   cp claude_desktop_config.json.example claude_desktop_config.json
   

2. Update the path and API key in the configuration file:

   {
     "mcp_server_url": "http://localhost:5000",
     "api_key": "your_api_key_here"
   }
   

Available Tools

• User Management: create_user, get_user, update_user, delete_user, list_users
• Collection Management: create_collection, get_collection, update_collection, delete_collection, list_collections
• Memory Operations: add_memory, get_memory, list_memories, search_memories

✨ Features

• User Management: Create, retrieve, update, and delete users in Zep Cloud.
• Collection Management: Create and manage memory collections.
• Memory Operations: Add, retrieve, and search memories.
• Modern Implementation: Utilize the FastMCP method for a more efficient and maintainable server.
• Fallback Mode: If unable to connect to the Zep Cloud API (due to authentication issues, network problems, etc.), switch to local mode, supporting only partial functionality.

📦 Installation

The installation steps are included in the "Quick Start" section above.

💻 Usage Examples

Basic Usage

The basic usage is described in the "Quick Start" section, including installation, configuration, and using available tools.

Advanced Usage

There is no specific advanced usage example provided in the original document.

📚 Documentation

Repository Structure

The repository is organized into the following directories:

• core/: Core functionality files

  • zep_cloud_client.py: Client implementation for the Zep Cloud API.
  • zep_cloud_server.py: MCP server providing tools for Claude Desktop.
  • run_server.py: Stand - alone script to directly run the server.

• scripts/: Operational utility scripts

  • check_user_exists.py: Check if a user exists in Zep Cloud.
  • create_specific_user.py: Script to create a specific user in Zep Cloud.
  • run_server.sh / run_server.bat: Shell scripts to run the server with environment settings.
  • Various other testing and debugging utility scripts.

• tests/: Test scripts organized by functionality

  • test_specific_user.py: Comprehensive tests for all user operations.
  • test_zep_cloud_client.py: Unit tests for the Zep Cloud client.
  • test_comprehensive.py: Complete API tests for all functions.

• config/: Configuration files

  • .env.example: Environment configuration template.
  • .env.new: Updated environment configuration.
  • claude_desktop_config.json.example: Configuration template for Claude Desktop.
  • requirements.txt: Package dependencies.

Security Considerations

API Key Protection

• Never commit API keys to version control. The .gitignore file is configured to ignore the .env file.
• Use the provided .env.example as a template and create your own .env file with the actual API key.

Configuration Files

• Personal configuration files such as claude_desktop_config.json contain system - specific paths and should not be committed to version control.
• Use the provided claude_desktop_config.json.example as a reference to create and update configuration files.

Troubleshooting

For troubleshooting information, refer to the AUTHENTICATION_NOTE.md document, which contains detailed information about API connectivity and authentication issues.

📄 License

There is no license information provided in the original document.

⚠️ Important Note

• Never commit API keys to version control. The .gitignore file is configured to ignore the .env file.
• Personal configuration files like claude_desktop_config.json contain system - specific paths and should not be committed to version control.

💡 Usage Tip

Use the provided .env.example as a template to create your own .env file with the actual API key, and use claude_desktop_config.json.example as a reference to create and update configuration files.