Evolutiondb Memory

Name: Evolutiondb Memory
Author: alptekin

by alptekincommunityv1.1.3

An MCP server for Claude Desktop and Claude Code that stores conversation facts as persistent long-term memory in EvolutionDB and lets the model search, list, and delete those memories in later sessions. It communicates over stdio JSON-RPC and talks to EvolutionDB using the PostgreSQL wire protocol.

From the registry: Persistent long-term memory for Claude Desktop / Claude Code, backed by EvolutionDB.

GitHub Repository

Install & configure

Prerequisites

required
Install the Python package
Install the MCP server package so the console entry point is available.
```
$ pipx install mcp-server-evolutiondb
```
required
Run EvolutionDB
EvolutionDB must be running and reachable by the MCP server. The README says the easiest setup is to start it from the main EvolutionDB repo with Docker Compose.
```
$ docker compose up -d
```
https://github.com/alptekin/evolutiondb

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `evolutiondb-memory` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Install the Python package** — Install the MCP server package so the console entry point is available. Run: `pipx install mcp-server-evolutiondb`
- **Run EvolutionDB** — EvolutionDB must be running and reachable by the MCP server. The README says the easiest setup is to start it from the main EvolutionDB repo with Docker Compose. Run: `docker compose up -d` (https://github.com/alptekin/evolutiondb)

Canonical MCP server config (stdio transport):
- command: `mcp-server-evolutiondb`
- args: []
- optional environment variables:
  - `EVOSQL_HOST`: EvolutionDB host. (example: `<your-evolutiondb-host>`)
  - `EVOSQL_PORT`: EvolutionDB port. (example: `<your-evolutiondb-port>`)
  - `EVOSQL_USER`: EvolutionDB username. (example: `<your-evolutiondb-user>`)
  - `EVOSQL_PASSWORD`: EvolutionDB password. (example: `<your-evolutiondb-password>`)
  - `MCP_USER_ID`: Sticky user namespace applied server-side to all tool calls. (example: `<your-user-id>`)
  - `MCP_STORE_PREFIX`: Catalog object prefix used for memory storage objects. (example: `<your-store-prefix>`)
  - `EVOSQL_PYTHON_SDK`: Override path to the Python ctypes binding if auto-discovery is not suitable. (example: `<path-to-python-sdk-binding>`)
  - `EVOSQL_MEMORY_LIB`: Override path to the libevosql-memory shared library if auto-discovery is not suitable. (example: `<path-to-libevosql-memory-library>`)

Note: The README also mentions the console entry-point alias `mcp-server-evosql`. Preferred portable config uses the installed package entry point `mcp-server-evolutiondb`. Although the README's older setup mentions building the SDK once, the package install section says installation is pure Python and the SDK/library paths are auto-discovered, so the pipx-installed console entry point is the simplest install path.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: The README also mentions the console entry-point alias `mcp-server-evosql`. Preferred portable config uses the installed package entry point `mcp-server-evolutiondb`. Although the README's older setup mentions building the SDK once, the package install section says installation is pure Python and the SDK/library paths are auto-discovered, so the pipx-installed console entry point is the simplest install path.