bugzilla-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUGZILLA_URL | No | Point at another Bugzilla 5+ instance. | https://bugzilla.mozilla.org |
| BUGZILLA_API_KEY | No | API key from https://bugzilla.mozilla.org/userprefs.cgi?tab=apikey. Enables private bugs, user lookups, whoami, and higher rate limits. | |
| BUGZILLA_TIMEOUT_MS | No | Per-request timeout. | 60000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_bugsA | Search bugzilla.mozilla.org for bugs. Combine free-text Quicksearch syntax highlights (https://bugzilla.mozilla.org/page.cgi?id=quicksearch.html):
Structured filters (product/component/status/...) apply to all bugs regardless of open/closed unless |
| get_bugA | Fetch one or more bugs by ID or alias with full metadata (status, resolution, product/component, assignee, dependencies, regressions, duplicates, flags, see-also links, keywords, whiteboard, timestamps). Does not include comments; use get_bug_comments for those. |
| get_bug_commentsA | Fetch the comment thread for a bug. Comment #0 is the original description. Supports paging, newest-first ordering, filtering by time, and truncating long comments. |
| get_bug_historyA | Fetch the field-change history of a bug (status/resolution transitions, priority changes, assignee changes, flag changes, CC additions, etc.). Optionally filter to specific fields or a time window. |
| get_bug_attachmentsA | List attachments (patches, screenshots, logs, test cases) on a bug with metadata. Attachment content is not included; use get_attachment to fetch a specific attachment's content. |
| get_attachmentA | Fetch a single attachment by ID. Text-based attachments (patches, logs, text, JSON, HTML, source code) are returned decoded as text; binary attachments are returned as base64 when |
| get_related_bugsA | Resolve every bug linked to the given bug (depends_on, blocks, regressed_by, regressions, duplicates, dupe_of, and same-instance see_also links) and return a summary of each so the relationship graph can be understood in one call. |
| list_productsA | List Bugzilla products (e.g. Firefox, Core, Toolkit, DevTools, Fenix, GeckoView, Thunderbird, Web Compatibility). Returns names and descriptions; use get_product to see a product's components. |
| get_productA | Get a product's details including its components (with descriptions and triage owners), active versions, and milestones. Use this to find the right component name before filing or searching. |
| get_field_valuesA | Get the legal values for a bug field (e.g. status, resolution, priority, severity, bug_type, keywords, platform, op_sys, or any cf_* custom field). Useful for building precise searches. |
| get_userA | Look up Bugzilla users by login/email, numeric ID, or a fuzzy match on name/nickname (e.g. ':dholbert'). Note: bugzilla.mozilla.org only allows user lookups when authenticated with BUGZILLA_API_KEY. |
| whoamiA | Report which Bugzilla instance this server talks to, its version, and (if BUGZILLA_API_KEY is configured) the authenticated user. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a clearly distinct resource or action: search, bug details, comments, history, attachments, related bugs, products, field values, user lookup, and instance info. Even related tools like get_bug and get_related_bugs are differentiated by descriptions: the former returns metadata with links, the latter resolves and summarizes the relationship graph.
The vast majority of tools follow a consistent verb_noun snake_case pattern (search_bugs, get_bug, get_bug_comments, get_product). The only deviation is whoami, which breaks the pattern but is a recognizable standard command and self-explanatory.
Twelve tools is well-scoped for a Bugzilla read/query server. Each tool covers a meaningful operation without redundancy, and the count is neither too thin nor bloated.
The toolset is comprehensive for reading and searching Bugzilla data but lacks the core lifecycle operations expected of a bug tracker: there is no create_bug, update_bug, add_comment, or attachment upload tool. The get_product description even mentions 'before filing,' implying filing should be possible, but no such tool exists, which would cause agent failures for write-oriented tasks.