Closed Bug 2027194 Opened 6 months ago Closed 4 months ago

Release mozilla/firefox-devtools-mcp on npm

Categories

(Developer Infrastructure :: Firefox MCP, task, P3)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jdescottes, Assigned: jdescottes)

References

(Blocks 1 open bug)

Details

At the moment the npm packages for firefox-devtools-mcp are either published under freema or padenot. We should release an official one under mozilla.

Before doing that we should cleanup the repository, review the documentation and security.

Priority: -- → P3
Blocks: 2027212
Blocks: 2027214
Component: AI for Development → Firefox MCP
Depends on: 2018245
Depends on: 2032934
Depends on: 2034061
Depends on: 2034794
Assignee: nobody → jdescottes
Status: NEW → ASSIGNED
Depends on: 2037053

Mack: you might have seen the discussion on Slack, but we are trying to release the package from https://github.com/mozilla/firefox-devtools-mcp under the @mozilla handle, and I'm following https://mozilla-hub.atlassian.net/wiki/spaces/SECENGOPS/pages/50102398/How+to+request+a+Mozilla+NPM+Account .

However I'm stuck at

Request the npmjs account be granted access to an existing (or new) team on NPM by opening a Jira issue for project “ITSEC” with subject “NPM Access Request”. (The request should then show in the table below.)

Because the ITSEC project no longer exists.

Frida mentioned you might be able to help here.
Do you have suggestions on how to move forward here?

Flags: needinfo?(mlarsonweber)
Depends on: 2037806

https://www.npmjs.com/package/@mozilla/firefox-devtools-mcp

First release done.

Clearing the ni, thanks for helping out here Mack!

Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Flags: needinfo?(mlarsonweber)
Resolution: --- → FIXED
Blocks: 2053705
You need to log in before you can comment on or make changes to this bug.