This repository contains the MCP (Model Context Protocol) server for the ZepAi module. The server is configured to run using a specific command and
Mcp zepai mcp server lets Claude, Cursor and other MCP clients work with MCP ZepAi directly. This repository contains the MCP (Model Context Protocol) server for the ZepAi module. The server is configured to run using a specific command and environment variables as detailed below.
This repository contains the MCP (Model Context Protocol) server for the ZepAi module. The server is configured to run using a specific command and environment variables as detailed below.
Once connected, the assistant can call these 4 tools directly:
command — The command to execute the server, in this case, using uvargs — Arguments passed to the command, including the directory and module to runcwd — The current working directory for the serverenv — Environment variables required for the server, such as ZEP_API_KEYSetup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.
Before the server will start you need to supply one environment variable: ZEP_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.
File and storage servers are what separate an assistant that talks about your documents from one that actually works with them. MCP ZepAi sits in that group, and the shape of its toolset — command, args, cwd among others — tells you what it is really for. Worth comparing against the other file systems servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| command | The command to execute the server, in this case, using uv. |
| args | Arguments passed to the command, including the directory and module to run. |
| cwd | The current working directory for the server. |
| env | Environment variables required for the server, such as ZEP_API_KEY. |
{
"mcpServers": {
"zepai": {
"command": "uv",
"args": [
"run",
"--directory",
"<path_to_the_mcp_directory>",
"python",
"-m",
"mcp_zepai"
],
"cwd": "<path_to_the_mcp_directory>",
"env": {
"ZEP_API_KEY": "<your_api_key_here>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ZEP_API_KEY | Credential the server authenticates with. | Yes |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.