ChromeDevTools / ChromeDevTools/chrome-devtools-mcp

Feature Request: Add native page content extraction (like BrowserOS's get_page_content)

Open
#1,166 3 comments 0 reactions 1 assignee View on GitHub

@natorion is already working on this.

Since Mar 12, 2026.

collecting-feedback
Dominant language
TypeScript
Stars
52.3k
Forks
4.3k
Avg merge
2d 7h
Merged PRs (30d)
83

Description

Feature Comparison with Other MCPs

After comparing Chrome DevTools MCP with BrowserOS MCP and Playwright MCP, I noticed Chrome DevTools MCP lacks native page content extraction capabilities.

Comparison Table
Feature Chrome DevTools MCP BrowserOS MCP Playwright MCP
Native page content extraction ❌ Requires JS ✅ get_page_content ❌ Requires JS
CSS selector filtering ✅ selector param
Viewport-only extraction ✅ viewportOnly param
evaluate_script ✅ (browser_evaluate)
wait_for ❌ Manual polling ✅ browser_wait_for
Missing Features in Chrome DevTools MCP

Direct page content extraction without JavaScript

Currently, to get page content, users must write JavaScript. BrowserOS MCP provides a much cleaner approach with native get_page_content.

Proposed API
get_page_content: {
  selector?: string;      // CSS selector to filter content
  viewportOnly?: boolean; // Only visible content
  includeLinks?: boolean; // Format links as markdown
  includeImages?: boolean; // Include image references
}
Chrome DevTools MCP Strengths 🌟
  • Excellent wait_for functionality
  • Great performance analysis tools
  • Comprehensive network monitoring
  • evaluate_script with proper JSON serialization
Suggestion

Consider adding a native get_page_content method that does not require users to write JavaScript for simple content extraction. This would significantly improve developer experience!

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.