ChromeDevTools / ChromeDevTools/chrome-devtools-mcp

AI agent does not automatically invoke MCP / performance tools without explicit instruction

Open
#940 6 comments 0 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

Description of the bug

When prompting an AI agent to “check LCP” or investigate slow page loads, the agent does not automatically invoke the relevant DevTools MCP performance tools. Tool usage only occurs when explicitly instructed. This seems like a tool discoverability/description issue, and improving tool metadata or prompt-to-tool mapping could make performance debugging more natural.

Reproduction

Chrome DevTools MCP server

AI assistant Cursor IDE invoking MCP tools

Tested across multiple prompts related to LCP and performance debugging

Expectation
Image Image
MCP configuration

No response

Chrome DevTools MCP version

latest

Chrome version

No response

Coding agent version

No response

Model version

No response

Chat log

No response

Node version

No response

Operating system

None

Extra checklist
  • I want to provide a PR to fix this bug

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 reproducing the behavior with the Chrome DevTools MCP server and Cursor IDE using prompts about LCP and slow page loads. Inspect the performance tool metadata and prompt-to-tool mapping described in the issue. Done means relevant performance tools are invoked from natural performance-debugging prompts without explicit tool instructions.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devtools, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.