bug_tracker_mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUGTRACKER_ROOT | No | Overrides the directory holding the shared bugs.db file. | $XDG_DATA_HOME/bug-tracker-mcp or ~/.local/share/bug-tracker-mcp |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| log_bugB | Log a new bug or improvement into the bug tracking store. |
| list_bugsA | List bugs within a project with optional filtering and pagination. Returns lightweight BugSummary items (omitting full description and notes) for progressive
disclosure. Use |
| get_bugA | Get full details of a specific bug by ID within a project. |
| update_bugC | Update attributes of an existing bug within a project. |
| resolve_bugB | Mark a bug as fixed with optional resolution details. |
| delete_bugB | Delete a bug by ID within a project. |
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 6 tools
Each tool targets a distinct action on bugs: create, delete, list, get, update, and resolve. There is no overlap between their purposes.
All tool names follow a consistent verb_noun pattern: log_bug, delete_bug, list_bugs, get_bug, update_bug, resolve_bug. No mixing of conventions.
6 tools cover the essential CRUD operations plus a dedicated resolve action for a bug tracker. This is well-scoped and not excessive.
The set provides full create, read (list and get), update, delete, and resolve. Minor gaps like reassigning or changing status beyond resolve exist but are acceptable for a basic tracker.