Chrome DevTools integration for debugging, performance analysis, and browser automation via MCP.
Works with
Provides tools for page navigation, element inspection via snapshots, clicking, form filling, screenshot capture, and JavaScript evaluation
Operates on a persistent Chrome profile with automatic browser startup; switch between multiple pages using list_pages and select_page
Supports efficient workflows: navigate, wait for content, take snapshots to identify elements by uid , then interact
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionchrome-devtoolsExecute the skills CLI command in your project's root directory to begin installation:
Fetches chrome-devtools from chromedevtools/chrome-devtools-mcp and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate chrome-devtools. Access via /chrome-devtools in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
33.3K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
33.3K
stars
Browser lifecycle: Browser starts automatically on first tool call using a persistent Chrome profile. Configure via CLI args in the MCP server configuration: npx chrome-devtools-mcp@latest --help.
Page selection: Tools operate on the currently selected page. Use list_pages to see available pages, then select_page to switch context.
Element interaction: Use take_snapshot to get page structure with element uids. Each element has a unique uid for interaction. If an element isn't found, take a fresh snapshot - the element may have been removed or the page changed.
navigate_page or new_pagewait_for to ensure content is loaded if you know what you look for.take_snapshot to understand page structureuids from snapshot for click, fill, etc.filePath parameter for large outputs (screenshots, snapshots, traces)pageIdx, pageSize) and filtering (types) to minimize dataincludeSnapshot: false on input actions unless you need updated page statetake_snapshot (text-based, faster, better for automation)take_screenshot (when user needs to see visual state)evaluate_script for data not in accessibility treeYou can send multiple tool calls in parallel, but maintain correct order: navigate → wait → snapshot → interact.
If chrome-devtools-mcp is insufficient, guide users to use Chrome DevTools UI:
If there are errors launching chrome-devtools-mcp or Chrome, refer to https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/troubleshooting.md.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Useful defaults in chrome-devtools — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
chrome-devtools fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added chrome-devtools from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
chrome-devtools has been reliable in day-to-day use. Documentation quality is above average for community skills.
chrome-devtools reduced setup friction for our internal harness; good balance of opinion and flexibility.
chrome-devtools is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in chrome-devtools — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
chrome-devtools reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: chrome-devtools is focused, and the summary matches what you get after install.
Registry listing for chrome-devtools matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 28