Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

LocalKeep

by zuneracodesversion 0.1.3i★ –iRuns on your computer
Registry nameio.github.zuneracodes/localkeep

Install

Overview

Description from the maker (original English)

Local chronological memory banks you control; Claude recalls them via MCP.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: LOCALKEEP_DATA_DIR, LOCALKEEP_DB_PATH

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "localkeep": {
      "command": "uvx",
      "args": [
        "localkeep"
      ],
      "env": {
        "LOCALKEEP_DATA_DIR": "your-value",
        "LOCALKEEP_DB_PATH": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add localkeep --env LOCALKEEP_DATA_DIR=your-value --env LOCALKEEP_DB_PATH=your-value -- uvx localkeep

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "localkeep": {
      "command": "uvx",
      "args": [
        "localkeep"
      ],
      "env": {
        "LOCALKEEP_DATA_DIR": "your-value",
        "LOCALKEEP_DB_PATH": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "localkeep": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "localkeep"
      ],
      "env": {
        "LOCALKEEP_DATA_DIR": "your-value",
        "LOCALKEEP_DB_PATH": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • LOCALKEEP_DATA_DIR env
    Optional directory for the SQLite DB (default: ~/.localkeep)
  • LOCALKEEP_DB_PATH env
    Optional full path to localkeep.db

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account zuneracodes, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 7221 servers in this category
  • Published to the registry more recently than 30% of the other 7221 servers in this category
  • Basic checks equal to or better than 100% of the other 7221 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is LocalKeep safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated 3 days ago
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 44 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

LocalKeep

LocalKeep is for anyone who wants a chronological memory layer for chatbots where *they* directly control *what* the model remembers about them. Instead of forcing you to rely on a black-box cloud memory that the model invents around you that you can't even edit, LocalKeep lets you curate titled, dated, editable memory banks directly on your own machine where you write the entries and manage them locally via a localhost Hub UI. When a conversation requires your prior context, Claude queries your local data through a secure, native Model Context Protocol (MCP) connector.

Why use LocalKeep

AI Chat apps are great at *sounding* like they remember you, but struggle at recalling the exact thing you care about — *what* happened, on *which* date, about *whom*? Consumer memory features tend to lack the capacity for true temporal reasoning, flattening your history into a soft, generic vibe summary instead of understanding that Event A triggered Event B three months ago, causing its reasoning to fail when you need something specific: a life event, a research arc, a decision you logged months ago. Worse yet, consumer AI memory is a black box: you don't get to decide what the model chooses to remember about you, how it interprets your life, or when it invents context around you.

LocalKeep fixes both structural flaws at once by replacing fragile, model-invented timelines with a rigid, chronological source of your truth, all while giving *you* absolute editorial control. You decide exactly *what* the AI is allowed to know about you. You write the entries, you anchor the dates, and you keep them local on your own machine. Claude simply acts as the lookup engine via MCP when a conversation requires your prior context. LocalKeep bridges the gap between structured personal logging and intelligent AI retrieval, ensuring your context is curated by you—not hallucinated by an LLM.

Who it’s for

  • Anyone frustrated that chat memory can’t reliably fetch dated facts or understand timelines
  • People who already maintain meticulous personal diaries, work logs, or research archives. Instead of settling for a generic chat-app paraphrase, you get to inject your *exact* words and historical data into the prompt as an unyielding source of truth.
  • Users who trust Claude for its reasoning capability, but demand that their foundational context database remains stored locally under their own roof. (Note: Querying memories via MCP still sends the *retrieved text fragments* to Anthropic during the session).

What it is (and isn’t)

  • Is: A lightweight customizable local Hub UI to manage your dated memory banks, paired with an MCP server that Claude Desktop can call.
  • Isn’t: A standalone chat application, a cloud-hosted memory API, or a background utility that silently scrapes your personal conversations.

The Aesthetic Philosophy

The Hub UI intentionally adopts a retro, Windows 95/MS Paint-inspired homage with customizable features to ensure LocalKeep feels like a deeply personal tool rather than an impersonal, rigid dashboard. By putting adjustable interface elements right at your fingertips, the UI signals that you are entering an intimate, offline workshop for your mind—a space you can shape and reconfigure to feel entirely like your own.

Install

pip install localkeep

or: uv tool install localkeep

Then:

localkeep-hub          # http://127.0.0.1:8000

In Claude Desktop, register the MCP server (claude_desktop_config.json):

{

"mcpServers": { "localkeep": { "command": "localkeep-mcp", "args": [] } } }

If the GUI can’t find localkeep-mcp on your PATH, use the absolute path from which localkeep-mcp (the Hub’s Connect panel copies this for you).

Memories default to ~/.localkeep/localkeep.db when installed via pip. Override with LOCALKEEP_DATA_DIR or LOCALKEEP_DB_PATH.

Auto-use LocalKeep (important)

Claude will not reliably call MCP tools unless you also set Personal preferences:

  1. Claude Desktop → Settings → Profile → Personal preferences
  2. Paste the LocalKeep instructions (Hub → Connect → Copy instructions, or see src/localkeep/assets/claude-personal-preferences.txt)
  3. Quit Claude completely and reopen
  4. When LocalKeep asks to run a tool, click Always approve

Develop from source

git clone https://github.com/zuneracodes/localkeep

cd localkeep uv sync --group dev uv run localkeep-hub # http://127.0.0.1:8000

optional live reload:

LOCALKEEP_HUB_RELOAD=1 uv run localkeep-hub

From a source checkout, the DB lives in data/localkeep.db (gitignored).

Tests

These smoke-check the Hub, retrieval, and MCP tools so a fresh install still stores and recalls dated memories the way a real user would.

uv sync --group dev

uv run pytest

Tests start from an empty DB and create memories through Hub form POSTs (same path as a new user).

Privacy

Storage is local. Banks and memories live in your chosen DB path (~/.localkeep/ for pip installs, or data/localkeep.db in a checkout). There is no LocalKeep cloud and nothing is auto-scraped from chat. Theme colors stay in browser localStorage. Refreshing the Hub page or restarting localkeep-hub does not delete your banks — only removing the database file does.

Recall goes through Claude. The Hub and database stay on your machine, but when Claude calls a LocalKeep MCP tool, the matching memories are returned into that chat and Anthropic processes them like any other tool result. LocalKeep isn’t shipping your whole DB upstream — only what that lookup returns for the question at hand.

Contributing

Bug reports and pull requests are welcome via GitHub Issues. Please run uv run pytest before opening a PR.

License

MIT — see LICENSE.

Ask PopNx