mcp-bugzilla

The mcp-bugzilla server exposes Bugzilla data and actions through the MCP interface, enabling AI models and other MCP clients to query bug information, fetch and manage comments, and leverage Bugzilla’s quicksearch capabilities. Core tools include bug_info for retrieving full details of a bug, bug_comments for collecting discussion history (with optional private comments), and add_comment to post new notes to a bug. For searching, bugs_quicksearch allows you to query bugs using Bugzilla’s quicksearch syntax, with support for status filtering and field selection. Utility helpers like bug_url and server_url_resource help you construct URLs and inspect the current server configuration. You can also obtain a detailed summary of a bug’s comments with summarize_bug_prompt. All methods are designed to work through the MCP endpoint at /mcp/ and require a valid Bugzilla API key in the request headers by default.

Prerequisites:

• Python 3.13 or later
• Access to a Bugzilla instance with REST API and an API key
• Optional: Docker/Podman for containerized deployment

From source installation (recommended for development):

1. Clone the repository:

git clone <repository-url>
cd mcp-bugzilla

2. Install uv (Python Model Context Protocol runtime) and project dependencies:

uv sync

3. Run the server (specifying your Bugzilla server until the API key header is configured):

uv run mcp-bugzilla --bugzilla-server https://bugzilla.example.com --host 127.0.0.1 --port 8000

This will start the HTTP server at http://127.0.0.1:8000/mcp/.

Docker/PODMAN installation (alternative):

1. Pull and run the image:

docker pull kskarthik/mcp-bugzilla
docker run -p 8000:8000 \
  -e BUGZILLA_SERVER=https://bugzilla.example.com \
  kskarthik/mcp-bugzilla \
  --bugzilla-server https://bugzilla.example.com \
  --host 0.0.0.0 \
  --port 8000

2. Access the MCP endpoint at http://<host>:8000/mcp/.

Prerequisites for operation:

• A Bugzilla account with an API key (configured via header ApiKey by default or through MCP_API_KEY_HEADER).
• The Bugzilla server URL must be reachable from the machine running the MCP server.

Environment variables to customize behavior (examples):

• BUGZILLA_SERVER: Base URL of the Bugzilla instance (e.g., https://bugzilla.example.com)
• MCP_HOST / MCP_PORT: Address and port for the MCP server to listen on (default 127.0.0.1:8000)
• MCP_API_KEY_HEADER: HTTP header name used to pass the API key (default ApiKey)
• USE_AUTH_HEADER: Enable Authorization: Bearer header instead of api_key query parameter

Selective tool disabling (optional):

• MCP_BUGZILLA_DISABLED_METHODS='bug_info,bug_comments'

Common issues:

• If the server cannot reach Bugzilla, verify network access and API key validity.
• Ensure the bugzilla server URL is correct and the API key has the necessary permissions.
• When running behind a reverse proxy, ensure proper host/port configuration and path /mcp/ routing.