List item cards for any Chrome Web Store extensions category by slug, with configurable results count, country, and language.
MIT
510,035 tools. Updated 2026-09-03 18:53
"A guide to developing Chrome extensions" matching MCP tools:
- List all Chrome extensions with their id, name, version, and enabled status for managing browser extension state.MIT
- Create a named persistent Chrome profile to retain cookies, logins, and extensions across browser runs, offering a reusable user-data directory.MIT
- Clone a Chrome profile into an isolated mcp-stealth location, preserving cookies, history, bookmarks, passwords, and extensions state. Chrome must be closed.MIT
- List, enable, disable, load, or unload Chrome extensions. Controls the master switch for extensions and handles unpacked extensions from a folder.MIT
- Remove a Chrome extension permanently by its extension ID. To keep it installed but disabled, use the separate enable function.MIT
Matching MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceProvides semantic search capabilities over the Plesk Extensions Guide documentation using Retrieval-Augmented Generation (RAG) and vector embeddings. It enables AI assistants to retrieve relevant technical information and answer natural language queries regarding Plesk extension development.
- FlicenseNot gradedqualityBmaintenanceExposes PICO XR building blocks as MCP tools, enabling AI agents to programmatically configure XR scenes for PICO devices through idempotent, non-destructive operations.1
Matching MCP Connectors
Extension and app analytics across Chrome, Edge, Firefox, Google Play, and the Apple App Store.
Trust signals for AI agents: an open agent-readiness standard and developer tool guide. Read-only.
- Permanently delete a Chrome profile and all its data, including cookies, logins, history, and extensions. Switch away from the active profile before deletion.MIT
- Retrieve extension errors from chrome://extensions and recent service worker crash logs to diagnose issues.MIT
- Launch Google Chrome with your real profile to retain cookies, extensions, and sessions. Use only on explicit user request to open Chrome.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
- Retrieve popular Chrome Web Store extensions by category, sort method, and count. Uses curated data for known extensions due to lack of public API.MIT
- 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
- Access detailed guides for developing Backstage plugins, covering setup, structure, APIs, testing, and best practices to build custom extensions.MIT
- Lists Chrome extensions accessible through the browser's CDP bridge for automation and control purposes.MIT
- Update Chrome extensions for multiple browser profiles in GoLogin. Add official or custom extensions and remove unnecessary ones in bulk, ensuring consistent profile configurations.MIT
- Add a public Chrome extension to Dolphin{anty} profiles using its Chrome Web Store URL. Non-public or unpublished extensions are rejected.
- Retrieve a comprehensive guide for a specific Viewer 3D API topic, such as camera, selection, or markup, to assist in developing Trimble Connect extensions.
- Retrieve Chrome Web Store top charts for trending, popular, or notable extensions. Specify country, language, and item count to get structured JSON data for analysis.MIT
- Identify trending Chrome extensions and themes using recent user and rating-count movement data. Filter by category, developer, permissions, status, and other criteria to find emerging items.MIT
- Facet Chrome Web Store data into aggregation buckets by item type, category, developer, permission, or manifest version. Filter by query, rating, and more to analyze extensions.MIT