LinkLore MCP server
✓ VerifiedLets AI agents record decisions, pitfalls, and specifications in a structured local memory that links directly to code context.
Also known as linklore/linklore-mcp, linklore-mcp, llre
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- 161
- Latest version
- 0.2.2
- Last commit
- Aug 6, 2026
- License
- —
What is LinkLore MCP?
LinkLore lets AI agents record decisions, pitfalls, and specifications in a structured local memory that links directly to code context.
Summary generated from the project's README
About LinkLore MCP server
Recording technical decisions and project specifications directly within your development workflow is what LinkLore enables for AI agents. Instead of relying on markdown files that drift from the actual implementation, this server provides a structured SQLite memory stored locally in a .linklore directory. It allows agents to maintain a persistent journal of pitfalls and plans that stay connected to the relevant source code files.
Developers use this tool by adding it to MCP clients like Claude Code, Cursor, or Windsurf using the uvx llre command. The system is designed specifically for machine usability, offering tools like brief() to provide a session-start dashboard of recent activity and hotspots. It includes specialized functions such as status() to detect when code changes have made existing documentation stale through git-diff analysis. While it operates locally by default, users can opt into Google login for personal backups or team sharing via openbox features.
What you can do with it
- 1Initialize project memoryAn agent can set up the entire local storage structure and register itself as an MCP server in a single step.
- 2Prevent recurring mistakesAn agent can record a specific technical pitfall so it does not repeat the same error in future sessions.
Written from the project's README. Every use case is checked against a quote from it.
How to install LinkLore MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall LinkLore MCP in Claude Code
$ claude mcp add linklore-mcp -- uvx llreInstall LinkLore MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"linklore-mcp": {
"command": "uvx",
"args": [
"llre"
]
}
}
}Install LinkLore MCP in VS Code
.vscode/mcp.json
{
"servers": {
"linklore-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"llre"
]
}
}
}Install LinkLore MCP in VS Code CLI
$ code --add-mcp '{"name":"linklore-mcp","type":"stdio","command":"uvx","args":["llre"]}'Install LinkLore MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"linklore-mcp": {
"command": "uvx",
"args": [
"llre"
]
}
}
}Install LinkLore MCP in Codex
$ codex mcp add linklore-mcp -- uvx llreInstall LinkLore MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.linklore-mcp] command = "uvx" args = ["llre"]
Install LinkLore MCP in Gemini CLI
$ gemini mcp add -s user linklore-mcp uvx -- llreInstall LinkLore MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"linklore-mcp": {
"command": "uvx",
"args": [
"llre"
]
}
}
}Configuration
LINKLORE_LANGUI/message language for LinkLore tool output. Supported: en, ko. Leave unset to auto-detect from the OS locale (falls back to en).
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachablelinklore/linklore-mcp is public and reachablegithub.com/linklore/linklore-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-08-06github.com/linklore/linklore-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from llrePass
- No critical advisory in the package or its dependencies32 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubLinkLore
MCP server for project memory — lets AI agents record decisions, pitfalls, and specs as they work, and recall them next session with code context attached.
Built for agents, not humans: every tool here is designed for usability by an AI, not readability for a person.
Why LinkLore
Every new session, an AI agent starts from zero — decisions get re-litigated, pitfalls get rediscovered, and "why is it done this way?" gets answered by guessing. Markdown notes don't fix this: they're written for people, they drift from the code, and no agent reads them reliably.
LinkLore is structured memory that the agent itself reads and writes through MCP tools:
- Two record types — lore (decisions, pitfalls, journal) and doc (specs, plans), bidirectionally linked to each other and to code files.
- Local-first — everything lives in a
.linklore/SQLite store inside your project. No account needed to start. - Code context — records link to source files; git-diff-based stale detection flags memory that the code has outrun.
- Cheap recall — query by meaning, tag, file, status, or period; a session-start
brief()returns open items and hotspots in a few hundred tokens.
Quick Start
Runs straight from PyPI — no install or clone (uvx llre).
Claude Code
claude mcp add llre -- uvx llre
Any other MCP client (Cursor, Codex, Windsurf, …) — add to the project's MCP config (e.g. .mcp.json):
{
"mcpServers": {
"llre": {
"command": "uvx",
"args": ["llre"]
}
}
}
Then initialize, once, in the project root:
uvx llre init
Or let your agent do all of it — this is a server meant to be set up by an AI agent rather than typed in by hand. Paste this as your first message to Claude Code, Cursor, Codex, or any other MCP-capable agent:
Set up LinkLore (an MCP server for project memory) in this repo. It's the PyPI package
llre, run viauvx llre— no install or clone needed. Register it as an MCP server for whichever client you are (Claude Code:claude mcp add llre -- uvx llre; otherwise add{"mcpServers": {"llre": {"command": "uvx", "args": ["llre"]}}}to this project's.mcp.json), then runuvx llre inithere. Ask me first before runninguvx llre login— it opens a browser for Google login and is only needed for personal backup or team sharing.
The Loop
How an agent actually uses it, in order:
start a session → brief() open items, recent activity, hotspots
about to touch code → show(file=..., query=…) decisions & pitfalls tied to that area
decided / got burned → add(type='lore', …) record it, linked to the files involved
spec or plan → add(type='doc', …) instead of a standalone .md
something changed → edit(id=..., …) append, replace a section, or supersede
memory getting messy → doctor() · cleanup() integrity check, duplicate detection
back up / share → push() · openbox(…) your server space · invite-only shared boxes
Available Tools
23 tools. Call any of them with help=True for full usage.
| Category | Tool | What it does |
|---|---|---|
| Setup | init |
Set up .linklore/ in the current directory |
| Project | brief |
Session-start dashboard — open items, recent activity, hotspots |
| Project | status |
Code↔doc sync drift detection (git-diff based) |
| Project | config |
Project settings, external sources, session pin |
| Diagnostics | doctor |
Data integrity check; action='fix' auto-repairs |
| Record | add |
Create lore or doc; items=[{...}] batch-creates |
| Record | edit |
Modify an item — append (default), replace a section, overwrite, or supersede |
| Record | rm |
Delete — recoverable trash by default, force=True for permanent |
| Record | restore |
Recover from trash; without id lists the trash |
| Record | local |
Move/copy/view items across sibling local workspaces |
| Search | show |
Query by id, text, tag, status, file, or period; graph and tag views |
| Search | log |
Change history |
| Link | link |
Connect two items (lore↔lore, doc↔doc, doc↔lore) |
| Link | unlink |
Disconnect two items |
| Doc view | doc_flow |
Render a doc's flow chain in order |
| Doc view | doc_map |
Overview of the full doc link network |
| Doc view | doc_rollup |
Collect lore linked to a doc into an AI-summary draft |
| Cleanup | cleanup |
Detect near-duplicate lore/doc candidates |
| My server | push |
Back up the local store to your own server space |
| My server | pull |
Restore from your own server space |
| Openbox | openbox |
All cross-owner sharing behind one gate — push/pull, browse, invite/join, roles |
| Feedback | report |
Send feedback or a bug report straight to the team |
The full guide ships inside the product, as lore — LinkLore documents itself with itself. After init(), your project carries it as a read-only source:
show(tag='guide')
It updates with the package: upgrade llre and brief() tells you what changed.
Repository Layout
mcp/— the readable portion of the MCP server source (PyPI:llre)plugin/— Claude Code plugin wrapper
Source Model
Mostly readable, core compiled. This repository publishes the MCP server's source in the clear — the entry point, i18n catalogs, base utilities, and the onboarding guide — under the Elastic License 2.0. The core modules (search, ranking, contradiction detection, the tool logic) ship as compiled extensions in the published wheel rather than plaintext source, so "read every line and fork it" isn't 100% true — but the majority is readable, and you can run it, self-host it, and use it commercially inside your own org. We'd rather be upfront that the crown-jewel logic is compiled than pretend it's fully open.
This tree is not buildable on its own (the compiled modules are not here) — install the published package instead: uvx llre.
Research
LinkLore is the case study of the paper "When the Agent Is the User: Agent-Driven Evolution of AI-Native Tools" — defining the AI-Native Tools category, where the AI agent is the primary operator.
DOI: 10.5281/zenodo.21216858 · citation: CITATION.cff
License
Elastic License 2.0. Free to install and use; you may not provide the software as a competing managed service, circumvent license-key functionality, or remove licensing notices.
Team sync, cross-project sharing, and cloud backup are provided by the backend service at linklore.io (not part of this repository).
LinkLore MCP questions
How do I add LinkLore MCP to Claude Code?
Run claude mcp add linklore-mcp -- uvx llre in your terminal. Add --scope user to make it available in every project.
How do I add LinkLore MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Where is the memory data stored?
Everything is stored locally in a .linklore/ SQLite database within your project directory.
Can the memory stay in sync with my code?
Yes, it uses git-diff-based detection to flag when the code has changed in a way that makes the recorded memory stale.