Ext Ops Panel
Open dashboard
Comparison

io.github.contextq/contextq-mcp vs io.github.zamansheikh/memory-lean

io.github.contextq/contextq-mcp is an MCP server published by contextq. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.zamansheikh/memory-lean is an MCP server published by zamansheikh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
Marketplaceio.github.contextq/contextq-mcpio.github.zamansheikh/memory-lean
Official MCP Registry Listed
Version: 2.1.1
Downloads/month (npm): 678
Downloads/week (npm): 199
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.5.0
Downloads/month (npm): 505
Downloads/week (npm): 505
Forks (GitHub): 0
Stars (GitHub): 3
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

io.github.contextq/contextq-mcp vs io.github.zamansheikh/memory-lean
Factio.github.contextq/contextq-mcpio.github.zamansheikh/memory-lean
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub)00
Last release (differs)Not published2026-10-16
Where it runs (differs)Remote server (app.contextq.dev/mcp)On your machine (memory-lean)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 0
Licence (differs)Not statedMIT
Repository (differs)github.com/contextq/contextq-mcpgithub.com/zamansheikh/memory-lean
Changes in the last 7 days (differs)05
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 23 h ago, requires a keyno remote endpoint we check

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

io.github.contextq/contextq-mcp

In its own words, on Official MCP Registry:

Persistent memory, hybrid search and a goal graph for AI agents, over stdio or remote HTTP.

io.github.zamansheikh/memory-lean

In its own words, on Official MCP Registry:

Token-lean memory for AI agents: a knowledge graph searched cheaply. Drop-in for server-memory.

How to run each

io.github.contextq/contextq-mcp As a remote MCP server

Claude Code
claude mcp add --transport http contextq-mcp https://app.contextq.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: CONTEXT_API_KEY (secret), CONTEXT_API_URL, Authorization header

io.github.zamansheikh/memory-lean As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio memory-lean -- npx -y memory-lean

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

Only io.github.contextq/contextq-mcp has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

Only io.github.contextq/contextq-mcp asks for

  • CONTEXT_API_KEY (secret)
  • CONTEXT_API_URL

Only io.github.zamansheikh/memory-lean asks for

  • MEMORY_FILE_PATH

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

What it can do: io.github.contextq/contextq-mcp · What it can do: io.github.zamansheikh/memory-lean · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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