Ext Ops Panel
Open dashboard
Comparison

Needle Remote vs io.github.JubaKitiashvili/context-mem

Needle Remote is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.JubaKitiashvili/context-mem is an MCP server published by JubaKitiashvili. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
MarketplaceNeedle Remoteio.github.JubaKitiashvili/context-mem
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.2.1
Downloads/month (npm): 564
Downloads/week (npm): 154
Forks (GitHub): 6
Stars (GitHub): 19
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

Needle Remote vs io.github.JubaKitiashvili/context-mem
FactNeedle Remoteio.github.JubaKitiashvili/context-mem
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub19
Forks (GitHub) (differs)No figure on GitHub6
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.needle.app/mcp)On your machine (context-mem)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/jubakitiashvili/context-mem
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 301 (2 days ago)no 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

Needle Remote

In its own words, on Docker MCP Catalog:

Production-ready RAG service to search and retrieve data from your documents.

io.github.JubaKitiashvili/context-mem

In its own words, on Official MCP Registry:

Persistent memory for AI agents — 98%+ retrieval recall, 99% token savings, 44 tools

How to run each

Needle Remote As a remote MCP server

Claude Code
claude mcp add --transport http needle https://mcp.needle.app/mcp

Requires: NEEDLE_API_KEY (secret)

io.github.JubaKitiashvili/context-mem As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio context-mem -- npx -y context-mem

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

Only Needle Remote 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

The marketplaces of io.github.JubaKitiashvili/context-mem publish no settings it asks for, so we do not compare settings.

What it can do: Needle Remote · What it can do: io.github.JubaKitiashvili/context-mem · 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