Ext Ops Panel
Open dashboard
Comparison

Needle Remote vs mcp-memory-service

Needle Remote is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). mcp-memory-service is a plugin bundle for AI coding tools published by doobidoo. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. 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 Remotemcp-memory-service
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Community marketplace doobidoo/mcp-memory-service Not listed Listed
Version: 1.1.0
Forks (GitHub): 360
Stars (GitHub): 2 030
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 mcp-memory-service
FactNeedle Remotemcp-memory-service
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub2 030
Forks (GitHub) (differs)No figure on GitHub360
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.needle.app/mcp)Installs as a plugin bundle
Transport (differs)Streamable HTTPNot stated
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 0
Hooks it runs (differs)Not published5
Parts of the bundle (differs)Not a bundle6
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/doobidoo/mcp-memory-service
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-16
Endpoint at the last check (differs)Answered with HTTP 301 (5 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.

mcp-memory-service

In its own words, on Community GitHub marketplaces:

Semantic memory for Claude Code sessions

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)

mcp-memory-service As a Claude Code plugin

Claude Code
/plugin marketplace add doobidoo/mcp-memory-service
/plugin install mcp-memory-service@mcp-memory-service

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

Only Needle Remote asks for

  • NEEDLE_API_KEY (secret)

Only mcp-memory-service asks for

  • MCP_HYBRID_SYNC_OWNER
  • MCP_MEMORY_STORAGE_BACKEND

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

What it can do: Needle Remote · What it can do: mcp-memory-service · Compare two other plugins

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