Ext Ops Panel
Open dashboard
Comparison

EvolutionDB Long-Term Memory vs SAME - Stateless Agent Memory Engine

EvolutionDB Long-Term Memory is an MCP server published by alptekin. Marketplaces we read that list it: 1 (Official MCP Registry). SAME - Stateless Agent Memory Engine is an MCP server published by sgx-labs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceEvolutionDB Long-Term MemorySAME - Stateless Agent Memory Engine
Official MCP Registry Listed
Version: 1.17.0
No figure published
Not marked · First seen
Listed
Version: 0.12.1
Downloads/month (npm): 201
Downloads/week (npm): 45
Forks (GitHub): 0
Stars (GitHub): 23
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

EvolutionDB Long-Term Memory vs SAME - Stateless Agent Memory Engine
FactEvolutionDB Long-Term MemorySAME - Stateless Agent Memory Engine
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub23
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp-server-evolutiondb)On your machine (@sgx-labs/same)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)7, secrets among them: 11, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/alptekin/evolutiondbgithub.com/sgx-labs/statelessagent
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

EvolutionDB Long-Term Memory

In its own words, on Official MCP Registry:

Persistent long-term memory for Claude Desktop / Claude Code, backed by EvolutionDB.

SAME - Stateless Agent Memory Engine

In its own words, on Official MCP Registry:

Persistent memory for AI coding agents. Local-first SQLite + vector search. 17 MCP tools.

How to run each

EvolutionDB Long-Term Memory As a local MCP server: PyPI package

Claude Code
claude mcp add --env "EVOSQL_PASSWORD=<YOUR_EVOSQL_PASSWORD>" --env "MCP_USER_ID=<YOUR_MCP_USER_ID>" --transport stdio evolutiondb-memory -- uvx mcp-server-evolutiondb

Requires: EVOSQL_PASSWORD (secret), MCP_USER_ID

SAME - Stateless Agent Memory Engine As a local MCP server: npm package

Claude Code
claude mcp add --env "VAULT_PATH=<YOUR_VAULT_PATH>" --transport stdio same -- npx -y @sgx-labs/same mcp

Requires: VAULT_PATH

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only EvolutionDB Long-Term Memory asks for

  • EVOSQL_DATABASE
  • EVOSQL_HOST
  • EVOSQL_PASSWORD (secret)
  • EVOSQL_PORT
  • EVOSQL_USER
  • MCP_STORE_PREFIX
  • MCP_USER_ID

Only SAME - Stateless Agent Memory Engine asks for

  • VAULT_PATH

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: EvolutionDB Long-Term Memory · What it can do: SAME - Stateless Agent Memory Engine · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built