Bangun, jalankan, uji, dan kirimkan browser extension ke toko Chrome, Firefox, Edge, dan Safari langsung dari AI client Anda.
Juga dikenal sebagai extensiondev/mcp, @extension.dev/mcp
- Stars
- 0
- Tools
- —
- Unduhan, 30 hari
- 2.651
- Versi terbaru
- 10.22.0
- Commit terakhir
- 15 Nov 2026
- Lisensi
- Apache-2.0
Apa itu extension.dev MCP?
extension.dev adalah MCP server. Bangun, jalankan, uji, dan kirimkan browser extension ke toko Chrome, Firefox, Edge, dan Safari langsung dari AI client Anda.
Ringkasan dibuat dari README proyek
Tentang extension.dev MCP server
Mengembangkan dan mendistribusikan browser extension di berbagai platform adalah hal yang dimungkinkan oleh MCP server ini bagi para developer yang menggunakan AI client. Server ini menyediakan jembatan antara AI agent dan ekosistem browser, memungkinkan pembuatan, pengujian, hingga pengiriman extension ke toko Chrome, Firefox, Edge, dan Safari. Server ini beroperasi dalam dua mode: local tools yang menjalankan framework Extension.js di mesin Anda, dan platform tools yang menangani proses deployment melalui extension.dev.
Pengguna dapat melakukan scaffolding proyek baru dari lebih dari 50 template, menjalankan sesi pengembangan dengan hot module replacement, dan menggunakan tool extension_assert untuk memverifikasi bahwa content script berjalan dengan benar. Meskipun local tools tidak memerlukan akun, fitur platform seperti extension_submit memerlukan login satu kali untuk mengelola kredensial toko. Server ini menjamin keamanan dengan mewajibkan persetujuan manusia untuk setiap pengiriman atau promosi nyata, guna mencegah agent mempublikasikan kode tanpa izin eksplisit.
Apa yang bisa Anda lakukan dengannya
- 1Scaffold dan jalankan extensionMinta AI agent Anda untuk membuat extension baru dari sebuah template dan meluncurkan sesi pengembangan live di browser tertentu.
- 2Verifikasi fungsionalitas extensionBiarkan agent menguji apakah content script telah berhasil diinjeksi ke dalam halaman web menggunakan automated assertions.
- 3Kirim ke browser storesInstruksikan agent untuk melakukan dry run submission ke Chrome Web Store dan Firefox Add-ons guna memeriksa apakah ada persyaratan yang belum terpenuhi.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal extension.dev MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal extension.dev MCP di Claude Code
$ claude mcp add mcp -- npx -y @extension.dev/mcpInstal extension.dev MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@extension.dev/mcp"
]
}
}
}Instal extension.dev MCP di VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@extension.dev/mcp"
]
}
}
}Instal extension.dev MCP di VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@extension.dev/mcp"]}'Instal extension.dev MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@extension.dev/mcp"
]
}
}
}Instal extension.dev MCP di Codex
$ codex mcp add mcp -- npx -y @extension.dev/mcpInstal extension.dev MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@extension.dev/mcp"]
Instal extension.dev MCP di Gemini CLI
$ gemini mcp add -s user mcp npx -- -y @extension.dev/mcpInstal extension.dev MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@extension.dev/mcp"
]
}
}
}Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauextensiondev/mcp is public and reachablegithub.com/extensiondev/mcp ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernya@extension.dev/mcp names extensiondev/mcp as sourcenpmjs.com/package/@extension.dev/mcp ↗Lolos
- Provenance build (atestasi Sigstore)No build attestation published for this releaseTidak diperiksa
- Lisensi open source (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-11-14github.com/extensiondev/mcp ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerNo popular package one edit away from @extension.dev/mcpLolos
- Tidak ada advisory kritis pada paket atau dependensinya399 resolved dependencies checked; no critical advisoryosv.dev ↗Lolos
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPTidak diperiksa
README
Lihat di GitHub@extension.dev/mcp

Ship browser extensions to four stores from your AI agent: create, run, test and submit to Chrome, Firefox, Edge and Safari.
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.
Docs · Tools · Skill · Changelog · Troubleshooting · Discord
Install
claude mcp add extension-dev -- npx -y @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": [
"-y",
"@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.
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 -y @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: a shared preview uploads the build it just made, a submit sends the build to extension.dev, a login stores a project-scoped token locally.
--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, 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; platform lists only those |
--no-ship |
EXTENSION_DEV_NO_SHIP=1 |
off | Refuses publish, promote, a real submit, 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 and reads builds, releases and approvals. 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. Addplatformto--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.
Pertanyaan tentang extension.dev MCP
Bagaimana cara menambahkan extension.dev MCP ke Claude Code?
Jalankan claude mcp add mcp -- npx -y @extension.dev/mcp di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan extension.dev MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Apakah saya bisa mengirimkan extension ke beberapa toko sekaligus?
Ya, Anda dapat mengirimkan build ke Chrome Web Store, Firefox Add-ons, Microsoft Edge Add-ons, dan Apple App Store.
Apakah saya butuh Mac untuk mempublikasikan ke Safari App Store?
Tidak, jalur Safari tidak memerlukan Mac karena platform melakukan signing dengan kunci yang tersimpan terenkripsi di dalam platform.
Apakah server akan mengirimkan extension secara otomatis?
Tidak, server memerlukan persetujuan dari pemilik workspace manusia untuk setiap pengiriman atau promosi nyata di extension.dev.
Bagaimana cara menggunakan platform tools?
Anda harus mengaktifkan fitur platform dan login satu kali melalui device code di extension.dev/device.
