Can't open Chrome with a specified profile #1255
Description
Description of the bug
Not really a bug, but I just can't figure out how to make it open a Chrome instance on my desired profile.
Expanding on the basic config:
"mcpServers": {
"chrome-devtools": {
"type": "stdio",
"command": "npx",
"args": ["chrome-devtools-mcp@latest"],
"env": {}
}
},I've tried:
"args": ["chrome-devtools-mcp@latest", "--userDataDir", "/Users/myuser/Library/Application Support/Google/Chrome"],"args": ["chrome-devtools-mcp@latest", "--userDataDir", "/Users/myuser/Library/Application Support/Google/Chrome/Profile 1"],"args": ["chrome-devtools-mcp@latest", "--userDataDir", "/Users/myuser/Library/Application Support/Google/Chrome", "--profileDirectory", "Profile 1"],One of those options (I think option 2) actually manages to open in my correct profile, but then the instructions (e.g., open https://example.com) are not executed, and next time I try to open my profile (manually or via MCP server), it is signed out.
Would appreciate any help.
Reproduction
No response
Expectation
No response
MCP configuration
No response
Chrome DevTools MCP version
0.20.3
Chrome version
No response
Coding agent version
Claude Code 2.1.76
Model version
Sonnet 4.6
Chat log
No response
Node version
v25.2.1
Operating system
macOS
Extra checklist
- I want to provide a PR to fix this bug