Vector Memory

io.github.NeerajG03Published by GitHub account NeerajG03v0.4.4Updated Oct 30, 2026

Semantic document memory using Redis vector store. Save and recall files with natural language.

The publisher's own server: Memory.fit

VerifiedSTDIODesktop onlyFiles & StorageKnowledge & Memory

Overview

AI-generated overview

A local MCP server that gives an assistant semantic document memory backed by a Redis vector store, so it can save files and recall them with natural language.

What you can do
  • Save documents and files into a Redis-backed vector memory.
  • Recall stored content by describing it in natural language rather than exact keywords.
  • Semantic search over the saved document set.
  • No tool list is published, so the exact operations are not documented beyond saving and recalling files.
When to use it
Worth adding when you want an assistant to keep a persistent, searchable memory of your own documents and retrieve them by meaning across sessions, and you already run or can run Redis.
Requirements
Runs as a local process on the user's machine, installed from the PyPI package mcp-server-vector-memory over stdio. Desktop client only; not usable from a web client. A reachable Redis instance with vector search support is implied by the description, though no connection settings are declared in the manifest.
Before you install
Saved documents are stored in Redis, so anything you ask the assistant to remember persists outside the chat; avoid storing secrets or sensitive files. No authentication or credentials are declared, so secure the Redis instance yourself. The tool list is not published, so review what it actually exposes before use.

Installation

In SourceWeft

  1. Open Vector Memory 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. v0.4.4LatestSep 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