bugzilla-mcp
MCP server for managing Bugzilla tickets and projects, with a built-in cron job for scheduled polling.
README
bugzilla-mcp
MCP (Model Context Protocol) server for managing Bugzilla tickets and projects, served over Express with a built-in cron job that pings Bugzilla on a schedule.
Targets the Bugzilla 5.2 REST API.
Features
- MCP over Streamable HTTP at
POST /mcp(stateless; works with any MCP client) - 15 tools covering bugs, comments, attachments, products, components, and field metadata
- Cron job that pings Bugzilla at a preconfigured time and polls for changed bugs
- Dockerized (multi-stage build, non-root user, docker-compose)
MCP Tools
| Tool | Bugzilla endpoint |
|---|---|
search_bugs |
GET /rest/bug |
get_bug |
GET /rest/bug/(id_or_alias) |
create_bug |
POST /rest/bug |
update_bug |
PUT /rest/bug/(id_or_alias) |
get_bug_history |
GET /rest/bug/(id)/history |
get_comments |
GET /rest/bug/(id)/comment |
add_comment |
POST /rest/bug/(id)/comment |
list_attachments |
GET /rest/bug/(id)/attachment |
create_attachment |
POST /rest/bug/(id)/attachment |
list_products |
GET /rest/product_{accessible,enterable,selectable} |
get_product |
GET /rest/product/(id_or_name) |
create_product |
POST /rest/product |
update_product |
PUT /rest/product/(id_or_name) |
create_component |
POST /rest/component |
get_field_values |
GET /rest/field/bug/(field)/values |
Note: Bugzilla has no delete-bug API; closing/resolving is done via update_bug
(e.g. status=RESOLVED, resolution=FIXED).
HTTP Endpoints
| Endpoint | Description |
|---|---|
POST /mcp |
MCP Streamable HTTP endpoint |
GET /health |
Liveness check |
GET /cron/status |
Cron schedule, last run time/result |
POST /cron/run |
Trigger the cron job manually |
/mcp and /cron/* require Authorization: Bearer <MCP_AUTH_TOKEN> when
MCP_AUTH_TOKEN is set.
Configuration
Copy .env.example to .env and fill in:
| Variable | Required | Description |
|---|---|---|
BUGZILLA_BASE_URL |
yes | Bugzilla instance URL, e.g. https://bugzilla.example.com |
BUGZILLA_API_KEY |
yes | API key from Bugzilla Preferences → API Keys |
MCP_AUTH_TOKEN |
no | Bearer token protecting /mcp and /cron/* |
CRON_SCHEDULE |
no | Cron expression, evaluated in UTC (default 0 9 * * * = daily 09:00 UTC) |
PORT |
no | Listen port (default 3000) |
The API key is sent as the X-BUGZILLA-API-KEY header on every Bugzilla request.
Running
Docker (recommended)
cp .env.example .env # then edit
docker compose up --build
Local
npm install
npm run build
npm run start:local # loads .env via node --env-file; or: npm run dev
npm start reads configuration from the process environment only (used in the
Docker image); use start:local or dev to load a local .env file.
Cron Job
At each scheduled tick the job:
- Calls
GET /rest/versionas a health check. - Polls
GET /rest/bug?last_change_time=<lastRun>for bugs changed since the previous run (skipped on the first run since there is no baseline). - Logs results and stores the last result in memory, visible at
GET /cron/status.
Connecting an MCP Client
Point any Streamable-HTTP-capable MCP client at http://<host>:3000/mcp, with
header Authorization: Bearer <MCP_AUTH_TOKEN> if configured.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。