Repository navigation
Bug 2088363 - Publish the package as @mozilla/firefox-mcp and keep publishing @mozilla/firefox-devtools-mcp - #233
Open
juliandescottes wants to merge 9 commits into
Conversation
Set the package name, mcpName and server.json to firefox-mcp, and point the repository links to mozilla/firefox-mcp. Add a firefox-mcp bin next to firefox-devtools-mcp, so npx works for both published package names. Fix the CLI help name, which still used the deprecated unscoped package.
Publish the same dist/ build under the old package name, so that existing npx @mozilla/firefox-devtools-mcp@latest setups keep updating. The compat package has no mcpName, so it makes no MCP Registry claim, and its README points to @mozilla/firefox-mcp. Move the staging logic of the moz publish script to a shared helper. Rename the release tarball to firefox-mcp.
Rename the moz package and its bin to firefox-mcp-moz. The old moz name is not published anymore. Also rename the temporary staging folders of the moz and mcpb scripts.
…fox-mcp Use @mozilla/firefox-mcp@latest in the README examples and in the Gemini extension, which installs from GitHub releases and so must change with the release. Use "Firefox MCP" as the .mcpb display name, rename the bundle to firefox-mcp-<version>.mcpb, and point both manifests to the mozilla/firefox-mcp repository. Rename the setup script title.
Rename the project to Firefox MCP in the README, CONTRIBUTING, the Claude plugin docs, the skill and agent texts, and the user-facing strings of the server. Point the badges and links to mozilla/firefox-mcp and @mozilla/firefox-mcp, and add one README line about the compat package. Keep the plugin ID, the slash commands, the server key and the Matrix room.
… Gemini extension New setups get tool names like mcp__firefox__navigate_page instead of mcp__firefox-devtools__navigate_page. Existing manual configs keep their own key. The Gemini extension installs from GitHub releases, so its key changes with the release. Gemini users get the new tool names on their next extension update. The setup script writes the new key too.
…efox-mcp Gemini CLI updates a renamed extension in place on the next "gemini extensions update": it moves the install folder to the new name and keeps the enabled state and settings. Claude Desktop users install each .mcpb by hand, as for every release.
The main package only ships the firefox-mcp bin, and the compat package only ships firefox-devtools-mcp. With the same two bins in both, a global install of one package failed with EEXIST when the other was already installed. npx runs a package's only bin whatever its name, so both "npx @mozilla/firefox-mcp" and "npx @mozilla/firefox-devtools-mcp" still work.
The publish job pushes three packages in a row. If one step failed, for example the compat package on a trusted publisher error, a rerun failed right away on the main package, whose version was already out. Each step now skips a version that is already on npm, so a rerun with the release tag finishes the publish with provenance and then registers the version.
juliandescottes
marked this pull request as ready for review
November 4, 2026 12:56
Collaborator
Author
|
This can be reviewed, but I will only merge it once I'm ready to release & rename everything |
hbenl
approved these changes
Nov 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of the rename to firefox-mcp (meta Bug 2082802). This is the release part, to ship as 0.11.0. Do not merge before release day: it needs the repo rename and the npm setup below.
Package:
Compat package:
Moz package:
Not in this PR: the Claude plugin manifests (Bug 2088365). Claude Code reads them from the main branch, so they land after @mozilla/firefox-mcp is on npm.
Before merging: