timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Durable shared memory for AI agents: search, write and correct facts, with per-client policy.
作者提供的原文
教 AI 做这类工作的 Skill,可与本项一起使用
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-10 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 4/4 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Lumberroom。按照 https://mcp.popnx.com/i/cloud-lumberroom-lumberroom.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/4 项检查 · 你的提问会经过开发者的服务器(mcp.lumberroom.cloud) · ✓ 命令已检查 2026年11月20日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Lumberroomhttps://mcp.lumberroom.cloud/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsLumberroom
用 Lumberroom 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Lumberroom,或回答中出现 Lumberroom 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Lumberroomhttps://mcp.lumberroom.cloud/mcp开启新聊天,输入前先从插件列表中选择 Lumberroom
用 Lumberroom 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Lumberroom,或回答中出现 Lumberroom 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user lumberroom https://mcp.lumberroom.cloud/mcp应能看到 Lumberroom 在列表中并显示已连接
用 Lumberroom 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Lumberroom,或回答中出现 Lumberroom 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Lumberroom 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Lumberroom,或回答中出现 Lumberroom 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Lumberroom 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Lumberroom,或回答中出现 Lumberroom 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.lumberroom.cloud/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user lumberroom https://mcp.lumberroom.cloud/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"lumberroom": {
"url": "https://mcp.lumberroom.cloud/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"lumberroom": {
"type": "http",
"url": "https://mcp.lumberroom.cloud/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过域名 lumberroom.cloud 验证(注册中心会核实域名所有权)
代码最后更新于4天前
不适用:由 lumberroom.cloud 的所有者自己运行的云端服务器,你不会运行仓库里的代码
在 532 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/cloud-lumberroom-lumberroom)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于4天前,最新版本(0.2.0)于10天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Official Exa MCP for web search, content fetching, and multi-step research.
Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| 本项 Lumberroom | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 是 | 是 | 否 | 否 |
| 基础检查 | 4/4 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | Apache-2.0 | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
One memory that every AI tool you use can read from and write to, with you deciding what each one is allowed to see.
More videos: Lumberroom playlist · lumberroom.cloud/videos
You run seven AI surfaces. Each keeps its own memory. None of them share. You re-explain your setup to ChatGPT, then again to Claude, then again to your coding agent, and when you correct one of them the others never find out. Lumberroom holds the facts once, on infrastructure you own, and every tool reads from the same place.
Three layers, doing three different jobs:
machines.desktop.os = Ubuntu 26.04, confirmed by you, on a date, superseding an older value.The value is in the second and third. Full thesis: docs/prd/system-prd.md.
Claude Code, Hermes, OpenWebUI, lumberroom CLI ──── static bearer token ────┐
│ Claude.ai, Cowork, mobile, ChatGPT ── OAuth 2.1 + PKCE ───────────────┤ ▼ Caddy (auto-TLS) ──▶ lumberroom (Rust: axum + rmcp) │ ▼ Postgres 16 + pgvector (127.0.0.1)
One Rust binary, a Postgres database with pgvector, and two clients that talk to them. Ten MCP tools behind four capabilities, mounted at /mcp. A built-in OAuth 2.1 authorization server for the surfaces that need a browser, with static bearer tokens honoured beside it whatever AUTH_MODE says. Envelope encryption for private, client-side encryption for sealed. A console at /console for the decisions a person has to make.
git clone https://github.com/lumberroom/lumberroom.git && cd lumberroom
sudo ./deploy/install.sh
That is token mode on loopback: the server binds 127.0.0.1:8787, opens no public port, and prints the command to run on your Mac. The client token is the first "token" field in the .env the installer writes (mode 600) in the clone. Add --domain and --auth-mode oauth when a browser has to reach it. The installer pulls ghcr.io/lumberroom/lumberroom-server:0.6.0 and falls back to building from this tree when the pull fails; --build-local skips the pull. It pins a version rather than tracking latest, because a memory store that upgrades itself while you sleep is not a feature.
Watch the self-host walkthrough: youtu.be/Km7CcmcsS2w.
Moved: the engine used to publish as ghcr.io/the-cybersapien/lumberroom-server. That image stays public, frozen at 0.4.0, and takes no new versions; pull ghcr.io/lumberroom/lumberroom-server instead.
The client runs on the machine holding your transcripts and your credentials, and talks to a server you host. Four ways in, in the order most people want them.
brew install lumberroom/lumberroom/lumberroom
Installed from the old the-cybersapien/lumberroom tap? The next brew update follows the move and renames the tap. Homebrew stops trusting a tap whose owner changed, so run brew trust lumberroom/lumberroom once, or brew upgrade refuses the formula.
cargo install lumberroom
A binary, with no package manager. Four targets, macOS and Linux on arm64 and x86_64:
tag=v0.6.0; target=aarch64-apple-darwin # or x86_64-apple-darwin,
base=https://github.com/lumberroom/lumberroom/releases/download/$tag curl -fsSLO "$base/lumberroom-${tag#v}-$target.tar.gz" curl -fsSL "$base/SHA256SUMS" | grep "$target.tar.gz" | shasum -a 256 -c - tar -xzf "lumberroom-${tag#v}-$target.tar.gz" && install -m 755 lumberroom ~/.local/bin/
Check the archive before you run what came out of it. Every release carries one SHA256SUMS over every asset, written by the job that collected them all.
On a machine where apt or dnf is how software arrives, the release also carries a .deb and an .rpm per architecture. Both hold the musl binary, statically linked, so neither declares a runtime dependency:
sudo dpkg -i lumberroom_0.6.0-1_amd64.deb # or lumberroom_0.6.0-1_arm64.deb
sudo rpm -i lumberroom-0.6.0-1.x86_64.rpm # or lumberroom-0.6.0-1.aarch64.rpm
Then point it at your server:
lumberroom doctor
doctor reports the endpoint, whether your credential is accepted, and which tools it opens. It is the first command to run and the one to run when something is wrong.
To wire a Mac into Claude Code, which installs the MCP server, the session hook and the CLAUDE.md rule in one pass:
LUMBERROOM_TOKEN=<token> ./client/wire-mac.sh --url http://127.0.0.1:8787
For Hermes Agent, lumberroom-hermes is a memory provider: recall on every turn and the engine's own tools for writes. It uses lumberroom.cloud unless base_url names your own engine, which runs the same code.
Then prove the loop, which states a fact in one session and recovers it in a fresh one:
LUMBERROOM_URL=http://127.0.0.1:8787 LUMBERROOM_TOKEN=<token> ./scripts/done-when-test.sh
Back up secrets/lumberroom-kek somewhere this box does not hold. Losing it makes every private row unreadable, in the database and in every backup.
| docs/faq.md | The questions people actually ask: deploying, granting a client, keys, refusals |
| docs/managing.md | Running a live store: approving a client, changing what it may reach, the two queues |
| DEPLOY.md | The runbook: both deploy paths, the KEK, backups, troubleshooting |
| deploy/oauth.md | The OAuth production path, per surface, with the consent screen |
| docs/permissions.md | Every grant field, both axes, and which tools each capability opens |
| docs/connect-claude-code.md | Wiring Claude Code on a Mac, end to end |
| docs/connect-claude-ai.md | The memory rules for claude.ai, Cowork and other connector clients: instructions to paste, or a skill |
| docs/architecture.md | The ports-and-adapters shape and where each part lives |
| docs/decisions/ | Why each part is shaped the way it is, one record per choice |
| docs/traps.md | Findings that cost real time, and what to do instead |
| VERIFY.md | The gates: what each checks, how to run it, what a pass looks like |
| docs/benchmarks.md | Every retrieval figure, with the run that produced it |
| CONTRIBUTING.md | Building, testing, and what a pull request needs |
| docs/README.md | The full index: PRDs, phase specs, research, design |
Every tool sits behind one grant, and src/mcp/capability.rs holds the single table that decides which. tools/list filters on it, so a model never sees a tool its credential cannot call, and the service checks the grant again on the call. Signatures are additive: they have gained arguments and never lost one.
| Grant | Tools |
|---|---|
| Open to every authenticated client | context_bootstrap, memory_search, memory_write, registry_get, alias_list |
mayDelete | memory_forget |
mayReadHistory | memory_history, registry_history |
registryWrite | registry_set, alias_set |
Namespace and sensitivity still apply inside every call. Full signatures and what each one does: docs/permissions.md.
possible_conflicts is what makes a correction stick. When a write lands close to an existing fact but not close enough to collapse into it, the server returns the neighbours it refused to merge, and the model calls memory_write again with supersedes. The store cannot tell a correction from a restatement; the model in the conversation is the only party that can.
user:me facts about you and how you workproject: facts scoped to one codebaseglobal facts true everywhere: infrastructure, conventions, credential locationspersonal:* and credentials:* classify above open by defaultA grant pairs a namespace glob with a sensitivity ceiling, on each of the read and write axes. {"namespace": "project:*", "max": "private"} grants every project namespace up to private. Two patterns matching one namespace resolve to the more generous ceiling.
The three levels are three different mechanisms:
What `private` does not protect, stated here rather than buried in a research file. The embedding stays plaintext, because there is no ANN index over ciphertext and an unsearchable level would push everything worth protecting back into open. Published inversion work recovers most of a short text from its embedding: Morris et al. report 92% exact recovery of 32-token inputs with black-box query access, a 2025 reproduction confirms it, and later work drops the need for the victim's model. Those are figures from the literature, not measurements on this system. The claim lumberroom makes is narrow and it is the one to hold it to: private protects the verbatim text of a row from whoever holds the database, and leaks its gist. It protects nothing against the live server, which decrypts to answer a search. Evidence: docs/research/encryption-and-sensitivity.md §1.
lumberroom help is the authoritative list. One client, the Rust one, shipped as a release binary and on the Homebrew tap.
lumberroom doctor # connectivity, auth, readiness, tool list
lumberroom clients # registered OAuth clients, how each registered, consent state lumberroom search "how do we deploy" lumberroom write "..." --namespace user:me --tags preference lumberroom review [--source conflict,stale,proposal] [--limit N] [--days N] [--min-similarity X] [--json] lumberroom review --dates # undated facts whose own text names a day lumberroom review --registry # registry entries due for review, non-canonical keys lumberroom review --dismissed # lists the dismissed-pair ledger lumberroom review --undismiss , # removes one pair from the ledger lumberroom registry get|set|alias ... lumberroom stats [--hours 168] [--by-client] lumberroom export --obsidian ~/vault lumberroom seal --namespace credentials:aws lumberroom tools
The lumberroom Rust CLI (crates/lumberroom) carries the archive commands:
lumberroom archive export ~/store.lumber --passphrase-stdin
lumberroom archive import ~/store.lumber --passphrase-stdin --dry-run
The con