FlagQuantum MCP Server vs Turbo Quant Memory
FlagQuantum MCP Server is an MCP server published by FlagQuantum. Marketplaces we read that list it: 1 (Official MCP Registry). 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-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
| Marketplace |  FlagQuantum MCP Server |  Turbo Quant Memory |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.1 Downloads/month (PyPI): 1 051 Downloads/week (PyPI): 104 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.32.0 Downloads/month (PyPI): 845 Downloads/week (PyPI): 61 Forks (GitHub): 1 Stars (GitHub): 9 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 | FlagQuantum MCP Server | Turbo Quant Memory |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 9 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release (differs) | 2026-10-16 (worse) | 2026-10-17 (better) |
| Where it runs (differs) | On your machine (flagquantum-mcp-server) | On your machine (turbo-quant-memory) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | 4, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/flagquantum/mcp-servers | github.com/lexus2016/turbo_quant_memory |
| Changes in the last 7 days (differs) | 1 | 3 |
| First seen | 2026-10-11 | 2026-10-11 |
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
FlagQuantum MCP Server
Build, compile, run and export FlagQuantum circuits locally. No credentials or outbound network.
Turbo Quant Memory
Local-first memory and knowledge graph for coding agents. Compact retrieval, no network.
How to run each
FlagQuantum MCP Server As a local MCP server: PyPI package
claude mcp add --transport stdio flagquantum-mcp-server -- uvx flagquantum-mcp-serverTurbo Quant Memory As a local MCP server: PyPI package
claude mcp add --env "TQMEMORY_SECRETS_PASSPHRASE=<YOUR_TQMEMORY_SECRETS_PASSPHRASE>" --transport stdio turbo-quant-memory -- uvx turbo-quant-memory serveRequires: 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 FlagQuantum MCP Server asks for
FLAGQUANTUM_MCP_MAX_GATESFLAGQUANTUM_MCP_MAX_IR_BYTESFLAGQUANTUM_MCP_MAX_QUBITS
Only Turbo Quant Memory asks for
TQMEMORY_EMBEDDING_BACKENDTQMEMORY_FTS_LANGUAGETQMEMORY_MIGRATE_ON_STARTUPTQMEMORY_SECRETS_PASSPHRASE (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: FlagQuantum MCP Server · What it can do: Turbo Quant Memory · Compare two other plugins
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.