Firefox Addons Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Search Firefox browser extensions on AMO. No key required.

VerifiedSTDIODesktop onlyWeb Search & Scraping

Overview

AI-generated overview

A local MCP server that lets an assistant search Firefox browser extensions on AMO (addons.mozilla.org) without an API key.

What you can do
  • Search Firefox browser extensions on the AMO add-ons site.
  • No tool list is published, so the exact search parameters and result fields are not documented here.
When to use it
Useful when you want an assistant to look up Firefox extensions or add-ons by name or topic while researching tools, without leaving the chat.
Requirements
Runs as a local stdio process installed from the npm package firefox-addons-mcp, so Node.js and npm are needed. No API key, environment variables or headers are declared. Network access to the AMO site is implied by the search function.
Before you install
No credentials are requested. Search queries are sent to Mozilla's add-ons site, so treat them as visible to that third party. The server only appears to search; no install or write actions are described.

Installation

In SourceWeft

  1. Open Firefox Addons Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.