Skip to main content
Glama
742,442 tools. Updated 2026-11-04 15:25

"A guide to developing Chrome extensions" matching MCP tools:

  • Fetch Chrome Web Store extensions by category slug. Returns item cards for a given category, with optional count, country, and language parameters.
    MIT
  • List all Chrome extensions with their id, name, version, and enabled status for managing browser extension state.
    MIT
  • List, enable, disable, load, or unload Chrome extensions in the active profile. Control the master switch and manage unpacked extensions for browser automation.
    MIT
    Destructive
  • Clone a Chrome profile into an isolated mcp-stealth location, preserving cookies, history, bookmarks, passwords, and extensions state. Chrome must be closed.
    MIT
  • Add a public Chrome extension to Dolphin{anty} profiles using its Chrome Web Store URL. Non-public or unpublished extensions are rejected.
    MIT

Matching MCP Servers

Matching MCP Connectors

  • Extension and app analytics across Chrome, Edge, Firefox, Google Play, and the Apple App Store. Search and compare extensions and apps; inspect trends, rankings, reviews, and version history; and search supported extension source code. Connect via Streamable HTTP with OAuth. API keys are also supported. Data availability and limits depend on the platform and plan. Documentation: https://chrome-stats.com/docs/mcp Privacy policy: https://chrome-stats.com/privacy Support: support@chrome-stats.com

  • Chrome Web Store — public extension listing data: a single extension by id, free-text search, and…

  • Apply an updated BeatBrowser extension build by restarting its Chrome runtime, skipping manual chrome://extensions visits. Call only after installing/updating or when version-mismatch warnings appear.
    MIT
  • Remove a Chrome extension permanently by its extension ID. To keep it installed but disabled, use the separate enable function.
    MIT
    Destructive
  • Permanently remove a persistent Chrome profile, deleting its cookies, logins, history, and extensions. Requires switching away from the active profile first.
    MIT
    Destructive
  • Retrieve extension errors from chrome://extensions and recent service worker crash logs to diagnose issues.
    MIT
  • Attach to an already-running Chrome browser via DevTools Protocol for automation, preserving login state, cookies, and extensions. Enable remote debugging in Chrome first.
    MIT
  • Send any Chrome DevTools Protocol command to a tab, iframe, or child session and get the raw result, including commands Chrome hides from extensions that are routed through the full DevTools channel.
    Apache 2.0
  • Retrieve Kya-Token identity headers to authenticate your HTTP requests. Use after establishing identity with kya_getAgentIdentity for Playwright, browser extensions, or any HTTP client.
    MIT
  • Lists all installed Chrome extensions with IDs, names, versions, enabled status, and options URLs. Use it to audit, troubleshoot, or manage extensions in an automated browser session.
    MIT