SmartMemory

ai.smartmemoryPublished by smartmemory.aiv1.4.94Updated Oct 24, 2026

Graph + vector memory for agents: recall, ingest, search, distill. Local or remote backend.

The publisher's own server: Memory.fit

VerifiedSTDIODesktop onlyKnowledge & Memory

Overview

AI-generated overview

SmartMemory is a local MCP server that gives an AI assistant graph-and-vector memory for agents, with recall, ingest, search and distill operations.

What you can do
Recall stored memories for the assistant to use as context in a conversation or task. Ingest new information into the memory store. Search memory using graph and vector retrieval. Distill accumulated memories into more compact or refined form. Connect to either a local or a remote backend.
When to use it
Worth adding when you want an assistant to keep and reuse context across sessions, or to search and consolidate a growing body of stored knowledge rather than relying only on the current conversation.
Requirements
Runs as a local process on the user's machine, installed from the PyPI package smartmemory-mcp over stdio. It is desktop-only and not web-executable. A memory backend is needed, either local or remote; the manifest declares no authentication, environment variables or headers.
Before you install
The server writes to and changes a persistent memory store through ingest and distill, so stored content can be altered or consolidated. If a remote backend is used, memory data leaves the local machine for that service; check where the data is stored and who can access it before relying on it for sensitive information.

Installation

In SourceWeft

  1. Open SmartMemory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.4.94LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Memory integrations