Developer · Local MCP server
Lore Context
Governed AI-agent memory, Evidence Ledger traces, evals, and portable context tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Lore-Context/lore-context-mcp- Version
- 0.6.0-alpha.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm, OCI image (Docker)
- Published
- 2026-04-29
- Updated
- 2026-04-29
- Publisher
- Lore-Context (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Lore-Context) · how
- Website
- lorecontext.com
- Repository
- github.com/Lore-Context/lore-context
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @lore-context/server | 0.6.0-alpha.1 | stdio |
| OCI image (Docker) | ghcr.io/lore-context/lore-context-mcp:0.6.0-alpha.1 | - | stdio |
How to connect Lore Context
Lore Context runs locally from a Node.js package published to the npm registry: @lore-context/server version 0.6.0-alpha.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @lore-context/server@0.6.0-alpha.1. It reads these environment variables: LORE_API_URL (required), LORE_API_KEY (secret) and LORE_MCP_TRANSPORT; set them in the client's configuration for this server.
Lore Context runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/lore-context/lore-context-mcp:0.6.0-alpha.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e LORE_API_URL -e LORE_API_KEY -e LORE_MCP_TRANSPORT ghcr.io/lore-context/lore-context-mcp:0.6.0-alpha.1. It reads these environment variables: LORE_API_URL (required), LORE_API_KEY (secret) and LORE_MCP_TRANSPORT; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"lore-context-mcp": {
"command": "npx",
"args": [
"-y",
"@lore-context/server@0.6.0-alpha.1"
],
"env": {
"LORE_API_URL": "<value>",
"LORE_API_KEY": "<secret>",
"LORE_MCP_TRANSPORT": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| LoomalySEO audit of every page: what to fix first, a fix prompt for your framework, and a re-check. | Remote · HTTPLive check: sign-in required |
| LoopbackFeedback bus for coding agents: pin feedback on the app you're building; a fix turns the pin green. | Local · stdio |
| LoreCross-agent memory over MCP: hybrid recall, knowledge graph, private/shared visibility, redaction. | Local · stdio |
| LoreLightweight MCP for infinite agent memory. Any agent, any session, anytime. | Local · stdio |
| LoreConvoLocal-first persistent session memory for Claude Code and other agents. SQLite + FTS5, no cloud. | Local · stdio |
| LoreweaveDurable agent memory over a markdown vault: bitemporal facts, timelines, hybrid graph search. | Local · stdio |
| Lossless Context MCPAgent context flight recorder: restore after compaction, fan-out packs, signed git-bound receipts. | Local · stdio |
| LovecPrompt-injection detector for untrusted text before it reaches an LLM (RU/EN). BYO lovec.tech key. | Local · stdio |