Ext Ops Panel
Open dashboard
Comparison

agent-memory vs Qdrant Memory

agent-memory is a plugin bundle for AI coding tools published by Keshab0310. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Qdrant Memory is an MCP server published by cnkang. 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
Marketplaceagent-memoryQdrant Memory
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 2
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Forks (GitHub): 0
Stars (GitHub): 0
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

agent-memory vs Qdrant Memory
Factagent-memoryQdrant Memory
Marketplaces that list it11
Stars (GitHub) (differs)3 (better)0 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last release (differs)Not published2026-10-13
Where it runs (differs)Installs as a plugin bundleOn your machine (qdrant-memory-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 03, secrets among them: 2
Hooks it runs (differs)2Not published
Parts of the bundle (differs)4Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/keshab0310/agent-memorygithub.com/cnkang/qdrant-memory-mcp
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-10-13

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

agent-memory

In its own words, on Claude Code: claude-plugins-community:

Save 60-90% on LLM token costs with intelligent memory compression. agent-memory automatically compresses tool output into structured observations, shares context across agents via a memory bus, and injects only relevant memory into each prompt — keeping your token budget under control. Features: auto-compression hooks (PostToolUse), token-budgeted context injection (SessionStart), semantic search via FTS5, cross-session persistence, and a token economics dashboard showing compression ratios and savings.

Qdrant Memory

In its own words, on Official MCP Registry:

Persistent scoped Qdrant memory for agents, through four explicit stdio MCP tools.

How to run each

agent-memory As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install agent-memory@claude-community

Qdrant Memory As a local MCP server: PyPI package

Claude Code
claude mcp add --env "EMBEDDING_API_KEY=<YOUR_EMBEDDING_API_KEY>" --env "QDRANT_API_KEY=<YOUR_QDRANT_API_KEY>" --transport stdio qdrant-memory -- uvx qdrant-memory-mcp mcp

Requires: EMBEDDING_API_KEY (secret), QDRANT_API_KEY (secret)

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 agent-memory asks for

  • AGENT_MEMORY_DATA
  • PYTHONPATH

Only Qdrant Memory asks for

  • EMBEDDING_API_KEY (secret)
  • QDRANT_API_KEY (secret)
  • QDRANT_URL

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

What it can do: agent-memory · What it can do: Qdrant Memory · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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