Fetch web page content using Chrome DevTools MCP when WebFetch fails, returns domain verification errors, or the page requires authentication/JS rendering. Uses the user's running Chrome browser via autoConnect. (agent)
From chrome-fetch-pluginnpx claudepluginhub istarwyh/agent-plugins --plugin chrome-fetch-pluginThis skill uses the workspace's default tool permissions.
CHROME-SETUP.mdSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Automatically extracts reusable patterns like error resolutions, workarounds, and debugging techniques from Claude Code sessions via Stop hook, saving them as learned skills for reuse.
Fetch web content through the user's Chrome browser when WebFetch cannot (domain restrictions, authentication, SPAs needing JS rendering).
new_page(url) to open the target URL in a new tabwait_for(text, timeout: 15000) with an expected keyword — if it times out, proceed anywayevaluate_script:
() => { const main = document.querySelector('main, article, [role="main"], .content, #content'); return (main || document.body).innerText; }
.substring(0, 50000) to truncate.take_snapshot() and read StaticText entriesclose_page(pageId) to clean up (skip if it's the only open page)--autoConnect and Chrome 144+Chrome Connection Issues: If you encounter "Could not connect to Chrome" errors, see the Chrome Setup Guide for detailed troubleshooting steps.
If you encounter any issues with this plugin, please report them following our Support Guide. Your feedback helps improve the community experience!