extension.dev Browser Extensions
Build, run, debug, test and ship Chrome, Firefox, Edge and Safari extensions from your AI agent.
Barındırılan MCP Sunucusu
npx add-mcp 'https://mcp.extension.dev/mcp'Claude Code, Codex, Cursor ve daha fazlasına kurulur
Dokümantasyon
extension.dev MCP

Build, run, debug, test and ship Chrome, Firefox, Edge and Safari extensions from your AI agent.
Extension.js is the framework you run. extension.dev is where it ships. This server covers both: the local tools run Extension.js on your machine, and the platform lane takes the build the rest of the way to the stores.
These tools build, run, inspect and ship one extension across Chrome, Edge, Firefox and Safari.
Docs · Tools · Skill · Changelog · Troubleshooting · Discord
Install
claude mcp add extension-dev -- npx @extension.dev/mcp --features=local,platform
Or install the extension-dev plugin, the MCP server pinned to one published version plus the browser-extension skill, in one step:
/plugin marketplace add extensiondev/skill
/plugin install extension-dev@extensiondev
Other clients take the same server as .mcp.json; every client's block, with a local-only form, is on Install in your client.
{
"mcpServers": {
"extension-dev": {
"command": "npx",
"args": [
"@extension.dev/mcp",
"--features=local,platform"
]
}
}
}
The local tools need no account; the platform tools, on with --features=local,platform, ask for a login the first time they reach extension.dev. Add extras (--features=local,platform,extras) to list extension_theme_verify and extension_network.
Your first prompt
Create a Chrome and Firefox extension that highlights external links, run it, and prove the content script injected.
The agent scaffolds from a template, starts the dev session, a browser opens with the extension loaded, and extension_assert answers with a verdict instead of a guess. Then:
Submit this build to the Chrome Web Store and Firefox Add-ons as a dry run and tell me what is missing.
Ship to four stores
extension_submit sends a built extension into review at the four stores through extension.dev, which holds your store credentials. It defaults to a dry run, and a real submit waits for a workspace owner to approve that exact act on extension.dev: the server never submits or publishes on its own. Reaching the App Store needs no Mac: the Safari lane signs with keys the platform holds encrypted at rest, under the same approval.
The platform tools need a login once. You approve a code at extension.dev/device; the project-scoped token stays on this machine, is never returned to the agent, and lives at most 7 days. No project yet? Request access at extension.dev.
npx @extension.dev/mcp login --project <workspace>/<project>
Details under Platform tools.
Watch it work
What it does
Extensions fail silently: content scripts that never inject, panels that never open. These tools give the agent eyes on the live browser.
- Ship: validate the manifest cross-browser, build, share a preview, promote, submit
- Scaffold from 50+ templates, or add a popup, sidebar or content script
- Run the dev server with HMR in every browser below
- See the live DOM, logs from every context,
chrome.storage, the loaded extensions - Act: evaluate code in any context, trigger the action button and commands, reload
- Test:
extension_assertanswerspass,failorinconclusive, the last naming the evidence that would settle it
Built on Extension.js, the open source framework extension.dev sponsors. Every engine command runs the project's own extension when the project has one, else the version this server pins (Engine pinning).
Requirements
- Node 22.12 or later.
- A Chromium or Firefox browser, or
extension_browsersinstalls one. - macOS with Xcode only for a local Safari session; the App Store lane needs no Mac.
- An extension.dev login only for the platform tools.
Browsers
extension_dev opens the extension in the browser you name. The Chromium family and Firefox get HMR, control, eval, inspect and assert, and so does any Chromium or Gecko binary by path. On macOS with Xcode, browser: "safari" builds the app, opens it, reloads it on every save and streams its logs; no eval, no extension_inspect, limits under Safari.
Security
- Local by default. Every local tool runs Extension.js on your machine. The control channel (
extension_storage,extension_reload,extension_open,extension_dom_snapshot) is same machine, same user, on unlessextension_devis called withallowControl: false. - The eval gate.
extension_evalstays off untilextension_devis called withallowEval: true.extension_elementclicks, fills, reads and waits for one element, and sends trusted mouse and keyboard input (move, press, release, type, key, scroll) that pages read asisTrusted: true, over the debug port with no gate, since it runs no caller code. A session never grows a gate on a second call: callextension_devagain withreplace: true. - What leaves the machine. Nothing until you ask. The local tools send nothing to extension.dev. A platform tool is answered by extension.dev's hosted lane at
mcp.extension.dev: this server exchanges the stored login at www.extension.dev for a credential that lasts ten minutes and sends the lane that credential, the tool's arguments and the project ref, never the login, a file path or theapioverride. A store check or a listing sync also sends what it read from the project (the text ofSTORE.md, the icon and screenshot sizes and digests, the git HEAD); a listing image is uploaded to www.extension.dev only when the listing write needs it. A shared preview uploads the build it just made, a project created from a folder uploads that folder, a capture sync uploads the capture files, and a login stores a project-scoped token locally. Signing in and out, a create and its device approval, a preview, a build download, a capture sync and a share create run on this machine.--no-shiprefuses every call that puts something in front of other people. - Approvals stay human. A real submit, a channel promotion and a share revoke answer
approval-required; a workspace owner approves the exact act on extension.dev, the call is repeated with the returnedapprovalId, and the server never approves anything itself.extension_submit_checkcarries the reads and the asks underreadOnlyHint: true;extension_submitcarries the act. - Untrusted text from pages comes back inside an
<untrusted-data-ID>fence, and every tool carries MCP annotations.
Telemetry
extension_create sends one draft_seeded event to us.i.posthog.com after a scaffold (template slug, source and commit, a random per-process id, never a path or a name), and the platform tools send a per-install id header. EXTENSION_DEV_NO_TELEMETRY=1 or DO_NOT_TRACK=1 stops both (payload).
Hosted server
https://mcp.extension.dev/mcp serves the platform reads and promotions over Streamable HTTP: a client connects with the URL alone, signs in at www.extension.dev through OAuth, and gets extension_workspace, extension_project_create, extension_builds (reads), extension_builds_act, extension_release_status, extension_release_promote and extension_auth (status only). Local tools, publish, submit and share links stay on the stdio server.
claude mcp add --transport http extension-dev https://mcp.extension.dev/mcp
Flags
| Flag | Environment variable | Default | Effect |
|---|---|---|---|
--features=<groups> | EXTENSION_DEV_FEATURES | local | local,platform adds the platform group; extras, off unless named, adds the theme check and the network stubs; a group named alone lists only its tools |
--no-ship | EXTENSION_DEV_NO_SHIP=1 | off | Refuses publish, promote, a real submit, a store act (the listing sync included), a shared preview, a share create or revoke |
--project <workspace>/<project> | EXTENSION_DEV_PROJECT | unset | Refuses any call that names another project |
| none | EXTENSION_DEV_TOKEN | unset | An access token in place of the device login, for CI |
| none | EXTENSION_DEV_NO_AUTO_OPEN=1 | off | Never opens the approval page in the default browser |
| none | EXTENSION_DEV_NO_TELEMETRY=1 or DO_NOT_TRACK=1 | off | Turns off the draft_seeded event and the per-install id header |
| none | EXTENSION_MCP_CLI_VERSION | this release's pin | The Extension.js version run when the project has no engine of its own |
| none | EXTENSION_MCP_ENGINE_DIR or EXTENSION_MCP_ENGINE_BIN | unset | Runs every engine command from a compiled Extension.js checkout or one bin file |
login, logout, whoami and release promote run headless; see Server flags.
Tools
The local group scaffolds, builds, runs, inspects, drives and asserts; the platform group logs in, shares, promotes, submits, reads builds, releases and approvals, and runs a published build with extension_try; the extras group, off unless named, verifies a Chrome theme and stubs network responses. Every tool has a page under the tool reference, generated from the schema the server registers, with its inputs, whether it only reads, the gate it needs and a prompt that reaches for it.
Pair with the skill
This server gives agents hands; @extension.dev/skill gives them judgment: cross-browser rules, silent-failure gotchas, debugging playbooks and the store checklist.
npx skills add extensiondev/skill
Troubleshooting
Every refusal carries a hint naming the next call. The five most common:
E_TOOL_DISABLED: the tool's group is off, or the call reaches outside this machine in no-ship mode. Add the group the hint names (platformorextras) to--features, or drop--no-ship, in the client's config, then call again.approval-required: have a workspace owner approve the act at the link, then repeat the call with the same arguments and the returnedapprovalId.E_AUTH_REQUIREDorE_AUTH_EXPIRED: the login lives at most 7 days. Runextension_auth(action: "login",project: "<workspace>/<project>"), then call again.E_NO_SESSION: nothing is running. Startextension_dev, thenextension_waitfor ready.extension_evalrefused: the session started without the gate. Callextension_devagain withallowEval: trueandreplace: true; reads need no eval.
extension_doctor names the broken leg of a session. After a new version lands a tool may answer E_SERVER_STALE: run /mcp, pick extension-dev, and call again. More under When it fails.
Community
Help and feedback on Discord; templates at templates.extension.dev; Extension.js framework issues at extension-js/extension.js.
License
Apache-2.0 (c) 2026 Cezar Augusto and the extension.dev collaborators. See LICENSE.
