Comparison

qector vs Turbo Quant Memory

qector is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.

qector is a plugin bundle for AI coding tools published by Guillaume Lessard. No marketplace we read lists it any more. Turbo Quant Memory is an MCP server published by Lexus2016. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplace	qector	Turbo Quant Memory
Community marketplace guillaumelessard/qector-claude-plugin	Removed on 2026-10-15 Version: 1.0.6 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen 2026-10-13	Not listed
Official MCP Registry	Not listed	Listed Version: 0.32.0 Downloads/month (PyPI): 845 Downloads/week (PyPI): 61 Forks (GitHub): 1 Stars (GitHub): 9 Not marked · First seen 2026-10-11

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

qector vs Turbo Quant Memory
Fact	qectorno longer listed · 2026-10-15	Turbo Quant Memory
Marketplaces that list it (differs)	0	1
Stars (GitHub) (differs)	1	9
Forks (GitHub) (differs)	0	1
Last release (differs)	Not published	2026-10-17
Where it runs (differs)	Installs as a plugin bundle	On your machine (turbo-quant-memory)
Transport (differs)	Not stated	stdio
Tools it declares	Not published	Not published
Environment variables it asks for (differs)	2, secrets among them: 0	4, secrets among them: 1
Hooks it runs (differs)	2	Not published
Parts of the bundle (differs)	47	Not a bundle
Licence (differs)	Proprietary	Not stated
Repository (differs)	github.com/guillaumelessard/qector-claude-plugin	github.com/lexus2016/turbo_quant_memory
Changes in the last 7 days (differs)	4	3
First seen (differs)	2026-10-13	2026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of qector

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

Qiskit Documentation MCP Server

MCP server for querying and retrieving Qiskit documentation, guides, and API references

by Qiskit · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
Quantum OpenQASM MCP

IBM Quantum OpenQASM 2.0 MCP — list backends, submit QASM, poll jobs, get histograms.

by markusvankempen · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
Quantum Suitability Validator

AI triage for quantum computing POC proposals. Screens before budget is allocated.

by OjasKord · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
Qiskit IBM Transpiler MCP Server

MCP server for AI Transpiler IBM Quantum services

by Qiskit · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
NVIDIA Skills

Find the right NVIDIA skill for GPU acceleration, CUDA, AI agents, data loading, training, inference, robotics, Physical AI, Omniverse, simulation, and other NVIDIA-powered…

by NVIDIA · Plugin bundle

Listed on: Claude Code: claude-plugins-official, Claude Code: claude-plugins-community, Community GitHub marketplaces · Describes nearly the same job
FlagQuantum MCP Server

Build, compile, run and export FlagQuantum circuits locally. No credentials or outbound network.

by FlagQuantum · MCP server

Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

qector

In its own words, on Community GitHub marketplaces:

Local QECTOR quantum error correction plugin for Claude Code and Claude Desktop with strict math skills, focused agents, and qector-decoder-v3 MCP servers.

Turbo Quant Memory

In its own words, on Official MCP Registry:

Local-first memory and knowledge graph for coding agents. Compact retrieval, no network.

How to run each

qector

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Turbo Quant Memory As a local MCP server: PyPI package

Claude Code

claude mcp add --env "TQMEMORY_SECRETS_PASSPHRASE=<YOUR_TQMEMORY_SECRETS_PASSPHRASE>" --transport stdio turbo-quant-memory -- uvx turbo-quant-memory serve

Requires: TQMEMORY_SECRETS_PASSPHRASE (secret)

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 qector asks for

PYTHONUNBUFFERED
QECTOR_SILENT

Only Turbo Quant Memory asks for

TQMEMORY_EMBEDDING_BACKEND
TQMEMORY_FTS_LANGUAGE
TQMEMORY_MIGRATE_ON_STARTUP
TQMEMORY_SECRETS_PASSPHRASE (secret)

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

What it can do: qector · What it can do: Turbo Quant Memory · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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 2026-10-18. We publish no contact details for plugin publishers.