Tdai Memory MCP

This package has been renamed to remem-mcp. Package name: tdai-memory-mcp → remem-mcp Env vars: TDAI_ → REMEM_ Everything else stays the same: same tools, same DB, same hooks. It runs locally over stdio via the published package.

People connecting memory tools to Claude, Cursor, VS Code, or another MCP client. The project is written in JavaScript.

NO LONGER MAINTAINED

LAST COMMIT 2026-08-15 · ★ 4 · VERIFIED 2026-08-25

JavaScript servers · how we verify → /methodology

01 · Install Tdai Memory MCP

Claude Code

claude mcp add tinhien11-tdai-memory-mcp -- npx -y tdai-memory-mcp

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "tinhien11-tdai-memory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tdai-memory-mcp"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

repository archived on GitHub - read-only; no future fixes, security or otherwise

repo age created 2026-08-10 - young repo, little track record yet

license no standard license detected - usage rights unclear; check the repo before commercial use

npm package tdai-memory-mcp - unscoped; check the name against the project README before installing

registry namespace io.github.tinhien11 is GitHub-verified and matches the repo owner

03 · What Tdai Memory MCP can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

v0.5.17 · 2026-08-11

npm · npx [email protected] · Docker · docker pull ghcr.io/tinhien11/tdai-memory-mcp:0.5.17

v0.5.16 · 2026-08-11

npm · npx [email protected] · Docker · docker pull ghcr.io/tinhien11/tdai-memory-mcp:0.5.16

v0.5.15 · 2026-08-11

npm · npx [email protected] · Docker · docker pull ghcr.io/tinhien11/tdai-memory-mcp:0.5.15

04 · Who maintains Tdai Memory MCP

tdai-memory-mcp is maintained by tinhien11. We track 2 MCP servers from tinhien11 - 1 actively maintained, 7 combined GitHub stars, oldest repo from Aug 2026. Full record: all servers from tinhien11.

remem-mcp - Local-first MCP Memory + CodeGraph + Wiki Local-first memory for AI coding agents. Memory + CodeGraph + Wiki in one SQLite file. ★ 3

05 · Facts

repository: github.com/tinhien11/tdai-memory-mcp
category: memory - dead as of 2026-08-25.
release cadence: 10+ releases in the last 90 days (latest 2026-08-11)
registry: io.github.tinhien11/tdai-memory-mcp (active, first published 2026-08-10 · 4 versions)
packages: npm:tdai-memory-mcp

06 · Tdai Memory MCP FAQ

What is Tdai Memory MCP?

Is Tdai Memory MCP still maintained?

Its last commit was 2026-08-15 (as of 2026-08-25) - we classify it as dead.

How do I install Tdai Memory MCP?

Run `npx -y tdai-memory-mcp`. You can also paste the ready-made client config above.

Does Tdai Memory MCP run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Tdai Memory MCP

Alternatives to Tdai Memory MCP

Maintained memory servers if Tdai Memory MCP isn't the fit.

Pairs well with

Servers that cover what Tdai Memory MCP doesn't - only shown when the pairing reason fits the companion.