Bugzilla MCP server
Commit Nov 13, 2026Allows an AI client to search, triage, and manage Firefox/Mozilla bugs through the Bugzilla REST API.
Also known as kud/mcp-bugzilla
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 13, 2026
- License
- MIT
What is Bugzilla MCP?
Bugzilla allows an AI client to search, triage, and manage Firefox/Mozilla bugs through the Bugzilla REST API.
Summary generated from the project's README
About Bugzilla MCP server
Managing Firefox and Mozilla bug reports through an AI client is possible with this server. It connects to the Bugzilla REST API to allow users to search, triage, and organize issues. Developers can use it locally via npx by configuring their MCP client, such as Claude Desktop. The server provides read-only access by default, but users can enable write capabilities by providing an MCP_BUGZILLA_API_KEY in their environment variables.
This tool offers seventeen distinct functions organized into six functional areas. You can perform deep searches using quicksearch or specific filters like product, component, and severity. The server handles complex tasks such as fetching field-change history, managing comment threads, and uploading base64-encoded attachments. It also supports administrative actions like creating new bugs, updating statuses, adding CC members, and marking duplicates. For those using self-hosted Bugzilla instances, the MCP_BUGZILLA_BASE_URL variable allows you to override the default Mozilla endpoint.
What you can do with it
- 1Searching for specific issuesFind bugs using specific filters like component or status or through a general text search.
- 2Updating bug statusModify existing bug reports by changing their status or adding new CC members.
- 3Managing bug discussionsRead through existing comment threads or post new comments to a bug report.
- 4Handling file attachmentsUpload patches or files directly to a bug report to provide more context.
Written from the project's README. Every use case is checked against a quote from it.
Configuration
MCP_BUGZILLA_API_KEY
| Name | Description | |
|---|---|---|
| MCP_BUGZILLA_API_KEY | — |
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablekud/mcp-bugzilla is public and reachablegithub.com/kud/mcp-bugzilla ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/kud/mcp-bugzilla ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub
MCP server for Bugzilla — search, discuss, and manage Firefox/Mozilla bugs via the Bugzilla REST API.
Website · Documentation
Features
- Bug lookup — fetch any bug by ID or alias, including its full field-change history.
- Powerful search — filter by product, component, status, severity, assignee, keywords, or free-text
quicksearch. - Comment threads — read all comments on a bug, post new ones, and tag comments (e.g. spam, needinfo).
- Attachment management — list, upload, and update patches and files; set review flags inline.
- Write support — create and update bugs, change status, add CC members, and mark duplicates — all gated behind an API key so read-only use needs no credentials.
- Product and user discovery — enumerate products, components, versions, flag types, field definitions, and look up users by email.
Install
Register the server with your MCP client. For Claude Desktop, add the following to your claude_desktop_config.json:
{
"mcpServers": {
"mcp-bugzilla": {
"command": "npx",
"args": ["-y", "@kud/mcp-bugzilla"],
"env": {
"MCP_BUGZILLA_API_KEY": "your-api-key-here"
}
}
}
}
MCP_BUGZILLA_API_KEY is optional — omit it for read-only access. To obtain a key, visit your Bugzilla API Keys preferences page.
The MCP_BUGZILLA_BASE_URL environment variable overrides the default endpoint (https://bugzilla.mozilla.org/rest) for self-hosted instances.
Usage
The server exposes 17 tools across six areas. Tools marked with 🔑 require MCP_BUGZILLA_API_KEY.
| Tool | Area | Auth | Description |
|---|---|---|---|
get_bug |
Bugs | — | Fetch a single bug by ID or alias |
search_bugs |
Bugs | — | Search with filters or full-text quicksearch |
create_bug |
Bugs | 🔑 | File a new bug |
update_bug |
Bugs | 🔑 | Update fields, status, keywords, CC, or close as duplicate |
get_bug_history |
Bugs | — | Get the field-change history for a bug |
get_comments |
Comments | — | Get all comments, optionally filtered by date |
create_comment |
Comments | 🔑 | Post a comment, optionally with work-time logging |
search_comment_tags |
Comments | — | Search available comment tag names |
update_comment_tags |
Comments | 🔑 | Add or remove tags on a comment |
get_attachments |
Attachments | — | List attachments for a bug |
create_attachment |
Attachments | 🔑 | Upload a patch or file (base64-encoded) |
update_attachment |
Attachments | 🔑 | Rename, mark obsolete, or change flags on an attachment |
get_products |
Products | — | List accessible products |
get_product |
Products | — | Get product details including components and versions |
get_user |
Users | — | Look up a user by email or login name |
get_bug_fields |
Fields | — | List bug fields and their legal values |
get_flag_types |
Flags | — | List flag types for a product/component |
Development
git clone https://github.com/kud/mcp-bugzilla.git
cd mcp-bugzilla
npm install
npm run dev
| Script | Description |
|---|---|
npm run build |
Compile TypeScript to dist/ |
npm run dev |
Run source directly via tsx |
npm test |
Run the Vitest test suite |
npm run typecheck |
Type-check without emitting |
npm run inspect:dev |
Open MCP Inspector against source |
📚 Full documentation → mcp-bugzilla/docs
Bugzilla MCP questions
Do I need an API key to use this server?
No, an API key is optional for read-only access, but required for write operations like creating bugs or posting comments.
What kind of bug information can I retrieve?
You can fetch bugs by ID or alias, view full field-change history, and read all comment threads.