Add the SuperLocalMemory MCP server as a connector in Perplexity Desktop. Research context and notes can persist across sessions in a local SQLite store. Note that Perplexity is a networked service — assess each component's privacy and network behavior separately.
The SLM core can keep its memory-content path local in Mode A, but Perplexity is a networked search service. Optional connectors or providers may transmit data. Review each component's privacy settings and terms. Connector availability is controlled by Perplexity and can change with plan or app updates.
Install the SLM package first, then add it as an MCP connector in Perplexity Desktop. Verify tool discovery and a memory round trip before treating the integration as active.
Use pipx or uv. Mode A does not require a model-provider key for its core path. Run setup to initialise the local database and configuration.
pipx install superlocalmemory slm setup
Open Perplexity Desktop, then navigate to Settings → Connectors → Add Connector. Connector support requires an eligible Perplexity plan — confirm availability in your account before proceeding.
In the connector name field, enter:
SuperLocalMemory
In the server command field, enter the MCP stdio command. If you installed with pipx:
slm mcp
If you prefer to run without a global install:
npx superlocalmemory mcp
Click Save, then restart Perplexity Desktop. Confirm that the connector shows as active. Store a note via the memory tools and recall it to verify the full round trip.
Verify tool discovery, remember, recall, update, forget, reconnect, and removal against the installed Perplexity Desktop and SLM releases.
When the connector is active, Perplexity can call SLM memory tools to store and recall research context across sessions. Tool availability depends on the selected MCP profile and installed release.
Store findings, conclusions, and data points from research sessions. Follow-up queries can build on what was previously explored — no re-explaining each session.
Store terminology, abbreviations, and domain-specific language relevant to your current work. Recalled context is bounded — inspect scope and provenance.
Documented MCP clients can connect to the same configured SLM profile. Every published client still needs the full release integration contract.
SLM stores core memory in a local SQLite database. Perplexity and optional integrations retain their own network behavior; assess each component separately.
Recall traces expose candidate sources, fusion state, and score details. Treat retrieved context as bounded evidence, not a verified fact, and verify critical information independently.
SuperLocalMemory is open source under AGPL v3. Full source code is publicly available and auditable. Verify the installed release, optional dependencies, and configured providers.
slm mcp). Verify tool discovery and a full memory round trip after restarting.slm setup, then point the Perplexity connector at slm mcp (pipx install) or npx superlocalmemory mcp. Verify the exact transport and tool list in the installed releases.Install, add the connector in Perplexity Desktop, then verify the memory round trip before relying on it.