Developer · Local MCP server
EvolutionDB Long-Term Memory
Persistent long-term memory for Claude Desktop / Claude Code, backed by EvolutionDB.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.alptekin/evolutiondb-memory- Version
- 1.17.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-06-22
- Updated
- 2026-06-22
- Publisher
- alptekin (GitHub)
- Repository
- github.com/alptekin/evolutiondb (folder client/mcp-server-evosql)
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: python3 | mcp-server-evolutiondb | 1.17.0 | stdio |
How to connect EvolutionDB Long-Term Memory
EvolutionDB Long-Term Memory runs locally from a Python package published to PyPI: mcp-server-evolutiondb version 1.17.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx mcp-server-evolutiondb; the entry names python3 as the runtime. It reads these environment variables: EVOSQL_HOST, EVOSQL_PORT, EVOSQL_USER, EVOSQL_PASSWORD (secret), EVOSQL_DATABASE, MCP_USER_ID (required) and MCP_STORE_PREFIX; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"evolutiondb-memory": {
"command": "uvx",
"args": [
"mcp-server-evolutiondb"
],
"env": {
"EVOSQL_HOST": "<value>",
"EVOSQL_PORT": "<value>",
"EVOSQL_USER": "<value>",
"EVOSQL_PASSWORD": "<secret>",
"EVOSQL_DATABASE": "<value>",
"MCP_USER_ID": "<value>",
"MCP_STORE_PREFIX": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Evidence Diff MCPExplain coarse Git and test-build evidence changes without source diff contents. Tools include... | Local · stdio |
| Evidence LogTamper-evident evidence log: signed heads, proofs, and recording salted digests of your records. | Remote · HTTP |
| EvidriftCatch TypeScript API and OpenAPI contract drift in AI-generated code, then revalidate it in CI. | Local · stdio |
| EVMoleLocal structured analysis of deployed EVM runtime bytecode. | Local · stdio |
| EvolveguardWraps the evolveguard CLI as a single generic MCP tool for agent-skill file safety checks. | Local · stdio |
| Exa Labs Exa Code MCPFind open-source libraries and fetch contextual code snippets by version to accelerate development… | Remote · HTTP |
| ExactGroundCheck npm/PyPI packages exist and that a function or method exists in an exact package version. | Remote · HTTP |
| ExcalidrawSecurity-hardened Excalidraw MCP server with auth, rate limiting, and 14 tools. | Local · stdio |