Needle Remote vs io.github.volsier/memforge-memory
Needle Remote is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.volsier/memforge-memory is an MCP server published by volsier. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 No figure published 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
| Fact | Needle Remote | io.github.volsier/memforge-memory |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.needle.app/mcp) | On your machine (@memforgeai/memory-service) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 4, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository | Not stated | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | 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
Production-ready RAG service to search and retrieve data from your documents.
io.github.volsier/memforge-memory
Team engineering memory for AI coding assistants. 47 MCP tools, pgvector semantic search.
How to run each
Needle Remote
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: NEEDLE_API_KEY (secret)
io.github.volsier/memforge-memory As a local MCP server: npm package
claude mcp add --env "DATABASE_URL=<YOUR_DATABASE_URL>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --env "OPENAI_BASE_URL=<YOUR_OPENAI_BASE_URL>" --env "OPENAI_EMBEDDING_MODEL=<YOUR_OPENAI_EMBEDDING_MODEL>" --transport stdio memforge-memory -- npx -y @memforgeai/memory-serviceRequires: DATABASE_URL, OPENAI_API_KEY (secret), OPENAI_BASE_URL, OPENAI_EMBEDDING_MODEL
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 Needle Remote asks for
NEEDLE_API_KEY (secret)
Only io.github.volsier/memforge-memory asks for
DATABASE_URLOPENAI_API_KEY (secret)OPENAI_BASE_URLOPENAI_EMBEDDING_MODEL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Needle Remote · What it can do: io.github.volsier/memforge-memory · 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.