@extension.dev/mcp 4.1.0 → 4.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/CHANGELOG.md +13 -0
  2. package/README.md +74 -92
  3. package/dist/module.js +1 -1
  4. package/package.json +2 -2
package/CHANGELOG.md CHANGED
@@ -1,5 +1,18 @@
1
1
  # Changelog
2
2
 
3
+ ## 4.1.2
4
+
5
+ README: restore the `@extension.dev/skill` pairing section (hands +
6
+ judgment) now that the skill is public on npm. No code changes.
7
+
8
+ ## 4.1.1
9
+
10
+ README rewritten for the public npm page: Extension.js-style header
11
+ (badges, tagline, quick start), tool table updated to the full 27-tool
12
+ surface (release-promote was missing), and links to private repos or
13
+ npm-restricted packages removed. Package description tool count fixed
14
+ (26 -> 27). No code changes.
15
+
3
16
  ## 4.1.0
4
17
 
5
18
  The MCP now consumes `@extension.dev/core` for all platform-auth logic
package/README.md CHANGED
@@ -1,48 +1,37 @@
1
- [npm-version-image]: https://img.shields.io/npm/v/%40extension.dev%2Fmcp
1
+ [npm-version-image]: https://img.shields.io/npm/v/%40extension.dev%2Fmcp.svg?color=0971fe
2
2
  [npm-version-url]: https://www.npmjs.com/package/@extension.dev/mcp
3
- [action-image]: https://github.com/extensiondev/mcp/actions/workflows/ci.yml/badge.svg?branch=main
4
- [action-url]: https://github.com/extensiondev/mcp/actions
3
+ [npm-downloads-image]: https://img.shields.io/npm/dm/%40extension.dev%2Fmcp.svg?color=0971fe
4
+ [npm-downloads-url]: https://www.npmjs.com/package/@extension.dev/mcp
5
+ [discord-image]: https://img.shields.io/discord/1253608412890271755?label=Discord&logo=discord&style=flat&color=0971fe
6
+ [discord-url]: https://discord.gg/v9h2RgeTSN
5
7
 
6
- [![Version][npm-version-image]][npm-version-url] [![workflow][action-image]][action-url]
8
+ # @extension.dev/mcp [![Version][npm-version-image]][npm-version-url] [![Downloads][npm-downloads-image]][npm-downloads-url] [![Discord][discord-image]][discord-url]
7
9
 
8
- # @extension.dev/mcp
10
+ > Give your AI agent hands for browser extension development. 27 MCP tools that scaffold, run, inspect, debug, and publish cross-browser extensions.
9
11
 
10
- Give your AI agent hands for browser extension development. One command connects Claude Code, Claude Desktop, Cursor, or any MCP client to 26 tools that scaffold, run, inspect, debug, and publish cross-browser extensions:
12
+ <img alt="Logo" align="right" src="https://avatars.githubusercontent.com/u/106714027" width="20%" />
11
13
 
12
14
  ```bash
13
15
  claude mcp add extension-dev npx @extension.dev/mcp
14
16
  ```
15
17
 
