https://github.com/allenrobel/bug-tracker-mcp
MCP server to track bugs
https://github.com/allenrobel/bug-tracker-mcp
bug-tracker bug-tracking mcp mcp-server
Last synced: 8 days ago
JSON representation
MCP server to track bugs
- Host: GitHub
- URL: https://github.com/allenrobel/bug-tracker-mcp
- Owner: allenrobel
- Created: 2026-06-03T02:41:00.000Z (15 days ago)
- Default Branch: main
- Last Pushed: 2026-06-09T19:28:05.000Z (9 days ago)
- Last Synced: 2026-06-09T20:21:13.410Z (8 days ago)
- Topics: bug-tracker, bug-tracking, mcp, mcp-server
- Language: Python
- Homepage:
- Size: 83 KB
- Stars: 1
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Bug Tracker MCP Server
## Summary
An MCP Server that leverages notes written in Markdown to track bugs. The server was written for those
developing Cisco Nexus Dashboard applications which use the REST API, but could easily be
leveraged for other uses.
My use case is providing Claude Code with a resource through which it can determine the
suitability of various Nexus Dashboard endpoints for a given task, and whether an endpoint exhibits
any behavioral bugs and, if so, what version(s) exhibit the behavior and what
version (if any) fixes the behavior. Notes might also contain workaround(s).
**The actual notes are not included in this repository.**
## Setup
### 1. Install Obsidian and login
### 2. Setup sync with the ND Vault (vault should be in `$HOME/Obsidian/ND`)
### 3. Edit `com.bug-tracker-mcp.plist` such that the paths match your environment
- `OBSIDIAN_VAULT_PATH` should point to your ND vault (e.g. `$HOME/Obsidian/ND`)
- `ProgramArguments` should call `uv server.py` via their full paths e.g.
- `/Users/arobel/repos/mcp/bug-tracker-mcp/.venv/bin/uv`
- run
- `/Users/arobel/repos/mcp/bug-tracker-mcp/server.py`
- `WorkingDirectory` should point to this repository on your host
- `/Users/arobel/repos/mcp/bug-tracker-mcp`
```bash
cd $HOME/repos/mcp/bug-tracker-mcp
vi com.bug-tracker-mcp.plist
cp com.bug-tracker-mcp.plist $HOME/Library/LaunchAgents
chmod 644 $HOME/Library/LaunchAgents/com.bug-tracker-mcp.plist
```
### 4. (Re)start the LaunchAgent
```bash
launchctl bootout gui/$(id -u)/com.bug-tracker-mcp
launchctl bootstrap gui/$(id -u) $HOME/Library/LaunchAgents/com.bug-tracker-mcp.plist
```
### 5. Edit Claude Code's config on the client Mac to point to this MCP server
- edit $HOME/.claude.json
- Search for the `mcpServers` block
- Add the following (where `mm1e` is the hostname or IP address of the Mac that's hosting the MCP server)
```json
"mcpServers": {
"bug-tracker-mcp": {
"type": "http",
"url": "http://mm1e:8001/mcp"
}
}
```
### 5. Restart Claude Code and check the MCP server status using the `/mcp` slash command
## MCP Server Logic Diagram
```mermaid
flowchart TD
A("Module import and setup") --> B["Read environment, constants, and create FastMCP"]
B --> C{"Running as main script?"}
C -->|Yes| D["Start MCP HTTP server"]
D --> E["Await MCP tool calls"]
C -->|No| E
E --> F{"Which tool is called?"}
F -->|list_bugs, search_bugs, or get_bug_by_id| I[["_all_notes()"]]
F -->|find_bugs_for_endpoint or find_bugs_for_version| G{"Version parses?"}
F -->|get_bug| J{"Target file exists and is relevant?"}
G -->|No| ERR["Raise ValueError or FileNotFoundError"]
G -->|Yes| I
J -->|No| ERR
J -->|Yes| L[["_load_note(path)"]]
I --> M{"Vault directory exists?"}
M -->|No| ERR
M -->|Yes| R[("Vault files and note cache")]
R --> N{"More markdown files?"}
N -->|Yes| O{"Relevant markdown file?"}
N -->|No| W["Drop stale cache entries and return note set"]
O -->|No| N
O -->|Yes| L
L --> P{"Cached note has same mtime?"}
P -->|Yes| Q["Reuse cached Note"]
P -->|No| S["Parse frontmatter and build Note"]
Q --> T{"Called from get_bug?"}
S --> T
T -->|Yes| Z["Return full metadata and content"]
T -->|No| N
W --> X["Apply tool-specific sorting, scoring, snippets, and filters"]
X --> Z
```