timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Drop-in chrome-devtools-mcp proxy sharing one persistent logged-in Chrome.
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 | 0/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 | 12/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 MCP Chrome Launcher. Follow https://mcp.popnx.com/i/hsm207-mcp-chrome-launcher.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 17, 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 MCP Chrome Launcher 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": { "chrome-launcher": { "command": "npx", "args": [ "-y", "mcp-chrome-launcher" ] } } } 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 MCP Chrome Launcher 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": {
"chrome-launcher": {
"command": "npx",
"args": [
"-y",
"mcp-chrome-launcher"
]
}
}
}Use MCP Chrome Launcher and tell me what you can do for me, then show me one thing✓ If Claude says it is using MCP Chrome Launcher or shows a MCP Chrome Launcher 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 MCP Chrome Launcher yet
MCP Chrome Launcher runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect MCP Chrome Launcher
B · Others in Web & browsers that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
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 MCP Chrome Launcher 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 chrome-launcher -- npx -y mcp-chrome-launcher 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 MCP Chrome Launcher 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 chrome-launcher -- npx -y mcp-chrome-launcherYou should see MCP Chrome Launcher listed as connected
Use MCP Chrome Launcher and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using MCP Chrome Launcher or shows a MCP Chrome Launcher 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 MCP Chrome Launcher 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": { "chrome-launcher": { "command": "npx", "args": [ "-y", "mcp-chrome-launcher" ] } } } 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 MCP Chrome Launcher 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 MCP Chrome Launcher and tell me what you can do for me, then show me one thing✓ If Cursor says it is using MCP Chrome Launcher or shows a MCP Chrome Launcher 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 MCP Chrome Launcher 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": { "chrome-launcher": { "type": "stdio", "command": "npx", "args": [ "-y", "mcp-chrome-launcher" ] } } } 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 MCP Chrome Launcher 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 MCP Chrome Launcher and tell me what you can do for me, then show me one thing✓ If VS Code says it is using MCP Chrome Launcher or shows a MCP Chrome Launcher 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
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user chrome-launcher -- npx -y mcp-chrome-launcherClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"chrome-launcher": {
"command": "npx",
"args": [
"-y",
"mcp-chrome-launcher"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"chrome-launcher": {
"command": "npx",
"args": [
"-y",
"mcp-chrome-launcher"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"chrome-launcher": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-chrome-launcher"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based 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 19, 2026
The registry name was verified with the GitHub account hsm207, 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
No entries on OSV.dev for mcp-chrome-launcher@0.1.3
Checks only this package version, not every dependency · checked Nov 17, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/hsm207-mcp-chrome-launcher)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.1.3) 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: Browser Use, changedetection.io (official), Apify MCP Server, Pomerado, Actionbook
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
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Official changedetection.io MCP: web page change tracking, back-in-stock and price alerts.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Connect your agents to any website. The cheaper, faster and more reliable alternative to browser use
Let your AI agent operate any website through a real, logged-in browser session.
| This one MCP Chrome Launcher | Browser Use | changedetection.io (official) | Apify MCP Server | Pomerado | Actionbook | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Cloud or install 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 |
| Needs a key | No | Yes | No | Yes | No | No |
| Add with + in Claude | No | Yes | No | No | No | No |
| Basic checks | 3/3 | 5/5 | 3/3 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | Apache-2.0 | MIT | MIT | 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.
mcp-chrome-launcherOne persistent, logged-in Chrome shared across all your AI agents, IDE windows, and Playwright/Puppeteer scripts—launched lazily on demand.
Zero runtime dependencies • Cross-platform (Windows, macOS, Linux) • 100% Test Coverage • Drop-in replacement for chrome-devtools-mcp
By default, Google's chrome-devtools-mcp launches Chrome over a private pipe (--remote-debugging-pipe) and locks the user profile directory. That creates three daily headaches:
--isolated wipes your logins every run, while --browserUrl forces you to manually boot Chrome with special flags from a terminal before opening your IDE.mcp-chrome-launcher fixes all three automatically. Drop it in place of chrome-devtools-mcp—it stays completely invisible on IDE startup, lazy-launches one detached Chrome on `127.0.0.1:9223` the moment a browser tool is actually called, and connects every MCP client and external script to that single warm, logged-in session.
| Capability | Default chrome-devtools-mcp | chrome-devtools-mcp --isolated | `mcp-chrome-launcher` |
|---|---|---|---|
| Keeps logins, cookies & extensions | ✅ | ❌ (Wiped every run) | ✅ |
| Multiple IDE windows & parallel agents | ❌ (SingletonLock crash) | ✅ (Separate browsers) | ✅ (One shared browser) |
| Attach Playwright / Puppeteer / CDP scripts | ❌ (Private pipe) | ❌ (Private pipe) | ✅ (`http://127.0.0.1:9223`) |
| Zero browser popup on IDE startup | ❌ / Varies | ❌ / Varies | ✅ (Lazy-launches on `tools/call`) |
| Survives IDE / agent restarts | ❌ | ❌ | ✅ (Detached process) |
Replace chrome-devtools-mcp with mcp-chrome-launcher in your MCP config (claude_desktop_config.json, .cursor/mcp.json, Windsurf, Gemini CLI, etc.). Any extra flags pass straight through to chrome-devtools-mcp!
*(Before first run: close any existing Chrome window already holding ~/.chrome-dev-profile without remote debugging.)*
npx (Recommended){
"mcpServers": { "chrome-devtools": { "command": "npx", "args": [ "-y", "mcp-chrome-launcher@latest" ] } } }
claude mcp add chrome-devtools -- npx -y mcp-chrome-launcher@latest
Any unrecognized flags (like --categoryExtensions) forward directly to chrome-devtools-mcp:
{
"mcpServers": { "chrome-devtools": { "command": "node", "args": [ "/path/to/mcp-chrome-launcher/mcp-chrome-launcher.mjs", "--port=9223", "--allowUnrestrictedPaths", "--categoryExtensions" ] } } }
Because Chrome exposes its DevTools endpoint locally on 127.0.0.1:9223, your own E2E scripts or scrapers can jump right into the exact browser session your AI agent is driving:
import { chromium } from 'playwright';
const browser = await chromium.connectOverCDP('http://127.0.0.1:9223'); const context = browser.contexts()[0]; const page = context.pages()[0]; console.log('Sharing live tab with MCP:', await page.title());
chrome-devtools-mcp immediately over stdio so initialize and tools/list finish fast without opening a browser window.stdin on the first tool invocation, checks if 127.0.0.1: is already live, and—if not—spawns a detached Chrome instance and waits until DevTools responds.stderr if another process owns the port or an un-debugged Chrome holds the profile lock.--chromePath).Usage: mcp-chrome-launcher [options] [chrome-devtools-mcp-args...]
Options: --port Remote debugging port (default: 9223) --userDataDir Chrome user data directory (default: ~/.chrome-dev-profile) --chromePath Path to Chrome executable (default: auto-detected) -h, --help Show this help message -v, --version Show version number
Chrome is intentionally spawned detached and bound strictly to loopback (127.0.0.1: ) so subsequent agent sessions and local scripts can reuse your warm tabs. Any local process on your machine can connect to 127.0.0.1: while that browser window stays open—quit that Chrome window when finished to close the debug port.