Mem Context

io.github.turbyhoPublished by GitHub account turbyhov0.1.4Updated Oct 27, 2026

Temporal memory MCP server with LanceDB vector search, weight-decay scoring, and LLM consolidation

VerifiedSTDIODesktop onlyKnowledge & MemoryAI & ML

Overview

AI-generated overview

Local MCP server that gives an assistant a temporal memory store backed by LanceDB vector search, weight-decay scoring and LLM consolidation.

What you can do
  • Stores and retrieves memories for the assistant using LanceDB vector search.
  • Ranks recalled memories with weight-decay scoring so older or less relevant items fade over time.
  • Consolidates stored memories through an LLM.
  • Runs as a local stdio process on the user's machine.
When to use it
Worth adding when you want an assistant to keep context across sessions and recall earlier information with recency-aware ranking, rather than starting from scratch each time.
Requirements
Runs locally as a stdio process, installed from the PyPI package mem-context, so a Python environment is needed. No authentication, environment variables or headers are declared. An LLM is involved in consolidation, so a model or provider must be available to it.
Before you install
It persists conversation-derived memories locally, so anything the assistant stores may be retained and later recalled. Consolidation sends stored content to an LLM, which may be a third party. No credentials are declared, but review where the memory data and any model calls go before use.

Installation

In SourceWeft

  1. Open Mem Context 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. v0.1.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.