Ext Ops Panel
Open dashboard
Comparison

Needle Remote vs neuralscape

Needle Remote is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). neuralscape is a plugin bundle for AI coding tools published by Ehfaz Rezwan. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. 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 Remoteneuralscape
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Community marketplace ehfazrezwan/neuralscape Not listed Not seen in the last pass
Version: 2.9.2
Forks (GitHub): 1
Stars (GitHub): 6
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 neuralscape
FactNeedle Remoteneuralscape
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub6
Forks (GitHub) (differs)No figure on GitHub1
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.needle.app/mcp)Remote server (ns.siliconinja.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Hooks it runs (differs)Not published7
Parts of the bundle (differs)Not a bundle20
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/ehfazrezwan/neuralscape
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 (4 days ago)not checked yet

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.

neuralscape

In its own words, on Community GitHub marketplaces:

Persistent agentic memory for Claude (Code + Cowork). In Claude Code, hooks auto-capture conversations and recall context on session start; in Cowork (no plugin hooks), the cross-platform skills (recall/remember/save-session/project/ingest) drive memory via the bundled OAuth MCP connector. The ingest skill loads files/folders/pasted context (Markdown/HTML/PDF/MS-Office). Exposes 14 MCP 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)

neuralscape As a Claude Code plugin

Claude Code
/plugin marketplace add ehfazrezwan/neuralscape
/plugin install neuralscape@neuralscape-plugins

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 neuralscape publish no settings it asks for, so we do not compare settings.

What it can do: Needle Remote · What it can do: neuralscape · 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