MCP.so
Sign In

Lorekeeper MCP Server

@Jessinra

Basic information

Category

Other

License

Apache-2.0

Transports

stdio

Author

Jessinra

Submitted by

Jessin Ra

About Lorekeeper MCP Server

Self-improving memory for AI agents

Lorekeeper MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "lorekeeper": {
      "command": "lorekeeper"
    }
  }
}

Lorekeeper MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Lorekeeper?

Lorekeeper is a self-improving memory server for AI agents. It stores memories locally in SQLite on your own disk, connects to any MCP-compatible agent, and improves with every session. It is designed for solo developers and agent workflows that need zero ops, zero cloud, and a persistent memory store.

How to use Lorekeeper?

Install with pip install lorekeeper-mcp, then run lorekeeper setup to configure your agents, and start the server with lorekeeper. Use lorekeeper-dashboard to open a web UI for managing memories. Agents can then call tools like lore_remember and lore_search to store and retrieve memories.

Key features of Lorekeeper

  • Hybrid semantic + keyword search with time-decay and usage scores
  • Self-improving quality loop: feedback adjusts memory scores
  • Auto-linking: new memories linked to closest semantic neighbors
  • Duplicate detection: blocks near-identical content
  • Full web dashboard with seven tabs for management
  • Universal MCP support: works with many agents
  • Local-first: data stays on your machine, no cloud
  • Namespaces: multiple agents share one store isolated
  • Reflection: agents auto-extract learnings from sessions

Use cases of Lorekeeper

  • Staying in context across sessions: agents remember preferences and code patterns
  • One memory pool, multiple agents: Claude Code, Cursor, Hermes share knowledge
  • Cross-session debugging: recall root causes and fixes from weeks ago
  • Project onboarding: new agents start with architecture context from past sessions

Frequently asked questions

1

What makes Lorekeeper different from file-based memory or cloud services?

Lorekeeper is a local MCP server that uses hybrid search, self-improving memory scores, and auto-linking. It is a single `pip install` with no cloud dependency, no API keys, and no configuration. File-based tools require manual maintenance, and cloud services charge per API call and send data off your machine.

2

How do I install and set up Lorekeeper?

Run `pip install lorekeeper-mcp`, then `lorekeeper setup` to auto-detect and configure supported agents. Finally, start the server with `lorekeeper`. No additional configuration is needed.

3

Where is my data stored?

All memories are stored locally in SQLite and LanceDB. Your data never leaves your machine. There is no cloud storage or remote server.

4

Does Lorekeeper require an API key or internet connection?

No. Lorekeeper requires no API keys, no sign-up, and no internet connection after installation. It is free to run forever.

5

Which agents are supported?

Lorekeeper works with any MCP-compatible agent, including Claude Code, Cursor, Hermes, Copilot, OpenCode, and Codex CLI.

Comments

More Other MCP servers