ChromeDevTools / ChromeDevTools/chrome-devtools-mcp

If the mcp launches an instance it should expose some way to close the browser

Open
#484 5 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

collecting-feedback feature
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.

Right now there is no way to close the browser (via mcp) that is launched via mcp. Close page will refuse to close the only page.

Describe the solution you'd like

Expose to the mcp a way to close the browsers it launched

Describe alternatives you've considered

Using os utils to close manually

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how the MCP launches browsers and how its existing page-close operation handles the last open page. Identify the MCP entry point for browser lifecycle actions, then verify that an exposed close operation can terminate browsers launched through MCP without relying on OS utilities.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.