Ext Ops Panel
Open dashboard
Comparison

Kagi Search vs EvolutionDB Long-Term Memory

Kagi Search is an MCP server published by kagisearch. Marketplaces we read that list it: 1 (Docker MCP Catalog). EvolutionDB Long-Term Memory is an MCP server published by alptekin. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceKagi SearchEvolutionDB Long-Term Memory
Docker MCP Catalog Listed
Version: sha256:c26439346cd6
Forks (GitHub): 48
Pulls (Docker Hub): 19 843
Stars (Docker Hub): 1
Stars (GitHub): 541
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.17.0
No figure published
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

Kagi Search vs EvolutionDB Long-Term Memory
FactKagi SearchEvolutionDB Long-Term Memory
Marketplaces that list it11
Stars (GitHub) (differs)541No figure on GitHub
Pulls (Docker Hub) (differs)19 843No figure on Docker Hub
Forks (GitHub) (differs)48No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/kagisearch)On your machine (mcp-server-evolutiondb)
Transportstdiostdio
Tools it declares (differs)2Not published
Environment variables it asks for (differs)2, secrets among them: 17, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/kagisearch/kagimcpgithub.com/alptekin/evolutiondb
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

Kagi Search

In its own words, on Docker MCP Catalog:

The Official Model Context Protocol (MCP) server for Kagi Search & other tools.

EvolutionDB Long-Term Memory

In its own words, on Official MCP Registry:

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

How to run each

Kagi Search As a local MCP server: Docker image

Claude Code
claude mcp add --env "KAGI_API_KEY=<YOUR_KAGI_API_KEY>" --transport stdio kagisearch -- docker run -i --rm -e KAGI_API_KEY mcp/kagisearch

Requires: KAGI_API_KEY (secret)

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

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

Tools each declares

The marketplaces of EvolutionDB Long-Term Memory publish no list of tools, so we do not compare tools.

Settings each asks for

Only Kagi Search asks for

  • KAGI_API_KEY (secret)
  • KAGI_SUMMARIZER_ENGINE

Only EvolutionDB Long-Term Memory asks for

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

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

What it can do: Kagi Search · What it can do: EvolutionDB Long-Term Memory · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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