Bugzilla MCP server
Commit Nov 14, 2026Enables AI clients to query bug information, manage comments, track history, and automate bug workflows through Bugzilla instances.
Also known as openSUSE/mcp-bugzilla
- Stars
- 15
- Tools
- 24
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 14, 2026
- License
- —
What is Bugzilla MCP?
Bugzilla enables AI clients to query bug information, manage comments, track history, and automate bug workflows through Bugzilla instances. It exposes 24 tools, such as bug_info, bug_history, bug_comments.
Summary generated from the project's README
About Bugzilla MCP server
Managing bug tracking workflows and querying issue data from inside an AI client is what mcp-bugzilla enables. Developers and QA engineers can use this server to interact with Bugzilla instances, allowing models to retrieve detailed bug information, examine change histories, and read discussion threads. The server provides specialized tools to filter through large amounts of data, such as excluding specific authors or limiting the number of comments returned to prevent context flooding.
Users can perform write operations like updating bug statuses, assigning issues to specific email addresses, or adding new comments. The server also handles file attachments, allowing for the listing of metadata or the downloading of patches and logs. Depending on the configuration, attachments can be returned inline as text or base64, or saved directly to a local directory. This setup requires appropriate Bugzilla permissions for any modification tasks and connects to your existing Bugzilla environment via the Model Context Protocol.
What you can do with it
- 1Summarize bug lifecycle changesAsk the AI to show only the status and resolution changes for a specific bug to avoid noise from other field updates.
- 2Automate issue assignmentDirect the AI to assign a bug to a specific developer with an explanatory comment.
- 3Retrieve relevant patchesRequest a list of only the most recent attachments that are flagged as patches for a given bug.
- 4Filter out bot noiseFetch recent comments while ignoring automated messages from release monitoring bots.
Written from the project's README. Every use case is checked against a quote from it.
Bugzilla MCP tools 24
Detected from the READMEbug_infobug_historybug_commentsget_component_defaultsadd_commentlist_attachmentsdownload_attachmentupdate_bug_statusassign_bugupdate_bug_fieldsadd_cc_to_bugmark_as_duplicate
| bug_info | — | |
| bug_history | — | |
| bug_comments | — | |
| get_component_defaults | — | |
| add_comment | — | |
| list_attachments | — | |
| download_attachment | — | |
| update_bug_status | — | |
| assign_bug | — | |
| update_bug_fields | — | |
| add_cc_to_bug | — | |
| mark_as_duplicate | — |
Show all 24 toolsShow fewer tools
create_bugadd_attachmentbugs_quicksearchquicksearch_syntax_resourcesummarize_bug_promptbug_urlbugzilla_versionbugzilla_extensionsbugzilla_timebugzilla_parametersmcp_server_info_resourceget_current_headers_resource
| create_bug | — | |
| add_attachment | — | |
| bugs_quicksearch | — | |
| quicksearch_syntax_resource | — | |
| summarize_bug_prompt | — | |
| bug_url | — | |
| bugzilla_version | — | |
| bugzilla_extensions | — | |
| bugzilla_time | — | |
| bugzilla_parameters | — | |
| mcp_server_info_resource | — | |
| get_current_headers_resource | — |
Configuration
BUGZILLA_API_KEYBUGZILLA_AUTH_MODEBUGZILLA_SERVERLOG_LEVELMCP_AUTH_HEADERMCP_BUGZILLA_DISABLED_METHODSMCP_HOSTMCP_PORTMCP_READ_ONLY
| Name | Description | |
|---|---|---|
| BUGZILLA_API_KEY | — | |
| BUGZILLA_AUTH_MODE | — | |
| BUGZILLA_SERVER | — | |
| LOG_LEVEL | — | |
| MCP_AUTH_HEADER | — | |
| MCP_BUGZILLA_DISABLED_METHODS | — | |
| MCP_HOST | — | |
| MCP_PORT | — | |
| MCP_READ_ONLY | — |
Automated checks
Ran Nov 14, 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 reachableopensuse/mcp-bugzilla is public and reachablegithub.com/opensuse/mcp-bugzilla ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-11github.com/opensuse/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 model24 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubBugzilla Model Context Protocol (MCP) Server
A robust MCP server that provides seamless interaction with Bugzilla instances through the Model Context Protocol. This server exposes a comprehensive set of tools and prompts, enabling AI models and other MCP clients to efficiently query bug information, manage comments, and leverage Bugzilla's powerful quicksearch capabilities.
Table of Contents
- Features
- Requirements
- Installation
- Configuration
- Usage
- API Reference
- Examples
- Troubleshooting
- License
Features
Tools
The server provides the following tools for interacting with Bugzilla:
Bug Information
-
bug_info(bug_ids: list[int], include_fields: Optional[str] = None, exclude_fields: Optional[str] = None): Retrieves comprehensive details for specified Bugzilla bug IDs. By default every field is returned; use Bugzilla's native field selection to trim large or bulk fetches.- Parameters:
bug_ids: A list of bug IDs to fetch details forinclude_fields: Comma-separated field names to return (Bugzilla's nativeBug.getparameter; supports field groups and_default/_all/_extra). For the leanest response request only scalar fields, e.g."id,status,resolution,summary". Requesting a user field (assigned_to,creator,cc,qa_contact) also returns its verbose*_detailobject. Defaults to all fieldsexclude_fields: Comma-separated field names to drop. To remove a user-object expansion, exclude both the base field and its*_detailtogether, e.g."cc,cc_detail"— excluding the*_detailalone has no effect, as Bugzilla re-attaches it while the base field is present
- Returns: A dictionary containing the array
bugswhich lists the requested information about the bugs (status, assignee, summary, description, extensions, etc.) - Note on Bugzilla API parity: both
include_fieldsandexclude_fieldsare native BugzillaBug.getparameters, forwarded to the API unchanged; the underlying request is standard Bugzilla - Example:
bug_info([12345, 67890], include_fields="id,status,resolution,summary")fetches two bugs with just the essential scalar fields
- Parameters:
-
bug_history(bug_id: int, new_since: Optional[datetime] = None, changed_fields: Optional[str] = None, exclude_authors: Optional[str] = None, limit: Optional[int] = None): Fetches the change history of a given bug ID, with SQL-like controls to keep only the change events that matter for triage.- Parameters:
bug_id: The bug ID to fetch history fornew_since: Optional datetime object to only return history newer than this timechanged_fields: Comma-separated Bugzilla field names; keep only changes to these fields, dropping events left with no matching change (e.g."status,resolution,assigned_to"to see only lifecycle changes and hide the cc / flagtypes.name / summary churn that dominates most histories)exclude_authors: Comma-separated substrings; drop events whose author matches any (e.g."upstream-release-monitoring"to hide release-monitoring bot edits)limit: Return only the most recent N events (chronological order preserved)
- Returns: A list of history-event dictionaries, each containing
when,who, and achangeslist (each change hasfield_name,added, andremoved) - Note on Bugzilla API parity:
new_sincemirrors Bugzilla's own API parameter.changed_fields,exclude_authors, andlimithave no server-side Bugzilla equivalent — this server applies them client-side, as post-processing over the standardBug.historyresponse; the underlying Bugzilla request is unmodified - Example:
bug_history(2504555, changed_fields="status,resolution")returns just the event where the bug was closed as RAWHIDE, filtering out the surrounding cc and needinfo-flag churn
- Parameters:
-
bug_comments(bug_id: int, include_private_comments: bool = False, new_since: Optional[datetime] = None, include_fields: Optional[str] = "count,id,creator,creation_time,text,attachment_id,is_private", exclude_creators: Optional[str] = None, limit: Optional[int] = None): Fetches comments associated with a given bug ID, with SQL-like controls to keep only what is needed and avoid flooding the context on large threads.- Parameters:
id: The bug ID to fetch comments forinclude_private_comments: Whether to include private comments (default:False)new_since: Optional datetime object to only return comments newer than this timeinclude_fields: Comma-separated field names to keep per comment (default:count,id,creator,creation_time,text,attachment_id). PassNoneto return every fieldexclude_creators: Comma-separated substrings; drop comments whose creator matches any (e.g."upstream-release-monitoring"to hide release-monitoring/bot noise)limit: Return only the most recent N comments (chronological order preserved)
- Returns: A list of comment dictionaries. By default each contains
count,id,creator,creation_time,text, andattachment_id; passinclude_fields=Nonefor the full objects (which also includecreator_id,bug_id,tags,time, andis_private) - Note on Bugzilla API parity:
new_sinceandinclude_fieldsmirror Bugzilla's own API parameters of the same names (include_fieldsis applied client-side here).exclude_creatorsandlimithave no server-side Bugzilla equivalent — this server applies them client-side, as post-processing over the standardBug.commentsresponse; the underlying Bugzilla request is unmodified. - Example:
bug_comments(12345, exclude_creators="upstream-release-monitoring", limit=5)returns the 5 most recent comments that aren't from the release-monitoring bot
- Parameters:
-
get_component_defaults(component: str = None, product: str = None, bug_id: int = None): Looks up a component's default assignee and QA contact, read from the parent product since Bugzilla has no component endpoint.- Parameters:
component: Component name (resolved frombug_idif omitted)product: Product the component belongs to (resolved frombug_idif omitted)bug_id: Resolve product/component from this bug instead of passing them
- Returns: A dictionary with
product,component,default_assignee,default_qa_contact,is_active - Example:
get_component_defaults(bug_id=12345)returns the defaults for that bug's component. To reset a bug to these defaults, useupdate_bug_fields(..., reset_qa_contact=True).
- Parameters:
-
add_comment(bug_id: int, comment: str, is_private: bool = False): Adds a new comment to a specified bug.- Parameters:
bug_id: The bug ID to add a comment tocomment: The comment text to addis_private: Whether the comment should be private (default:False)
- Returns: A dictionary containing the ID of the newly created comment
- Example:
add_comment(12345, "Fixed in version 2.0", is_private=False)
- Parameters:
Attachments
-
list_attachments(bug_id: int, exclude_obsolete: bool = False, patches_only: bool = False, limit: Optional[int] = None): Lists a bug's attachments as metadata only (the base64 file contents are excluded to keep responses small), with filters to cut the noise on bugs that accumulate many attachments.- Parameters:
bug_id: The bug whose attachments to listexclude_obsolete: Drop attachments flagged obsolete (is_obsolete). Note: some bots (e.g. release-monitoring) never set this flag, so it only helps where obsolete is actually usedpatches_only: Keep only attachments flagged as patches (is_patch)limit: Return only the most recent N attachments (chronological order preserved)
- Returns: A list of attachment metadata objects (
id,file_name,summary,content_type,size,is_private,is_obsolete,is_patch,creation_time, ...). Use anidwithdownload_attachmentto fetch the file. - Note on Bugzilla API parity:
exclude_obsolete,patches_only, andlimithave no server-side Bugzilla equivalent — this server applies them client-side, as post-processing over the standard attachment metadata; the underlying Bugzilla request is unmodified - Example:
list_attachments(2381747, patches_only=True, limit=3)returns the 3 most recent patch attachments
- Parameters:
-
download_attachment(attachment_id: int, output_dir: Optional[str] = None, delivery: "auto" | "inline" | "save" = "auto", include_private: bool = False): Downloads a single attachment by id. Thedeliveryargument lets the caller choose how the content is returned.- Parameters:
attachment_id: The attachment id to download (discover vialist_attachments)output_dir: Optional directory to save the file in when it is written to disk. Defaults to the server's configured download directory (--download-dir/BUGZILLA_DOWNLOAD_DIR).delivery:auto(default): textual attachments (logs, patches, plain/xml/json, ...) up to 256 KiB are returned inline as decodedcontent; binary attachments, or larger text, are written to disk.inline: always return the content in the response — decodedcontentfor text, or base64data_base64for binary (and for text whose bytes are not valid UTF-8). Refused above 1 MiB.save: always write the file to disk and return itspath.
include_private: Whether to download a private attachment (default:False); a private attachment is refused unless this is set toTrue.
- Returns: Text inline:
{"mode": "text", "content": <decoded text>, ...metadata}. Binary inline:{"mode": "base64", "data_base64": <base64>, ...metadata}. On disk:{"mode": "saved", "path": <absolute path>, ...metadata}. The saved file is named<attachment_id>-<sanitized file_name>. - Example:
download_attachment(685495)·download_attachment(685495, delivery="save")
- Parameters:
Write Operations
Note: Write operations require appropriate Bugzilla permissions. These tools enable bug management and workflow automation.
-
update_bug_status(bug_id: int, status: str, resolution: str = None, comment: str = ""): Updates the status of a bug with optional comment.- Parameters:
bug_id: The bug ID to updatestatus: New status (e.g.,NEW,ASSIGNED,MODIFIED,ON_QA,VERIFIED,CLOSED)resolution: Required when status isCLOSED(e.g.,FIXED,WONTFIX,NOTABUG,DUPLICATE)comment: Optional comment explaining the status change
- Returns: A dictionary containing the updated bug fields
- Example:
update_bug_status(12345, "CLOSED", resolution="FIXED", comment="Fixed in version 2.0")
- Parameters:
-
assign_bug(bug_id: int, assignee: str, comment: str = ""): Assigns a bug to a user.- Parameters:
bug_id: The bug ID to assignassignee: Email address of the assigneecomment: Optional comment explaining the assignment
- Returns: A dictionary containing the updated bug fields
- Example:
assign_bug(12345, "developer@example.com", comment="You're the expert on this component")
- Parameters:
-
update_bug_fields(bug_id: int, priority: str = None, severity: str = None, resolution: str = None, custom_fields: dict = None, reset_qa_contact: bool = False, reset_assigned_to: bool = False, comment: str = ""): Updates various bug fields.- Parameters:
bug_id: The bug ID to updatepriority: Priority level (e.g.,urgent,high,medium,low,unspecified)severity: Severity level (e.g.,urgent,high,medium,low,unspecified)resolution: Resolution (only for closed bugs)custom_fields: Dict of custom fields, e.g.{"cf_fixed_in": "1.2.3"}reset_qa_contact: IfTrue, reset the QA contact to the component's defaultreset_assigned_to: IfTrue, reset the assignee to the component's defaultcomment: Optional comment explaining the changes
- Returns: A dictionary containing the updated bug fields
- Example:
update_bug_fields(12345, priority="high", severity="urgent", comment="Escalating due to customer impact") - Example:
update_bug_fields(12345, reset_qa_contact=True)resets the QA contact to the component default
- Parameters:
-
add_cc_to_bug(bug_id: int, cc_email: str): Adds an email address to the CC list of a bug.- Parameters:
bug_id: The bug IDcc_email: Email address to add to CC list
- Returns: A dictionary containing the updated bug fields
- Example:
add_cc_to_bug(12345, "manager@example.com")
- Parameters:
-
mark_as_duplicate(bug_id: int, duplicate_of: int, comment: str = ""): Marks a bug as a duplicate of another bug and closes it.- Parameters:
bug_id: The bug ID to mark as duplicateduplicate_of: The bug ID this is a duplicate ofcomment: Optional comment (auto-generated if not provided)
- Returns: A dictionary containing the updated bug fields including status
CLOSED, resolutionDUPLICATE, anddupe_ofreference - Example:
mark_as_duplicate(12345, 789012, comment="Same root cause as the original report")
- Parameters:
-
create_bug(product, component, summary, version, description, op_sys="All", platform="All", priority=None, severity=None, cc=None, custom_fields=None): Files a new bug.- Parameters:
product,component,summary,version,description: Required core fieldsop_sys,platform: Default toAllpriority,severity: Optional, instance-specific valuescc: Optional list of email addresses to CCcustom_fields: Optional dict of extra/custom fields (e.g.{"cf_fixed_in": "1.2.3"})
- Returns: A dictionary with the new bug
id. If the Bugzilla instance mandates additional fields, its error message is surfaced so you can retry with them. - Example:
create_bug("MyProduct", "general", "App crashes on launch", "unspecified", "Steps to reproduce: ...")
- Parameters:
-
add_attachment(bug_id, file_name, summary, data, content_type="text/plain", is_patch=False, is_private=False, comment=""): Attaches a file to a bug.- Parameters:
bug_id: The bug to attach tofile_name: File name shown in Bugzillasummary: Short description of the attachmentdata: The attachment content, base64-encodedcontent_type: MIME type (ignored whenis_patch=True)is_patch: Mark the attachment as a patchis_private: Restrict to the insider groupcomment: Optional comment added alongside the attachment
- Returns: A dictionary with the created attachment
ids - Example:
add_attachment(12345, "crash.log", "Crash log", "aGVsbG8=", content_type="text/plain")
- Parameters:
Bug Search
-
bugs_quicksearch(query: str, include_fields: str = "...", limit: int = 50, offset: int = 0, order: str = "relevance"): Executes a search for bugs using Bugzilla's powerful quicksearch syntax.- Parameters:
query: A quicksearch query string (e.g.,"product:Firefox")include_fields: Comma-separated list of fields to return (default:"id,product,component,assigned_to,status,resolution,summary,last_change_time")limit: Maximum number of results to return (default:50)offset: Number of results to skip for pagination (default:0)order: Sort order (default:"relevance"). For field searches, use"bug_id DESC"to sort newest bugs first, or"changeddate DESC"to sort by recently modified.
- Returns: A list of dictionaries, each containing essential bug fields
- Example:
bugs_quicksearch("product:Firefox status:NEW", limit=10, order="bug_id DESC")
- Parameters:
-
quicksearch_syntax_resource(): Returns documentation on Bugzilla's quicksearch syntax.- Returns: A string containing Markdown documentation.
-
summarize_bug_prompt(bug_id: int): Returns a detailed summary prompt for all comments of a given bug ID.- Returns: A well-structured summary of the bug's comments including usernames (bold italic) and dates (bold).
Utility Tools
-
bug_url(bug_id: int): Constructs and returns the direct URL to a specific bug on the Bugzilla server.- Returns: A string representing the bug's URL (e.g.,
"https://bugzilla.example.com/show_bug.cgi?id=12345")
- Returns: A string representing the bug's URL (e.g.,
-
bugzilla_version(): Returns the version of the Bugzilla server.- Returns: A string representing the Bugzilla version (e.g.,
"5.0.4").
- Returns: A string representing the Bugzilla version (e.g.,
-
bugzilla_extensions(): Returns the extensions installed on the Bugzilla server.- Returns: A dictionary containing installed Bugzilla extensions and their metadata.
-
bugzilla_time(): Returns the current time and timezone of the Bugzilla server.- Returns: A dictionary containing server time (
db_time,web_time,web_time_utc) and timezone details (tz_name,tz_offset,tz_short_name).
- Returns: A dictionary containing server time (
-
bugzilla_parameters(names: list[str] = None): Returns the configuration parameters of the Bugzilla server.- Parameters:
names: Optional list of parameter names to filter results
- Returns: A dictionary containing Bugzilla configuration parameters.
- Parameters:
-
mcp_server_info_resource(): Returns the configuration arguments being used by the current server instance (version, host, port, etc.).- Returns: A dictionary containing server configuration.
-
get_current_headers_resource(): Returns the HTTP headers from the current request.- Returns: A dictionary of HTTP headers.
Requirements
- Python 3.13
- A Bugzilla instance with REST API access
- A Bugzilla user account with an API key (optional: public instances support anonymous access)
- Network access to the Bugzilla server
Installation
PyPI
The easiest way to install and run mcp-bugzilla is using uv:
Option 1: Using uvx (Recommended - No Installation Required)
Run the server directly without installing it:
uvx mcp-bugzilla --bugzilla-server https://bugzilla.example.com
This will automatically download and run the latest version.
Option 2: Install with uv pip
If you prefer to have mcp-bugzilla installed in your system:
# Install the package
uv pip install mcp-bugzilla
# Run the server
mcp-bugzilla --bugzilla-server https://bugzilla.example.com
Option 3: Install in a Virtual Environment
Create an isolated environment for mcp-bugzilla:
# Create a virtual environment
uv venv mcp-bugzilla-env
source mcp-bugzilla-env/bin/activate # On Windows: mcp-bugzilla-env\Scripts\activate
# Install the package
uv pip install mcp-bugzilla
# Run the server
mcp-bugzilla --bugzilla-server https://bugzilla.example.com
Note: If you don't have uv installed, install it first from https://github.com/astral-sh/uv#installation
From Source
-
Clone the repository:
git clone <repository-url> cd mcp-bugzilla -
Install dependencies:
uv sync -
Run the server:
uv run mcp-bugzilla --bugzilla-server https://bugzilla.example.com --host 127.0.0.1 --port 8000This will start the HTTP server at
http://127.0.0.1:8000/mcp/.
Docker
Pull the pre-built image from the openSUSE registry:
docker pull registry.opensuse.org/opensuse/mcp-bugzilla:latest
Run the container:
docker run -p 8000:8000 \
registry.opensuse.org/opensuse/mcp-bugzilla:latest \
--bugzilla-server https://bugzilla.example.com \
--host 0.0.0.0 \
--port 8000
You can also pass configuration via environment variables:
docker run -p 8000:8000 \
-e BUGZILLA_SERVER=https://bugzilla.example.com \
-e MCP_HOST=0.0.0.0 \
-e MCP_PORT=8000 \
registry.opensuse.org/opensuse/mcp-bugzilla:latest
Podman works identically — just substitute docker with podman.
Configuration
Command-Line Arguments
The mcp-bugzilla command supports the following options:
| Argument | Environment Variable | Default | Description |
|---|---|---|---|
--bugzilla-server <URL> |
BUGZILLA_SERVER |
Required | Base URL of the Bugzilla server (e.g., https://bugzilla.example.com) |
--transport {http,stdio} |
MCP_TRANSPORT |
http |
Transport for the MCP server. stdio is for direct subprocess launches by an MCP client; http exposes a network endpoint |
--host <ADDRESS> |
MCP_HOST |
127.0.0.1 |
Host address for the MCP server to listen on (http transport only) |
--port <PORT> |
MCP_PORT |
8000 |
Port for the MCP server to listen on (http transport only) |
--mcp-auth-header <HEADER> |
MCP_AUTH_HEADER |
none | HTTP header name that clients use to send the Bugzilla API key to this MCP server (http transport only). When not specified, inbound header authentication is disabled and client headers are ignored. |
--bugzilla-api-key <KEY> |
BUGZILLA_API_KEY |
none | Static Bugzilla API key. Optional: if omitted and not provided per-request via --mcp-auth-header (http), access is anonymous. For --transport stdio this is the only source of the key |
--bugzilla-auth-mode {query,bearer} |
BUGZILLA_AUTH_MODE |
query |
How to authenticate with Bugzilla: query sends ?api_key=<KEY> (default, works with most instances); bearer sends Authorization: Bearer <KEY> header (required for Red Hat Bugzilla and similar) |
--read-only |
MCP_READ_ONLY |
False |
Disables all tools which can modify a bug. Works well in conjunction with MCP_BUGZILLA_DISABLED_METHODS |
--tool-search |
MCP_TOOL_SEARCH |
False |
Collapse all tools into search_tools + call_tool meta-tools using BM25 relevance ranking. The LLM searches for tools by natural language query and calls them directly. Reduces context overhead when many tools are available |
--download-dir <DIR> |
BUGZILLA_DOWNLOAD_DIR |
<tmpdir>/mcp-bugzilla |
Directory where download_attachment writes binary/oversized attachments. The default directory is created on first use and restricted to the owner (0o700); an explicit output_dir keeps its own permissions |
Note: --host and --port are rejected with an error when used together with --transport stdio.
Note: Command-line arguments take precedence over environment variables.
Deprecated Arguments
The following arguments are deprecated and will be removed in a future release. They continue to work and emit a warning in the logs when used. Migrate to the replacements shown:
| Deprecated | Replacement | Notes |
|---|---|---|
--api-key / BUGZILLA_API_KEY (old semantics) |
--bugzilla-api-key / BUGZILLA_API_KEY |
Same env var; the new arg makes the intent explicit. Previously required for stdio; now optional (anonymous if absent) |
--api-key-header / MCP_API_KEY_HEADER |
--mcp-auth-header / MCP_AUTH_HEADER |
Clarifies that this controls the inbound client→MCP header |
--use-auth-header |
--bugzilla-auth-mode bearer |
Replaces a boolean flag with an explicit mode choice |
Bugzilla MCP questions
What tools does Bugzilla MCP provide?
It exposes 24 tools, including bug_info, bug_history, bug_comments, get_component_defaults, add_comment.
Can I filter bug history to see only specific changes?
Yes, you can use the changed_fields parameter to keep only changes to specific fields, such as status or resolution, which helps filter out noise.
Does the server support updating bug status?
Yes, the update_bug_status tool allows you to change a bug's status and resolution, and optionally include a comment explaining the change.