Tdai Memory Mcp

io.github.tinhien11Published by GitHub account tinhien11v0.3.0Updated Oct 24, 2026

Local-first MCP memory server for coding agents. No API key, no cloud. SQLite + FTS5 + sqlite-vec.

The publisher's own server: Memory.fit

VerifiedSTDIODesktop onlyKnowledge & Memory

Overview

AI-generated overview

A local-first memory server for coding agents, storing memories in a local SQLite database with full-text and vector search; the package has been renamed to rem

What you can do
Provides persistent memory for coding agents, backed by a local SQLite file with FTS5 full-text search and sqlite-vec vector search, so an assistant can store and recall context across sessions. The package has been renamed from tdai-memory-mcp to remem-mcp; the new package keeps the same tools, the same database file and the same hooks, and existing memory.db data is preserved at the same path. Environment variables are renamed from the TDAI_ prefix to REMEM_.
When to use it
Use it when you want a coding agent to remember project context between sessions without sending data to a cloud service or supplying an API key. Prefer the renamed remem-mcp package for new installs; existing tdai-memory-mcp users should migrate.
Requirements
Runs as a local process over stdio, installed from npm (tdai-memory-mcp, now remem-mcp), so Node.js is needed. No API key, no cloud account and no declared environment variables. It writes a local SQLite database at ~/.local/share/remem-mcp/memory.db. Desktop only.
Before you install
The package is renamed and the old name is superseded; install remem-mcp and run its setup command instead. Environment variables change from the TDAI_ prefix to REMEM_, so existing configuration must be updated. Memories are stored in a local database file on the machine.

Installation

In SourceWeft

  1. Open Tdai Memory Mcp 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

tdai-memory-mcp → remem-mcp

This package has been renamed to remem-mcp.

Migrate

bash
npx remem-mcp setup

Your existing memory.db is preserved — same SQLite file, same path (~/.local/share/remem-mcp/memory.db).

What changed

  • Package name: tdai-memory-mcp → remem-mcp
  • Env vars: TDAI_* → REMEM_*
  • Everything else stays the same: same tools, same DB, same hooks

Links

Source: README.md at commit 435dcb6

Tools

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

Version history

1
  1. v0.3.0LatestSep 16, 2026

Score

40% 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
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Memory integrations