接入你的智能体
从发布者处安装。不是 PlugMCP 端点。
远程 URL 还是本机命令? 两种安装方式的区别
Centralized browser profile management for AI IDEs
bpm is a CLI tool + MCP server that manages isolated Chromium browser profiles across AI-powered development environments like Claude Code, Cursor, and Antigravity.
AI IDEs spawn their own Chromium instances with ephemeral profiles:
No existing tool solves this. Browser MCP does automation, not profile management. AdsPower MCP is closed ecosystem. chrome-cli controls tabs, not profiles.
# Install (requires Go 1.24+)
go install github.com/tquangkhai98/browser-profiles-manager@latest
# Or download a pre-built binary from GitHub Releases:
# https://github.com/tquangkhai98/browser-profiles-manager/releases
# Create a profile
bpm create work-staging
# Launch browser with profile
bpm use work-staging
# Check what credentials exist
bpm creds work-staging
# Sync credentials to another profile
bpm sync work-staging personal
# Import existing Chrome profile
bpm import ~/Library/Application\ Support/Google/Chrome/Default my-chrome
# Map project directory to profile
bpm map ~/projects/my-app work-staging
Add to your AI IDE's MCP config (Claude Code, Cursor, Antigravity):
{
"mcpServers": {
"bpm": {
"command": "bpm",
"args": ["serve"]
}
}
}
bpm profiles work with browser automation MCP servers, letting AI agents control browsers with persistent login sessions. Login once manually, then let your AI agent automate with full authentication — no re-login needed.
# Step 1: Create profiles for each role
bpm create lms-admin
bpm create lms-teacher
bpm create lms-student
# Step 2: Login once per profile (manual)
bpm use lms-admin # → login as admin
bpm use lms-teacher # → login as teacher
bpm use lms-student # → login as student
# Step 3: AI agent uses profiles with persistent sessions ✅
Stable, official, uses accessibility tree for reliable element interaction.
{
"mcpServers": {
"browser-admin": {
"command": "npx",
"args": [
"@playwright/mcp@latest",
"--user-data-dir", "~/.local/share/bpm/profiles/lms-admin"
]
},
"browser-teacher": {
"command": "npx",
"args": [
"@playwright/mcp@latest",
"--user-data-dir", "~/.local/share/bpm/profiles/lms-teacher"
]
}
}
}
Connect to a running Chrome instance launched by bpm. Provides DOM inspection, Network monitoring, and Console access.
First launch Chrome manually with remote debugging enabled:
# macOS example — launch Chrome with remote debugging on port 9222
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
--user-data-dir="$(bpm list --json | jq -r '.[] | select(.name=="lms-admin") | .path')" \
--remote-debugging-port=9222
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["chrome-devtools-mcp@latest", "--browserUrl=http://127.0.0.1:9222"]
}
}
}
AI-native browser automation — describe actions in plain language instead of CSS selectors.
{
"mcpServers": {
"browser-use": {
"command": "npx",
"args": [
"browser-use-mcp@latest",
"--user-data-dir", "~/.local/share/bpm/profiles/lms-admin"
]
}
}
}
⚠️ Important: Never open the same profile in two browsers simultaneously — bpm uses file locks to prevent profile corruption.
bpm create <name> Create isolated profile
bpm list [--json] List profiles with status
bpm delete <name> Delete profile + data
bpm status <name> [--json] Check lock/usage status
bpm use <name> Launch browser with profile
bpm detect [--json] List installed browsers
bpm map <dir> <profile> Map project dir → profile
bpm map --auto [--json] Auto-resolve profile for cwd
bpm map --list [--json] Show all mappings
bpm creds <name> [--json] Inspect credentials in profile
bpm sync <src> <dst> Sync credentials between profiles
bpm import <path> <name> Import existing Chrome profile
bpm export <name> <path> Export profile for backup
bpm serve Start MCP server
All read commands support --json for scripting and piping:
$ bpm list --json
[
{
"name": "work-staging",
"browser": "chrome",
"locked": false,
"created_at": "2026-03-29T12:00:00Z"
}
]
$ bpm detect --json
[
{
"name": "Google Chrome",
"id": "chrome",
"exe_path": "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"
}
]
$ bpm creds work-staging --json
{
"profile_name": "work-staging",
"sites": [
{"domain": "github.com", "cookie_count": 12, "login_count": 1}
],
"total_cookies": 12,
"total_logins": 1
}
When you login to GitHub in one browser profile, that login is stored as cookies and saved passwords. Credential sync copies those databases to another profile:
Cookies, Login Data) from sourcemake build # Build CLI with version info
make test # Run all tests
make cover # Generate coverage report
make lint # Run staticcheck
make install # Install to $GOPATH/bin
make desktop # Build desktop app
make dev # Desktop dev mode with hot-reload
make clean # Remove build artifacts
browser-profiles-manager/
├── main.go # CLI entry point
├── cmd/ # CLI commands (Cobra)
├── internal/ # Core business logic
│ ├── profile/ # Profile CRUD + locking
│ ├── browser/ # Browser detection & launch
│ ├── credential/ # Credential read/sync (SQLite)
│ ├── mapping/ # Directory ↔ profile mapping
│ ├── config/ # Configuration management
│ └── mcp/ # MCP server implementation
├── desktop/ # Wails desktop app
├── Makefile # Build automation
└── docs/ # Documentation
MIT
Manage isolated Chromium browser profiles across AI IDEs (Claude Code, Cursor, Antigravity) — CLI + MCP server + desktop app
工具
暂无工具列表。远程服务器在首次健康检查后会获得工具列表。
常见问题
在本页复制适用于 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 配置。它使用发布者的安装方式,而不是 PlugMCP 代理。
此记录未列出必需的环境变量。
Browser Profiles Manager 通过 stdio 在本地运行。
上次检查时间:2026-10-28。 Manage isolated Chromium browser profiles across AI IDEs (Claude Code, Cursor, Antigravity) — CLI + MCP server + desktop app