@extension.dev/mcp 6.2.0 → 6.4.0

package/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
       "name": "extension-mcp",
       "source": "./",
       "description": "MCP tools for browser extension development: scaffold from 60+ templates, run the dev server with HMR, inspect the live DOM and logs, and publish store-ready builds for Chrome, Edge, and Firefox.",
-      "version": "6.2.0",
+      "version": "6.4.0",
       "category": "development",
       "author": {
         "name": "Cezar Augusto"

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "extension-mcp",
   "description": "MCP tools for browser extension development: scaffold from 60+ templates, run the dev server with HMR, inspect the live DOM and logs, and publish store-ready builds for Chrome, Edge, and Firefox. Ships /extension, /extension-add, /extension-debug, and /extension-publish commands.",
-  "version": "6.2.0",
+  "version": "6.4.0",
   "author": {
     "name": "Cezar Augusto",
     "email": "hello@extension.dev",

package/CHANGELOG.md

@@ -1,5 +1,108 @@
 # Changelog
 
+## 6.4.0
+
+A build on your machine can now become a link someone else can open, and the
+bundled Live Preview carrier finally allows the origin that opens it.
+
+### Added
+
+- **`extension_preview_web` renders an in-progress build in the web emulator.**
+  It builds the project, points `preview.extension.dev` at `dist/<browser>` over
+  the dev-only `preview://build` scheme, and returns a deep link plus a
+  loadability check against the preview dev server. `surface:"inspect"` renders
+  in `inspect.extension.dev` instead, for fixture and forensic work. This tool
+  reaches npm for the first time in this release.
+- **`share:true` uploads the build you just made.** It POSTs the resolved
+  `dist/<browser>` to the platform's artifact store and returns a public
+  `preview.extension.dev` link that renders those exact bytes, for a recipient
+  with no install, no sign-in, and no dev server. That link also serves the
+  whole build as a downloadable zip (`share.zipUrl`), so sharing it hands over
+  the built code. `share.serves` reports `uploaded-local-build`. Sharing needs a
+  token scoped to an existing extension.dev workspace and project
+  (`extension_login` or `EXTENSION_DEV_TOKEN`, valid up to 7 days), degrades to
+  a login hint when there is no token, and never fails the local preview.
+  `share` also returns `expiresAt` and `revokeUrl`: shared builds expire, and
+  `DELETE`ing `revokeUrl` with the same token kills the link for good, which is
+  the part a TTL alone cannot do when a link reaches the wrong person.
+- **A shared link's revoke handle survives losing the tool output.** Revocation
+  is permanent and re-sharing mints a new artifact id, so `share.revokeUrl` is
+  the only handle that can ever pull a given link, and losing it used to mean
+  waiting out the 30-day TTL. Every successful share is now appended to
+  `.extension.dev/shared-previews.json` in the project, next to the carrier's
+  own project-local state and gitignored the same way: one entry per share with
+  `previewUrl`, `artifactId`, `revokeUrl`, `expiresAt`, `zipUrl` and the time it
+  was shared. The list is only ever appended to, an unreadable file is kept
+  aside instead of overwritten, a write that fails never fails the share, and
+  the returned `share.record` and note say where the handle went. If the entry
+  cannot be added to `.gitignore`, the response says so.
+- **`extension_theme_verify` settles a Chrome theme manifest before it ships.**
+  It derives every color current Chrome would paint from the manifest with a
+  transcribed Chromium resolver and reports the divergence class of any problem:
+  D1 fabrication, D3 parity gap, D4 acceptance gap (keys Chrome silently
+  discards, such as dead legacy keys, incognito keys, unknown keys and
+  out-of-range values). The legs that need a real browser come back as
+  `needsAttended` with a pointer to the attended harnesses, never as passed.
+
+### Fixed
+
+- **The bundled Live Preview carrier reaches `preview.extension.dev`.** This
+  package ships the carrier prebuilt and `extension_dev` materializes it into
+  the project's `./extensions`, so the carrier only changes when the package
+  does. Its `externally_connectable` allowlist had no web preview origin, so a
+  page on `preview.extension.dev` could not talk to the carrier at all. 6.3.0
+  shipped without the fix.
+- The carrier popup requested `icons/icon.png` while the carrier build ships
+  `images/icon.png`, so the popup icon was broken.
+
+### Changed
+
+- `extension_preview_web` takes no `channel` argument. It renders the build on
+  disk, not a promoted CI build. `extension_publish` and
+  `extension_release_promote` are unchanged and remain the path for released,
+  channel-scoped builds.
+- The server advertises 35 tools, up from 33.
+
+## 6.3.0
+
+Private projects stop reading as empty, and the links this server hands back
+stop being login-only.
+
+### Fixed
+
+- **Registry reads work for PRIVATE projects.** `extension_release_list`,
+  `extension_store_status`, `extension_deploy` and `extension_publish` read the
+  project's state from `registry.extension.land`, which answers 401 for a
+  private project. That 401 was reported as "no registry data", so a project the
+  operator owns and is logged into looked like it had no builds at all. A 401 or
+  403 now mints a short-lived read token and retries once. Public projects are
+  untouched: still one request, still no call to the platform.
+- The stored login token is never used as the `?t=` URL parameter even though it
+  would verify. It is long-lived, and a credential in a query string is kept by
+  every proxy and access log on the path, so it is traded for a ten-minute token
+  first. Requires the bearer path on `POST /api/access-grant`.
+
+### Added
+
+- **Public build links.** `extension_release_list` returns a `publicUrl` for
+  every channel and build plus a `publicProjectUrl`, and
+  `extension_release_promote` returns `publicChannelUrl` and `publicBuildUrl`.
+  Every link these tools returned before pointed at the console, which requires
+  a login and workspace membership, so it was a dead end for the teammate or
+  reviewer the operator wanted to send it to. The public pages carry the
+  per-browser downloads, the run-locally and integrity dialogs, and what's new.
+  For a private project the response says plainly that an outside recipient
+  still needs a share link from `extension_publish`.
+- `api` is accepted by `extension_release_list` and `extension_store_status`,
+  matching the other hosted-facing tools. It picks the platform the read token
+  is minted against and the origin the returned links point at.
+
+### Changed
+
+- Depends on `@extension.dev/urls` `^0.3.0` for the new `userland` origin and
+  its whole-URL builders, so a build link this server returns cannot drift from
+  the routes the viewer serves.
+
 ## 6.2.0
 
 The URL layer stops being a copy. This server used to carry byte-identical

package/README.md

@@ -5,9 +5,11 @@
 [discord-image]: https://img.shields.io/discord/1253608412890271755?label=Discord&logo=discord&style=flat&color=26FFB8
 [discord-url]: https://discord.gg/v9h2RgeTSN
 
+<img alt="@extension.dev/mcp" src="https://media.extension.land/brand/repos/mcp/github-banner.png" />
+
 # @extension.dev/mcp [![Version][npm-version-image]][npm-version-url] [![Downloads][npm-downloads-image]][npm-downloads-url] [![Discord][discord-image]][discord-url]
 
-> Give your AI agent hands for browser extension development. 33 MCP tools that scaffold, run, inspect, debug, and publish cross-browser extensions.
+> Give your AI agent hands for browser extension development. 35 MCP tools that scaffold, run, inspect, debug, and publish cross-browser extensions.
 
 <img alt="Logo" align="right" src="https://media.extension.land/brand/extension-dev/logo-dock.png" width="20.7%" />
 
@@ -118,6 +120,7 @@ cp node_modules/@extension.dev/mcp/claude/commands/*.md ~/my-extension/.claude/c
 | see | `extension_list_extensions` | List loaded extensions (Chromium) |
 | see | `extension_logs` | Stream logs from every context |
 | see | `extension_doctor` | Diagnose the dev session leg by leg (ready contract, ports, token, executor, browser) |
+| see | `extension_theme_verify` | Verify a Chrome theme manifest against the colors Chrome actually paints |
 | act | `extension_eval` | Evaluate in a context (needs `allowEval: true` on `extension_dev`) |
 | act | `extension_storage` | Read/write `chrome.storage` |
 | act | `extension_reload` | Reload extension or tab |
@@ -129,15 +132,22 @@ cp node_modules/@extension.dev/mcp/claude/commands/*.md ~/my-extension/.claude/c
 | platform | `extension_login` | GitHub device-code login, stored token |
 | platform | `extension_whoami` | Show the stored login (never the token) |
 | platform | `extension_logout` | Remove stored credentials |
+| platform | `extension_preview_web` | Render a build in the web emulator, and share it as a link |
 | platform | `extension_publish` | Publish a shareable preview to extension.dev |
 | platform | `extension_release_promote` | Promote a build to a release channel, headless |
 | platform | `extension_deploy` | Submit to the Chrome, Firefox, and Edge stores through extension.dev |
 
 Browser-launching tools (`dev`, `start`, `preview`) shell out to the `extension` CLI, the project's own `node_modules/.bin/extension` when present, otherwise `npx extension@<pinned>` at the version this package is verified against; everything else runs in-process.
 
+## Sharing a build in progress
+
+An unpacked extension is unusually hard to hand to someone: the only way to look at a colleague's work-in-progress has been to take their zip and run untrusted code with real browser permissions on your own machine. `extension_preview_web` with `share: true` uploads the `dist/` it just built and returns a link that renders those exact bytes in the emulator. Whoever opens it installs nothing and signs in to nothing, which is what lets a designer, a PM, or a reviewer into the loop at all. Sharing needs auth (`extension_login` or `EXTENSION_DEV_TOKEN`), the link expires, and `DELETE`ing the returned `revokeUrl` with the same token kills it early. Revocation is permanent and re-sharing mints a new link, so that `revokeUrl` is the only handle to the link you just made; every share is also appended to `.extension.dev/shared-previews.json` in the project (gitignored) so it survives losing the tool output. Without `share`, the tool returns a local-only deep link and uploads nothing.
+
+That is a different job from shipping. Use `share` for the build you are holding right now; use `extension_publish` and `extension_release_promote` below for builds your CI has released.
+
 ## From preview to store
 
-The platform tools connect agents to [extension.dev](https://extension.dev): `extension_login` runs a GitHub device-code flow and stores a project-scoped token locally (never returned to the agent), `extension_publish` turns a build into a shareable preview URL, and `extension_release_promote` promotes a tested build to a release channel from CI or an agent session, no browser required. `extension_deploy` submits a built extension to the Chrome Web Store, Edge Add-ons, and Firefox AMO through extension.dev, which holds your store credentials and dispatches the release from your project's mirror CI, it defaults to a dry run and store credentials are never tool arguments. After a real submission, `extension_store_status` reads the recorded outcome, per-store credential health, and review state from the project's public registry, so agents and CI can answer "was it approved?" without a console visit. Access tokens live at most 7 days; CI pipelines re-mint them from the console's Access tokens page.
+The platform tools connect agents to [extension.dev](https://extension.dev): `extension_login` runs a GitHub device-code flow and stores a project-scoped token locally (never returned to the agent), `extension_publish` turns a build your project has already published into a shareable URL, and `extension_release_promote` promotes a tested build to a release channel from CI or an agent session, no browser required. `extension_deploy` submits a built extension to the Chrome Web Store, Edge Add-ons, and Firefox AMO through extension.dev, which holds your store credentials and dispatches the release from your project's mirror CI, it defaults to a dry run and store credentials are never tool arguments. After a real submission, `extension_store_status` reads the recorded outcome, per-store credential health, and review state from the project's public registry, so agents and CI can answer "was it approved?" without a console visit. Access tokens live at most 7 days; CI pipelines re-mint them from the console's Access tokens page.
 
 ## The extension.dev stack
 

package/bin/extension-mcp.js

@@ -6,6 +6,7 @@
 // ██║ ╚═╝ ██║╚██████╗██║
 // ╚═╝     ╚═╝ ╚═════╝╚═╝
 // Apache License 2.0 (c) 2026 Cezar Augusto and the extension.dev collaborators
+
 import {startServer, runCli} from '../dist/module.js'
 
 const [, , cmd, ...rest] = process.argv