Lore Context

Name: Lore Context
Author: Lore-Context

作者：Lore-Context版本 0.6.0-alpha.1i★ –i在你的电脑上运行

注册名称io.github.Lore-Context/lore-context-mcp

安装

概览

作者提供的说明（英文原文）

Governed AI-agent memory, Evidence Ledger traces, evals, and portable context tools.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 会计、财务与税务
你需要填写：LORE_API_URL, LORE_API_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： LORE_API_URL, LORE_API_KEY, LORE_MCP_TRANSPORT

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "lore-context": {
      "command": "npx",
      "args": [
        "-y",
        "@lore-context/server"
      ],
      "env": {
        "LORE_API_URL": "your-value",
        "LORE_API_KEY": "your-value",
        "LORE_MCP_TRANSPORT": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add lore-context --env LORE_API_URL=your-value --env LORE_API_KEY=your-value --env LORE_MCP_TRANSPORT=your-value -- npx -y @lore-context/server

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "lore-context": {
      "command": "npx",
      "args": [
        "-y",
        "@lore-context/server"
      ],
      "env": {
        "LORE_API_URL": "your-value",
        "LORE_API_KEY": "your-value",
        "LORE_MCP_TRANSPORT": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "lore-context": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@lore-context/server"
      ],
      "env": {
        "LORE_API_URL": "your-value",
        "LORE_API_KEY": "your-value",
        "LORE_MCP_TRANSPORT": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

LORE_API_URL 必填 env
Base URL of the Lore API that the MCP server should proxy tool calls to.
LORE_API_KEY 机密 env
Optional Lore API key when the API is configured to require authentication.
LORE_MCP_TRANSPORT env
MCP stdio transport implementation. Use sdk unless debugging legacy JSON-RPC mode.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 Lore-Context 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“会计、财务与税务”中的其他服务器比较i

星标数多于此分类中其他 1720 个服务器的 0%
发布到注册中心的时间比此分类中其他 1720 个服务器的 7% 更新
基础检查结果等于或优于此分类中其他 1720 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Lore Context 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：LORE_API_URL, LORE_API_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.6.0-alpha.1）于6个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Docker。

有什么可以替代它？

同一分类中有：Finance Toolkit, SolidInvoice, Korea Tax Calculator

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Finance Toolkit

作者：JerBouma

500+ transparent financial methods calculated from raw statements, not third-party endpoints.

电脑或云端★ 5,496MIT昨天更新

安装

SolidInvoice

作者：SolidInvoice

Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.

在云端运行★ 981MIT7天前更新

安装

Korea Tax Calculator

作者：UpstageAI

Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.

在你的电脑上运行★ 97MIT今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Lore Context

The control plane for AI-agent memory, eval, and governance.

Know what every agent remembered, used, and should forget — before memory becomes production risk.

Getting Started · Website Quickstart · Benchmark Methodology · API Reference · Architecture · Project Plan · Release Status · Roadmap · Integrations · Deployment · Changelog

🌐 Read this in your language: English · 简体中文 · 繁體中文 · 日本語 · 한국어 · Tiếng Việt · Español · Português · Русский · Türkçe · Deutsch · Français · Italiano · Ελληνικά · Polski · Українська · Bahasa Indonesia

Localized docs may lag the current English release notes; the canonical v2.1 docs are the English README and docs/ set.

What is Lore Context

Lore Context is an open-core control plane for AI-agent memory: it composes context across memory, search, repository graphs, and tool traces; evaluates retrieval quality on your own datasets; routes governance review for sensitive content; and exports memory as a portable interchange format you can move between backends.

It does not try to be another memory database. The unique value is what sits on top of memory:

Context Query — single endpoint composes memory + web + repo + tool traces, returns a graded context block with provenance.
Memory Eval — runs Recall@K, Precision@K, MRR, stale-hit-rate, p95 latency on datasets you own; persists runs and diffs them for regression detection.
Governance Review — six-state lifecycle (candidate / active / flagged / redacted / superseded / deleted), risk-tag scanning, poisoning heuristics, immutable audit log.
MIF-like Portability — JSON + Markdown export/import preserving provenance / validity / confidence / source_refs / supersedes / contradicts. Works as a migration format between memory backends.
Repo Graph — deterministic repository indexing (files, symbols, imports, calls, routes, tests) exposed as API routes and read-only MCP tools so agents ground repository answers in a stable project-context contract.
Multi-Agent Adapter — first-class agentmemory integration with version probe + degraded-mode fallback; clean adapter contract for additional runtimes.

When to use it

Use Lore Context when...	Use a memory database (agentmemory, Mem0, Supermemory) when...
You need to prove what your agent remembered, why, and whether it was used	You just need raw memory storage
You run multiple agents (Claude Code, Cursor, Qwen, Hermes, Dify) and want shared trustable context	You're building a single agent and OK with a vendor-locked memory tier
You require local or private deployment for compliance	You prefer a hosted SaaS
You need eval on your own datasets, not vendor benchmarks	Vendor benchmarks are sufficient signal
You want to migrate memory between systems	You don't plan to ever switch backends

Quick Start

# 1. Clone + install

git clone https://github.com/Lore-Context/lore-context.git cd lore-context && pnpm install

2. Run the quickstart helper and inspect the activation report

pnpm quickstart -- --dry-run --activation-report

3. Generate a real API key (do not use placeholders in any environment beyond local-only dev)

export LORE_API_KEY=$(openssl rand -hex 32)

4. Start the API (file-backed, no Postgres required)

pnpm build && PORT=3000 LORE_STORE_PATH=./data/lore-store.json pnpm start:api

5. Write a memory

curl -H "Authorization: Bearer $LORE_API_KEY" -H "Content-Type: application/json" \ -X POST http://127.0.0.1:3000/v1/memory/write \ -d '{"content":"Use RDS as truth store and Qdrant as the derived recall index for Lore Context production.","memory_type":"project_rule","project_id":"demo"}'

6. Query context, then inspect the returned traceId in the Evidence Ledger

curl -H "Authorization: Bearer $LORE_API_KEY" -H "Content-Type: application/json" \ -X POST http://127.0.0.1:3000/v1/context/query \ -d '{"query":"production storage","project_id":"demo","token_budget":1200}'

For the public website quickstart, see lorecontext.com/quickstart. For full setup (Postgres, Docker Compose, Dashboard, MCP integration), see docs/getting-started.md.

The canonical alpha quickstart is git clone + pnpm quickstart. Lore does not currently publish or claim a public @lore-context/quickstart npm package. The MCP stdio server is published separately as @lore-context/server for registry and client distribution, and the SDK middleware ships as @lore-context/sdk-middleware (npm) and lore-context-middleware (PyPI).

For AI-readable discovery, the website publishes /llms.txt and /llms-full.txt from public documentation only. The Official MCP Registry entry is published, and additional distribution drafts live under docs/distribution. Launch drafts live under docs/launch, and design partner intake under docs/design-partners. The public benchmark page is a reproducible methodology and small smoke-run report, not a competitive benchmark-win claim.

Architecture

The diagram below shows the full open-core plus hosted-production shape. In the public OSS repo, local file/Postgres deployment is supported directly; hosted Google sign-in, AWS SQS workers, private embeddings, billing, and multi-tenant operations are commercial hosted-cloud surfaces.

                       ┌───────────────────────────────────────────────┐

MCP/REST clients ─► │ apps/api (auth + rate limit + evidence) │ (Claude Code, │ ├── Memory Inbox / lifecycle / audit │ Codex, Cursor, │ ├── capture ingestion + recall hydration │ OpenCode...) │ ├── context query (memory/web/repo/traces) │ │ ├── repo graph query / symbol / impact │ │ ├── Google sign-in + hosted MCP metadata │ │ └── OpenAPI + usage + operator surfaces │ └───────────────┬───────────────────────────────┘ │ capture / embedding / graph jobs ▼ ┌───────────────────────────────────────────────┐ │ memory-worker (AWS SQS + DLQ fan-out) │ │ ├── auto redaction / curation / save │ │ ├── dreaming butler (prune/merge/resolve) │ │ ├── private Qwen3 embedding service │ │ └── Qdrant dense+sparse indexing │ └───────────────┬───────────────────────────────┘ │ ┌────────────────────┼────────────────────┐ ▼ ▼ ▼ RDS PostgreSQL 16 Qdrant derived index apps/dashboard truth store + audit lore_memories_v12 user-facing SaaS

For detail, see docs/architecture.md.

What's in v2.1.0

v2.1.0 is the Repo Graph API and MCP Tools release. It makes Lore's own repository graph a first-class agent memory surface: deterministic TypeScript/JavaScript repository indexing for files, symbols, imports, calls, routes, tests, and process hints, exposed through API routes and read-only MCP tools so agents ground repository answers in a stable project-context contract instead of ad hoc text search.

v2.1.0 is the current open-core source line. The hosted Lore Cloud production line also runs v2.1.0 on the commercial AWS/Qdrant/private-embedding substrate, but hosted operations, billing, production release automation, and Secret Vault runtime stay in Lore-Context/lore-cloud.

Capability	Status	Where
Repo graph API + MCP tools (`repo.graph_query` / `symbol_context` / `impact` / `detect_changes`)	✅ OSS + hosted production	`packages/repo-graph`, `apps/api`, `apps/mcp-server`
Code knowledge graph indexer	✅ OSS + hosted production	`packages/code-indexer`, `packages/code-indexer-python`
Context Query composing memory + web + repo + tool traces	✅ OSS + hosted production	`apps/api`, `docs/api-reference.md`
7-stream `HybridSearchOrchestrator` (FTS / pgvector / Qdrant dense+sparse / graph / temporal / wiki)	✅ OSS + hosted production	`packages/search`
Cross-encoder reranker (post-fusion, opt-in)	✅ OSS, provider key required	`apps/api/src/rerankers/`
Dreaming butler memory consolidation (prune / merge / resolve / surface)	✅ OSS, flag-gated	`apps/api/src/workers/butler-v18.ts`
Agent memory self-improvement loop + context recipes	✅ OSS, human-gated promotion	`packages/eval`, `packages/search`
SDK middleware (auto-inject + auto-retain for OpenAI / Anthropic clients)	✅ Published	`packages/sdk-middleware-typescript`, `packages/sdk-middleware-python`
Generated SDK source previews	✅ OSS source preview	`packages/sdk-python`, `packages/sdk-go`, `packages/sdk-java`, `packages/sdk-dotnet`
Browser extension capture scaffold	✅ OSS scaffold	`apps/browser-extension`
Secret vault for AI agents (MCP-native, three-button authorization)	Hosted beta, pending crypto audit	commercial runtime in `Lore-Context/lore-cloud`
Cloud Memory Engine: RDS truth store + SQS worker fan-out + Qdrant index	Hosted production	commercial hosted cloud
Private Qwen3-Embedding-0.6B 1024-dim vector service	Hosted production	commercial hosted cloud
Automatic capture ingestion and Memory Inbox exceptions	✅ OSS + hosted production	`apps/api`, `packages/capture`, `apps/dashboard`
Google sign-in + personal vault bootstrap	Hosted production	commercial hosted cloud
Commercial SaaS: individual subscriptions, billing, quota gating	Hosted production	`Lore-Context/lore-cloud`
REST API with API-key auth (reader/writer/admin)	✅ OSS + hosted production	`apps/api`
OpenAPI 3.1 contract at `/openapi.json` (reports `2.1.0`)	✅ OSS + hosted production	`apps/api/src/openapi.ts`
MCP stdio server (legacy + official SDK transport)	✅ OSS + hosted production	`apps/mcp-server`
Next.js dashboard customer workflow scaffold	✅ OSS scaffold + hosted production	`apps/dashboard`
Evidence Ledger API + Dashboard summary	✅ OSS + hosted production	`apps/api`, `apps/dashboard`

| Governance state machine + audit log | ✅ OSS + hosted production | `packages/g

只显示了开头部分；其余内容请在仓库中阅读

Lore Context

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“会计、财务与税务”中的其他服务器比较i

常见问题

替代选择

Finance Toolkit

SolidInvoice

Korea Tax Calculator

作者的 README

Lore Context

What is Lore Context

When to use it

Quick Start

2. Run the quickstart helper and inspect the activation report

3. Generate a real API key (do not use placeholders in any environment beyond local-only dev)

4. Start the API (file-backed, no Postgres required)

5. Write a memory

6. Query context, then inspect the returned traceId in the Evidence Ledger

Architecture

What's in v2.1.0