16
- Extensions fail silently: content scripts that never inject, panels that never open, permissions that return `undefined` with no error. These tools give agents eyes on the live browser (DOM probes, unified logs from every context, storage access, event replay) so they debug from evidence instead of guessing. Scaffolding draws on the 60+ template catalog of the [extension.dev](https://extension.dev) platform, built on [Extension.js](https://extension.js.org).
18
+ Works with Claude Code, Claude Desktop, Cursor, and any MCP client.
17
19
 
18
- ## What's in this package
20
+ [extension.dev](https://extension.dev) · [Documentation](https://extension.js.org) · [Templates](https://templates.extension.dev) · [Examples](https://github.com/extension-js/examples) · [Discord](https://discord.gg/v9h2RgeTSN)
19
21
 
20
- ```
21
- @extension.dev/mcp
22
- src/ MCP server source (26 tools)
23
- claude/ Claude Code integration (CLAUDE.md, slash commands, rules)
24
- bin/ CLI entrypoint
25
- ```
26
-
27
- **MCP server**: programmatic bridge between AI assistants and the extension.dev platform. Imports from published npm packages:
28
-
29
- - `extension-create`: project scaffolding
30
- - `extension-develop`: build/dev/preview
31
- - `extension-install`: managed browser binaries
22
+ ## Why an MCP server for extensions
32
23
 
33
- **Claude Code integration**: drop-in instructions, slash commands, and rules for Claude Code:
24
+ Extensions fail silently: content scripts that never inject, panels that never open, permissions that return `undefined` with no error. An agent editing files blind will happily "fix" all of them without noticing none of them work.
34
25
 
35
- - `claude/CLAUDE.md`: project-level instructions for any extension project
36
- - `claude/commands/`: slash commands (`/extension`, `/extension-add`, `/extension-debug`, `/extension-publish`)
37
- - `claude/rules/`: rules for extension development, cross-browser compat, and MCP tools
26
+ These tools give agents eyes on the live browser, so they debug from evidence instead of guessing:
38
27
 
39
- **Agent Skill**: the knowledge companion to this server lives in [`@extension.dev/skill`](https://npmjs.com/package/@extension.dev/skill): a portable [Agent Skills](https://agentskills.io)-format skill (SKILL.md + references) covering cross-browser rules, silent-failure gotchas, debugging playbooks, and store publishing. This server gives agents hands; the skill gives them judgment. Pair them:
28
+ - **Scaffold** from the 60+ template catalog behind [templates.extension.dev](https://templates.extension.dev), or add a popup, sidebar, or content script to an existing project
29
+ - **Run** the dev server with HMR in Chrome, Edge, Firefox, or any managed browser binary, no build config
30
+ - **See** the live DOM, unified logs from every extension context, `chrome.storage` contents, and the loaded-extension list
31
+ - **Act**: evaluate code in any context, trigger the action button and commands, reload the extension, replay events
32
+ - **Ship**: validate the manifest cross-browser, build for production, publish a shareable preview, and promote builds to release channels headlessly
40
33
 
41
- ```bash
42
- mkdir -p .claude/skills && cp -R node_modules/@extension.dev/skill/skills/extension-dev .claude/skills/
43
- ```
44
-
45
- Browser-launching tools (`dev`, `start`, `preview`) shell out to the `extension` CLI since they require the full browser launcher infrastructure.
34
+ Built on [Extension.js](https://extension.js.org), the open-source cross-browser extension framework.
46
35
 
47
36
  ## Setup
48
37
 
@@ -52,7 +41,7 @@ Browser-launching tools (`dev`, `start`, `preview`) shell out to the `extension`
52
41
  claude mcp add extension-dev npx @extension.dev/mcp
53
42
  ```
54
43
 
55
- ### Claude Desktop / .mcp.json
44
+ ### Claude Desktop / `.mcp.json`
56
45
 
57
46
  ```json
58
47
  {
@@ -65,79 +54,72 @@ claude mcp add extension-dev npx @extension.dev/mcp
65
54
  }
66
55
  ```
67
56
 
68
- ### Claude Code integration (manual)
57
+ ### Pair with the skill
69
58
 
70
- Copy the Claude Code rules and commands into any extension project:
59
+ This server gives agents hands; [`@extension.dev/skill`](https://www.npmjs.com/package/@extension.dev/skill) gives them judgment: the cross-browser rules, silent-failure gotchas, debugging playbooks, and store checklist, packaged in the open [Agent Skills](https://agentskills.io) format. With both installed, agents know to verify against the live browser instead of guessing, and these tools make that a one-call operation.
71
60
 
72
61
  ```bash
73
- # Rules (how Claude understands your project)
74
- cp node_modules/@extension.dev/mcp/claude/CLAUDE.md ~/my-extension/.claude/CLAUDE.md
75
-
76
- # Slash commands
77
- mkdir -p ~/my-extension/.claude/commands
78
- cp node_modules/@extension.dev/mcp/claude/commands/*.md ~/my-extension/.claude/commands/
62
+ npm i -D @extension.dev/skill
63
+ mkdir -p .claude/skills && cp -R node_modules/@extension.dev/skill/skills/extension-dev .claude/skills/
79
64
  ```
80
65
 
81
- ## Tools
66
+ ### Claude Code project integration
82
67
 
83
- | Tier | Tool | Integration | Description |
84
- | ---- | ------------------------------- | ------------------------------- | --------------------------------- |
85
- | 1 | `extension_create` | `extensionCreate()` | Scaffold from a template |
86
- | 1 | `extension_list_templates` | native | Browse 60+ templates |
87
- | 1 | `extension_build` | `extensionBuild()` | Build for production |
88
- | 1 | `extension_dev` | CLI spawn | Dev server with HMR |
89
- | 1 | `extension_start` | CLI spawn | Build + preview |
90
- | 1 | `extension_preview` | CLI spawn | Preview production build |
91
- | 2 | `extension_get_template_source` | native | Read template source files |
92
- | 2 | `extension_manifest_validate` | native | Cross-browser manifest validation |
93
- | 2 | `extension_inspect` | native | Build output analysis |
94
- | 2 | `extension_source_inspect` | CDP WebSocket | Live DOM inspection |
95
- | 2 | `extension_dom_inspect` | agent bridge | CDP-free DOM snapshot |
96
- | 2 | `extension_list_extensions` | CDP WebSocket | List loaded extensions (Chromium) |
97
- | 2 | `extension_logs` | agent bridge | Stream logs from every context |
98
- | 2 | `extension_wait` | native | Poll ready.json contract |
99
- | 2 | `extension_add_feature` | native | Add sidebar/popup/content script |
100
- | act | `extension_eval` | agent bridge | Eval in a context (`--allow-eval`) |
101
- | act | `extension_storage` | agent bridge | Read/write `chrome.storage` |
102
- | act | `extension_reload` | agent bridge | Reload extension or tab |
103
- | act | `extension_open` | agent bridge | Open surface / trigger `action`,`command` |
104
- | 3 | `extension_install_browser` | `extensionInstall()` | Install managed browser |
105
- | 3 | `extension_list_browsers` | `getManagedBrowsersCacheRoot()` | List managed browsers |
106
- | 3 | `extension_detect_browsers` | native | System browser detection |
107
- | auth | `extension_login` | platform | GitHub device-code → stored token |
108
- | auth | `extension_whoami` | native | Show stored login (no token) |
109
- | auth | `extension_logout` | native | Remove stored credentials |
110
- | auth | `extension_publish` | platform | Publish to extension.dev (token) |
111
-
112
- ## Development
68
+ The package ships drop-in instructions, slash commands, and rules for extension projects:
113
69
 
114
70
  ```bash
115
- pnpm install
116
- pnpm compile # Build with rslib
117
- pnpm test # Run tests
118
- pnpm start # Start MCP server
119
- ```
120
-
121
- ### Publishing
71
+ # Rules (how Claude understands your project)
72
+ cp node_modules/@extension.dev/mcp/claude/CLAUDE.md ~/my-extension/.claude/CLAUDE.md
122
73
 
123
- ```bash
124
- NPM_TOKEN=<token> pnpm publish
74
+ # Slash commands (/extension, /extension-add, /extension-debug, /extension-publish)
75
+ mkdir -p ~/my-extension/.claude/commands
76
+ cp node_modules/@extension.dev/mcp/claude/commands/*.md ~/my-extension/.claude/commands/
125
77
  ```
126
78
 
127
- Uses `prepublishOnly` to run tests and compile before publishing.
128
-
129
- ## The extension.dev open source stack
130
-
131
- | Package | Use it to |
132
- | --- | --- |
133
- | [`@extension.dev/skill`](https://github.com/extensiondev/skill) | Teach agents the cross-browser rules and silent-failure gotchas |
134
- | [`@extension.dev/deploy`](https://github.com/extensiondev/deploy) | Ship to Chrome, Firefox, and Edge stores from CI |
135
- | [`@extension.dev/artifact-integrity`](https://github.com/extensiondev/artifact-integrity) | Gate releases on artifact verification |
136
- | [`@extension.dev/compiler`](https://github.com/extensiondev/compiler) | Build extensions in the browser with esbuild-wasm |
137
- | [`@extension.dev/core`](https://github.com/extensiondev/core) | Authenticate and publish to the extension.dev platform |
79
+ ## Tools
138
80
 
139
- All of it rides on [Extension.js](https://github.com/extension-js/extension.js), the open-source cross-browser extension framework.
81
+ | Tier | Tool | Description |
82
+ | ---- | ---- | ----------- |
83
+ | build | `extension_create` | Scaffold from a template |
84
+ | build | `extension_list_templates` | Browse 60+ templates |
85
+ | build | `extension_get_template_source` | Read template source files |
86
+ | build | `extension_add_feature` | Add sidebar/popup/content script |
87
+ | build | `extension_build` | Build for production |
88
+ | run | `extension_dev` | Dev server with HMR |
89
+ | run | `extension_start` | Build + preview |
90
+ | run | `extension_preview` | Preview the production build |
91
+ | run | `extension_wait` | Poll the dev-server ready contract |
92
+ | see | `extension_manifest_validate` | Cross-browser manifest validation |
93
+ | see | `extension_inspect` | Build output analysis |
94
+ | see | `extension_source_inspect` | Live DOM inspection (CDP) |
95
+ | see | `extension_dom_inspect` | CDP-free DOM snapshot |
96
+ | see | `extension_list_extensions` | List loaded extensions (Chromium) |
97
+ | see | `extension_logs` | Stream logs from every context |
98
+ | act | `extension_eval` | Evaluate in a context (`--allow-eval`) |
99
+ | act | `extension_storage` | Read/write `chrome.storage` |
100
+ | act | `extension_reload` | Reload extension or tab |
101
+ | act | `extension_open` | Open a surface / trigger `action`, `command` |
102
+ | browsers | `extension_install_browser` | Install a managed browser binary |
103
+ | browsers | `extension_list_browsers` | List managed browsers |
104
+ | browsers | `extension_detect_browsers` | Detect system browsers |
105
+ | platform | `extension_login` | GitHub device-code login, stored token |
106
+ | platform | `extension_whoami` | Show the stored login (never the token) |
107
+ | platform | `extension_logout` | Remove stored credentials |
108
+ | platform | `extension_publish` | Publish a shareable preview to extension.dev |
109
+ | platform | `extension_release_promote` | Promote a build to a release channel, headless |
110
+
111
+ Browser-launching tools (`dev`, `start`, `preview`) shell out to the `extension` CLI; everything else runs in-process.
112
+
113
+ ## From preview to store
114
+
115
+ The four 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. To automate store submission itself (Chrome Web Store, Edge Add-ons, Firefox AMO), pair with [`@extension.dev/deploy`](https://www.npmjs.com/package/@extension.dev/deploy).
116
+
117
+ ## Community
118
+
119
+ - Join the [Discord](https://discord.gg/v9h2RgeTSN) for help and feedback
120
+ - Browse production-ready [examples](https://github.com/extension-js/examples)
121
+ - Report Extension.js framework issues on [GitHub](https://github.com/extension-js/extension.js/issues)
140
122
 
141
123
  ## License
142
124
 
143
- MIT
125
+ MIT (c) Cezar Augusto and the Extension.js authors.
package/dist/module.js CHANGED
@@ -178,7 +178,7 @@ __webpack_require__.d(whoami_namespaceObject, {
178
178
  schema: ()=>whoami_schema
179
179
  });
180
180
  var package_namespaceObject = {
181
- rE: "4.1.0"
181
+ rE: "4.1.2"
182
182
  };
183
183
  const schema = {
184
184
  name: "extension_create",
package/package.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "name": "@extension.dev/mcp",
3
3
  "type": "module",
4
- "version": "4.1.0",
5
- "description": "MCP server that lets AI agents build, run, inspect, and publish browser extensions. 26 tools for scaffolding, live DOM inspection, log streaming, and store-ready builds across Chrome, Edge, and Firefox.",
4
+ "version": "4.1.2",
5
+ "description": "MCP server that lets AI agents build, run, inspect, and publish browser extensions. 27 tools for scaffolding, live DOM inspection, log streaming, and store-ready builds across Chrome, Edge, and Firefox.",
6
6
  "license": "MIT",
7
7
  "author": {
8
8
  "name": "Cezar Augusto",