chore: add mcp registration artifacts - #196
Merged
Merged
Conversation
hbenl
approved these changes
Sep 21, 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.
This PR aims to help with the integration of firefox-devtools-mcp with MCP registries and third-party tools.
First we add cursor and gemini entry points, so that users can directly add the mcp using the built-in tools for those ecosystems.
Then we add a MCP registry publish step. This targets the official/sanctioned repository of MCPs at https://registry.modelcontextprotocol.io/ . Many other MCP registries derive from this one, so getting listed there already should provide more exposure.
The setup and tasks are heavily based on what is done for chrome-devtools-mcp, but it will require a first release with the
mcpNamein the package.json to work. It's both triggered automatically from thereleaseaction, but can also be triggered independently (I suspect we might have issues in the beginning).