Banyan Memory

io.github.labacaciaPublished by GitHub account labacaciav1.5.1Updated Oct 24, 2026

Persistent, governed local memory for MCP-compatible AI clients.

The publisher's own server: Memory.fit

VerifiedSTDIODesktop onlyKnowledge & Memory

Overview

AI-generated overview

Banyan Memory is a local MCP server that gives MCP-compatible AI clients persistent, governed memory stored on the user's own machine.

What you can do
Provides persistent memory that AI clients can keep across sessions, rather than losing context when a conversation ends. The memory is described as governed, implying rules or controls over what is stored and used. It runs locally as a desktop-only process, so memory data stays on the user's machine. No individual tools are listed, so specific operations are not documented here.
When to use it
Worth considering when you want an AI client to remember information between sessions and you prefer that memory to live locally on your own desktop rather than in a hosted service.
Requirements
Runs as a local process on the user's machine, installed from a NuGet package or a Windows x64 MCP bundle. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Before you install
The server stores persistent memory locally, so consider what personal or sensitive information may be retained and how it can be reviewed or cleared. No tools, instructions or README are provided, so its exact behavior and data handling cannot be verified from this listing.

Installation

In SourceWeft

  1. Open Banyan 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

1
  1. v1.5.1LatestSep 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