ChromeDevTools / ChromeDevTools/chrome-devtools-mcp
Support multiple Chrome Profiles
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 52.3k
- Forks
- 4.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 83
Description
Is your feature request related to a problem? Please describe.
When multiple profiles are open at the same time, there's no way to control which profile will be automated by the MCP server. The MCP server will select the default profile as determined by Chrome.
Describe the solution you'd like
A way to explicitly select a profile when running the MCP server.
Describe alternatives you've considered
--profile-directory can be used on Chrome to specify the default profile (https://superuser.com/questions/377186/how-do-i-start-chrome-using-a-specified-user-profile), this might be a good option (which we should document if it works).
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the MCP server startup and Chrome launch configuration, then check how command-line options are parsed and passed to the browser. Determine whether --profile-directory can select an already-open profile, and document or implement explicit profile selection with coverage for multiple profiles. Done means a user can reliably choose the profile the server automates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100