Lodekeep

com.lodekeepPublished by lodekeep.comOfficial publisherv1.2.0Updated Oct 27, 2026

Memory MCP server for Claude Code. Correct a fact and the old version stops being recalled.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryAI & ML

Overview

AI-generated overview

Lodekeep is a memory MCP server for Claude Code that stores facts and stops recalling a fact once it has been corrected.

What you can do
  • Store and recall persistent facts across sessions for Claude Code.
  • Update a fact so the corrected version replaces the old one in recall.
  • Available as a remote endpoint or as a local npm package over stdio.
  • No tool list is published, so the exact operations are not documented here.
When to use it
Worth adding when you want an assistant to remember facts between sessions and to keep those memories current, rather than repeating outdated information after a correction.
Requirements
OAuth authentication is required. Can be used as a remote endpoint at the provider's site or run locally from the npm package lodekeep over stdio, which needs Node.js. No environment variables or headers are declared.
Before you install
The server keeps a persistent memory of facts, so anything you ask it to remember is retained and later recalled; review what gets stored. Access requires OAuth sign-in to the provider's service, and no tool list is published, so what it can read or change cannot be verified in advance.

Installation

In SourceWeft

  1. Open Lodekeep in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.lodekeep%2Fmemory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "lodekeep": {
      "type": "http",
      "url": "https://lodekeep.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.2.0LatestSep 16, 2026

Score

60% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.