79 tagged chrome-devtools-protocol, measured the same way as everything else here.
Browse within: browser-automation 35chrome-extension 18cdp 16llm-tools 12manifest-v3 11boss-zhipin 7chrome 7cities-skylines-2 7claude-code-plugins 7claude-code-plugins-marketplace 7claude-plugins 7nodejs 7brave 6chrome-devtools 6
ShalomObongo/chrome-bridge-mcp
Skill Claude CodeCodex
Drive the user's real Chrome browser — their own profile, tabs, cookies and logged-in sessions — through the chrome-bridge MCP server. Use for tasks that need existing browser state: reading a page behind a login, filling a form on a site the user is signed into, testing a local app in a real browser, or inspecting…
Skill Claude CodeCodex
Analyze a chart — set up symbol/timeframe, add indicators, scroll to key dates, annotate, and screenshot. Use when the user wants technical analysis or chart review.
Skill Claude CodeCodex
Full Pine Script development loop — write code, compile, fix errors, iterate. Use when building a new indicator or strategy in TradingView.
Skill Claude CodeCodex
Generate a comprehensive strategy performance report — metrics, trade analysis, equity curve, and recommendations. Use after backtesting a Pine Script strategy.
Skill Claude CodeCodex
Runtime observability for React Native/Expo apps on Android. Use when debugging RN UI, performance (FPS, JS blocking), network, re-renders, or runtime errors on a running app — understand the current screen and UI findings, capture screenshots, UI trees, ref snapshots, per-request network, CDP console/heap/CPU…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: