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.
Skills that teach the AI this kind of work; they work alongside this one
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
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 10/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 22/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install BrainOS. Follow https://mcp.popnx.com/i/brainos-hq-brain-os.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 18, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server BrainOS for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "brain-os": { "command": "npx", "args": [ "-y", "brain-os", "serve" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the BrainOS tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"brain-os": {
"command": "npx",
"args": [
"-y",
"brain-os",
"serve"
]
}
}
}Use BrainOS and tell me what you can do for me, then show me one thing✓ If Claude says it is using BrainOS or shows a BrainOS tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect BrainOS yet
BrainOS runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect BrainOS
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server BrainOS for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user brain-os -- npx -y brain-os serve 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the BrainOS tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user brain-os -- npx -y brain-os serveYou should see BrainOS listed as connected
Use BrainOS and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using BrainOS or shows a BrainOS tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server BrainOS for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "brain-os": { "command": "npx", "args": [ "-y", "brain-os", "serve" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the BrainOS tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use BrainOS and tell me what you can do for me, then show me one thing✓ If Cursor says it is using BrainOS or shows a BrainOS tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server BrainOS for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "brain-os": { "type": "stdio", "command": "npx", "args": [ "-y", "brain-os", "serve" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the BrainOS tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use BrainOS and tell me what you can do for me, then show me one thing✓ If VS Code says it is using BrainOS or shows a BrainOS tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
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"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: brain-osBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The registry name was verified with the GitHub account brainOS-HQ, which owns the repo
Code last changed 2 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/brainos-hq-brain-os)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 2 days ago, and the latest version (0.11.2) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Search and read Empryo's documentation. Read-only, no auth, no local access.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| This one BrainOS | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | Yes | Yes | Yes | No | No |
| Basic checks | 3/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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