All servers / Developer / Extension.dev MCP server
Extension.dev MCP server
MCP server that lets AI agents build, run, debug, test and ship browser extensions to the Chrome Web Store, Firefox Add-ons, Edge Add-ons and the App Store. Bui
Tested by ConnectATDScore 86 out of 100. Tested 2026-11-19 on package version 11.0.0. Package: @extension.dev/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (25.4 seconds including download)
- Tools offered: 27
- Last published: 2026-11-16
- Weekly downloads (npm): 727
- License: Apache-2.0 · Direct dependencies: 8
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
extension_create4 of 4 parameters describedCreate an extension project from a template (extension_templates); it may init git. It is verified, so the next step is extension_dev, not a build; `scripts` name the outputs (`npm run build` writes dist/chromium). Sends one draft_seeded event; the readme's Telemetry section turns it off.
extension_templates9 of 9 parameters describedBrowse the template catalog or read a template's files. TypeScript is slug 'typescript', shadcn 'sidebar-shadcn'; AI templates tag 'ai'.
extension_build15 of 15 parameters describedBuild the extension on this machine into dist/<browser>/; never for sharing (extension_builds). Refuses a dist a dev session serves unless outDir.
extension_dev24 of 24 parameters describedRun the extension while you edit it (dev build, hot reload, browser): the first call for "run my extension". ready.status "ready" means nothing else to call. extension_start runs the production build.
extension_start21 of 21 parameters describedRun the PRODUCTION build in a browser (extension_dev is for writing code); no hot reload or extension_logs. Bridge verbs need allowControl:true (Extension.js 4.1.34 or later; older is refused as engine-unsupported).
extension_try7 of 7 parameters describedRun a published extension.dev build in a fresh profile on this machine, no install, and screenshot it; warn the person about what it can reach. End with action:'close'; a local project is extension_dev.
extension_stop5 of 5 parameters describedStop a dev or start session, naming the server and browser pid it ended. Call it when done.
extension_manifest_validate5 of 5 parameters describedValidate a manifest.json across browsers; buildBlocking lists the errors that make extension_build refuse.
extension_theme_verify2 of 2 parameters describedVerify a Chrome theme manifest headless: the colors Chrome would paint and the keys it discards.
extension_analyze3 of 3 parameters describedAnalyze a BUILT extension in dist/<browser>: sizes, entries, permissions, store checks (not on a dev build).
extension_assert4 of 4 parameters describedRun a test stage on an extension_dev or extension_start session: pass, fail, not ready (a precondition) or inconclusive per expectation. Debug-port checks: extension_start allowControl:true; content-script-injected and console-errors-empty: extension_dev only.
extension_inspect8 of 8 parameters describedInspect a web page (or targetId) over the debugger protocol: HTML, DOM, console, probes, closed shadow roots. Surfaces by name are extension_dom_snapshot. Firefox: agent bridge, needs allowEval:true.
extension_list_extensions2 of 2 parameters describedList the extensions in a session's browser; its own carries ownExtension:true.
extension_logs12 of 12 parameters describedRead a dev session's logs from every context in one timeline, or follow:true for live frames after the replayed ring. Works on a `npx extension dev` run by hand (follow needs --allow-control there); not on extension_start.
extension_eval10 of 10 parameters describedEvaluate JavaScript in a running extension's background, surface, content script, page or targetId. Needs allowEval:true at start (by hand: --allow-eval) on every route, the debug port included, whose runs carry a user gesture. Safari: pages only; extension_logs reads the background.
extension_storage9 of 9 parameters describedRead or write one chrome.storage key from the background, over the control channel.
extension_reload6 of 6 parameters describedReload the extension's background, or a tab, over the control channel (allowControl); a background reload waits up to 5 s.
extension_network9 of 9 parameters describedStub a network response on a Chromium session: add a rule, list or clear the rules, or read which requests hit one or missed. Rules last until extension_stop. Firefox is refused.
extension_open15 of 15 parameters describedOpen an extension surface or a url, or replay the toolbar action, a context menu item or a shortcut, over the control channel (by hand: --allow-control). A url opens in a background tab and answers target.targetId for extension_screenshot and the readers. A replay carries no user gesture.
extension_dom_snapshot13 of 13 parameters describedTake a shallow DOM snapshot of one open surface or targetId, or list what is open (listTargets on the debug port, listTabs). Closed shadow roots and probes: extension_inspect.
extension_element18 of 18 parameters describedClick, fill, read or wait for one element by CSS selector, or send trusted mouse and key input in an open surface, a page by url or a targetId. Runs no caller code, so no allowEval; Chromium only.
extension_screenshot12 of 12 parameters describedTake a .png of one surface, page or targetId in a live session (Safari: pages only); a closed surface is opened first, answering opened: true.
extension_wait6 of 6 parameters describedWait for a session to be ready, or for: "rebuild" after an edit; only after wait:false, a ready.status not "ready", or noBrowser; answers port, controlPort and cdpPort or rdpPort. A page condition is extension_eval until; never sleep in a shell.
extension_add_feature3 of 3 parameters describedPlan the surface before adding an options page, a popup, a side panel, a content script, a devtools panel, a new tab page or a background script. It answers manifest additions, files and template and changes nothing; then validate the manifest and run extension_dev.
extension_browsers4 of 4 parameters describedFind, install and remove browsers Extension.js launches. detect scans system and managed ones; install downloads hundreds of MB in one blocking call; uninstall never touches a system install.
extension_doctor2 of 2 parameters describedDiagnose a dev session leg by leg, each with its remediation; run it first when an act tool errors unexpectedly. value.capabilities reads WebGPU and isolation; with no projectPath it checks node, the CLI and the template cache.
extension_docs_search3 of 3 parameters describedFind the docs page to cite before answering about a WebExtension API, a manifest key, a permission or a browser difference. It searches the Extension.js and extension.dev docs (free) and answers pages with URLs. Memory is the fallback only when it returns nothing.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.