timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
One memory for every AI tool: your AI picks up where you left off, with decisions and plans.
作者提供的原文
教 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
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 10/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 22/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 BrainOS。按照 https://mcp.popnx.com/i/brainos-hq-brain-os.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月18日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server BrainOS,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "brain-os": { "command": "npx", "args": [ "-y", "brain-os", "serve" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 BrainOS 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"brain-os": {
"command": "npx",
"args": [
"-y",
"brain-os",
"serve"
]
}
}
}用 BrainOS 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 BrainOS,或回答中出现 BrainOS 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 BrainOS
BrainOS 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server BrainOS,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user brain-os -- npx -y brain-os serve 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 BrainOS 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user brain-os -- npx -y brain-os serve应能看到 BrainOS 在列表中并显示已连接
用 BrainOS 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 BrainOS,或回答中出现 BrainOS 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server BrainOS,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "brain-os": { "command": "npx", "args": [ "-y", "brain-os", "serve" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 BrainOS 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 BrainOS 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 BrainOS,或回答中出现 BrainOS 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server BrainOS,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "brain-os": { "type": "stdio", "command": "npx", "args": [ "-y", "brain-os", "serve" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 BrainOS 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 BrainOS 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 BrainOS,或回答中出现 BrainOS 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user brain-os -- npx -y brain-os serveClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"brain-os": {
"command": "npx",
"args": [
"-y",
"brain-os",
"serve"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"brain-os": {
"command": "npx",
"args": [
"-y",
"brain-os",
"serve"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"brain-os": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"brain-os",
"serve"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 brainOS-HQ 验证,该账户拥有此仓库
代码最后更新于前天
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
尚未检查
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/brainos-hq-brain-os)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于前天,最新版本(0.11.2)于前天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有: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
| 本项 BrainOS | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 是 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
One memory across your AI tools. Keep decisions, plans and next steps connected across ChatGPT, Claude, Cursor and other supported AI apps.
[brainos-hq.com](https://brainos-hq.com)
Your AI remembers conversations. It still forgets project state.
Brain OS gives agents operational state: decisions, plans, blockers, and priorities that survive across sessions.
AI agents are powerful inside a session, but long-running work has more state than any one chat: what you decided, what's blocked, what's active, and what should not be reopened. Brain OS gives agents operational state, not conversation logs:
Brain OS is an MCP server that works with any MCP-compatible client: Claude Code, Cursor, Zed, GitHub Copilot, OpenAI Codex, Windsurf, or any agent that speaks the protocol.
Before the agent acts, it can check whether a proposed move conflicts with an existing decision:
> decision_check({ proposal: "switch to Postgres for the new service" })
{ "verdict": "conflict", "conflicting_decision": { "id": "dec_2026_03_14_db_choice", "decision": "Use SQLite for all local-first projects", "reason": "Lower ops burden, no infra to run, fits single-user scope", "rejected_alternatives": ["Postgres", "DuckDB"], "logged_at": "2026-03-14" }, "guidance": "Re-litigating a settled choice. Surface the prior reasoning to the user before proceeding." }
That's the wedge: structured state with enforcement, so agents stop re-opening questions you already answered.
Requires Node.js 20 or newer.
Claude Code:
claude mcp add brain-os -- npx -y brain-os serve
Cursor (.cursor/mcp.json) and other MCP clients:
{
"mcpServers": { "brain-os": { "command": "npx", "args": ["-y", "brain-os", "serve"] } } }
VS Code uses .vscode/mcp.json with a "servers" key and "type": "stdio" in place of "mcpServers".
From chat (no terminal): open your project and ask the agent:
Set up Brain OS in this project.
The agent calls brain_setup. It shows the folder and the exact files it would create, and writes nothing until you say yes. Your existing AGENTS.md / CLAUDE.md are never overwritten. If you already have your own AGENTS.md, the Brain OS rules go to .claude/brain-os/AGENTS.md, and the setup lists any of your files that need a one-line pointer to it. Nothing is written outside the project.
From the terminal:
# In your project
npx brain-os init
Either way, setup does three things:
.claude/commands/ so you can run /brain, /brain:focus, /brain:decide, etc. directly in Claude Code. Bare aliases (/focus, /decide, etc.) install alongside them.AGENTS.md is the canonical file. Thin pointer files cover Claude Code (CLAUDE.md), GitHub Copilot (.github/copilot-instructions.md), Cursor (.cursor/rules/brain-os.mdc), Zed (.zed/rules.md), and Windsurf (.windsurfrules).Flags (brain_setup takes the same options as minimal / include_commands):
npx brain-os init --minimal: install only AGENTS.md + CLAUDE.md and skip the other client pointers (clean-repo mode)npx brain-os init --no-commands: skip the slash commands (MCP server only)npx brain-os init --no-agent-instructions: skip all agent-instructions pointer filesBrain OS can independently read a small, explicit set of repository facts and show drift without updating memory or project state:
npx brain-os reconcile --check .
The matching MCP tool, operational_state_check, observes only package.name, package.version, the current Git branch, and Git HEAD. Optional claimed state, desired state, and decision context are returned as separate layers: observations may be verified, stale, conflicting, unavailable, or different from a claim, but the checker never chooses a winner or applies a change.
The report is ephemeral JSON written to stdout. It creates no fact, evidence, issue, memory, entity, decision, plan, or audit record.
The semantic_recall tool needs an embeddings provider. Everything else (entity_update, decision_log, plan_*, etc.) works without one.
Brain OS does not install an embeddings SDK by default. This keeps the core install small and avoids pulling native ONNX/Sharp dependencies into users who do not need semantic search. Install the optional OpenAI provider beside brain-os, then add BRAIN_EMBEDDINGS to your MCP server env:
npm install brain-os openai
Then configure the provider in your MCP server environment:
{
"brain-os": { "command": "npx", "args": ["-y", "brain-os", "serve"], "env": { "BRAIN_EMBEDDINGS": "openai", "OPENAI_API_KEY": "${OPENAI_API_KEY}" } } }
| Mode | What it does | Setup |
|---|---|---|
local | Temporarily unavailable while the former provider carries unresolved High-severity transitive advisories. | Use keyword recall or the OpenAI provider until an audited local backend ships. |
openai | Uses text-embedding-3-small via the OpenAI API. Faster than local. Costs ~$0.02 per million tokens. | Install openai, set BRAIN_EMBEDDINGS=openai, then reference OPENAI_API_KEY from your shell environment. |
If BRAIN_EMBEDDINGS is unset, the OpenAI provider is missing, or local mode is requested, semantic_recall returns a clear setup error. No silent provider install, model download, or API call occurs. Core tools continue working normally.
Never paste a raw `sk-...` key into your MCP config.
~/.claude.jsonand similar MCP config files are plaintext and easy to expose on screen or in backups. Instead, export the key once in your shell and reference it from the MCP process environment.
| Tool | Description |
|---|---|
entity_read | Read operational state of one or all tracked entities |
entity_update | Update entity state — status, momentum, blockers, next moves |
decision_log | Log a strategic decision with reasoning and alternatives |
decision_check | Check a proposed action against active decisions — returns clear/caution/conflict |
decision_refresh | Refresh an existing decision: bump review_date, append evidence, change status. Metadata only — does not mutate decision content. |
decision_review | Review-debt inbox: buckets overdue decisions (still-true / changed / archive / needs-evidence) and recommends an action for each. Read-only — proposes, you confirm. Auto-detects duplicate-stub decisions. |
context_resolve | Resolve which entity the current work belongs to, from explicit mention / alias / files / lexical signals. Deterministic and confidence-scored — routes known context, never guesses intent. |
focus_get | Get prioritized recommendations on what to work on |
project_evidence_scan | Read-only scan of a repo's native operating state (STATE.md, FLAGS, HANDOFF, ROADMAP/PLAN/TODO, git activity, dirty files) for human gates, next moves, and do-not-touch — grounds focus in repo reality. |
operational_state_check | Ephemeral read-only comparison of allowlisted package/Git facts with optional claimed and desired state; reports evidence-backed drift/conflict without applying changes. |
brain_setup | Set up Brain OS in the open project from chat. Previews the folder and exact file plan, then writes only after the user confirms (single-use preview token). Never overwrites existing instruction files. Local stdio server only. |
pattern_detect | Analyze patterns across all entities |
memory_check | Audit memory quality — flags stale data, contradictions, noise |
memory_commit | End-of-session commit — save all state changes |
semantic_recall | Search memory by meaning using natural language |
audit_log | Read the full mutation history — what changed, when, by whom |
wrap_check | Detect whether meaningful state changes have accumulated since the last wrap |
wrap_auto | Non-interactive safety-net wrap: applies low-risk fields and stages high-risk changes for review |
plan_set | Set an ordered plan for an entity — step 1 becomes active next_move |
plan_advance | Complete or skip a step (requires evidence/reason) — auto-promotes next |
plan_add | Add steps to an existing plan |
plan_read | View plan progress and current step |
risk_assess | Classify risky actions before execution, including public-release and destructive-operation risks |
action_guard | Apply built-in guard templates to common high-risk actions before proceeding |
brain-os init installs slash commands into .claude/commands/ so the agent has a clear vocabulary for working with operational state. Each command installs in two forms: /brain:* (canonical, documented form) and a bare alias (/decide, /focus, etc.) for power-user brevity. /brain is the namespace root and installs once.
It also installs:
.claude/brain-os/PROTOCOL.md (project) and ~/.claude/brain-os/PROTOCOL.md (user; written by npx brain-os init, or by brain_setup only with include_user_protocol=true). The protocol governs tool routing: when an agent runs a Brain OS slash command, it reads the protocol first, then calls entity_read/plan_read/focus_get/etc. as primary. Pulse files become fallback only..claude/agents/brain-os-mode.md. When the main agent delegates Brain OS work to a subagent (e.g. Claude Code's Task tool), it picks up under the same protocol — no risk of subagents falling back to generic file search.templates/hooks/brain-os-routing-guard.py. Opt-in PreToolUse hook that warns if pulse files are read while a .brain/ workspace exists. Install instructions are printed by brain-os init.| Command | Alias | What it does |
|---|
| /brain | — | Project scanner: overview of