@digital-streams-media/mcp-server

MCP server for Bug Traker — connects Claude Code, Claude Desktop, Cline, and any other MCP-compatible client to your Bug Traker workspace.

What it does

Exposes nine MCP tools for bug-triage, codebase-extraction, and quality workflows:

• bug_tracker_list_bugs — list bugs assigned to you, filtered by status
• bug_tracker_get_bug_context — full bug detail including annotated screenshots and session-recording stills
• bug_tracker_propose_bug_update — post a diagnosis or fix proposal as a comment (developer reviews and applies manually)
• bug_tracker_list_prompts / bug_tracker_get_prompt — fetch extraction prompts
• bug_tracker_submit_extraction / bug_tracker_submit_quality / bug_tracker_submit_tests / bug_tracker_submit_system_state — submit codebase analysis results back into the workspace

The server itself is a thin client around the Bug Traker REST API. All authorisation, business logic, and data live on app.bug-traker.com. Your API key never leaves the local process.

Install

You don't usually install this directly — your MCP client (Claude Code, Claude Desktop, etc.) does it for you when you reference the package in .mcp.json / mcp.config.json. The standard pattern:

{
  "mcpServers": {
    "bug-tracker": {
      "command": "npx",
      "args": ["-y", "@digital-streams-media/mcp-server@latest"],
      "env": {
        "BUG_TRACKER_API_URL": "https://app.bug-traker.com/api",
        "BUG_TRACKER_API_KEY": "bt_usr_..."
      }
    }
  }
}

npx will fetch the package on first use and cache it for subsequent runs. The Bug Traker VS Code extension writes this configuration automatically when you connect a workspace.

Get an API key

Sign in to app.bug-traker.com, go to Profile → VS Code Extension, and copy your personal API key (starts with bt_usr_). The key is scoped to your account and the projects you have access to. You can revoke and regenerate at any time.

Configuration

The MCP server reads its configuration in this order:

1. Environment variables (the standard MCP-host pattern, used by .mcp.json above)
   • BUG_TRACKER_API_URL (default: https://app.bug-traker.com/api)
   • BUG_TRACKER_API_KEY
   • MCP_ALLOW_PROPOSALS (default: false — guards bug_tracker_propose_bug_update)
2. Credential broker (0.5.0+) — BUG_TRACKER_BROKER_SOCKET, set by the Bug Traker VS Code extension in the .mcp.json it writes. The server connects to that local socket (Unix domain socket / Windows named pipe) at startup and receives the key from the extension, which holds it in the OS keychain. Nothing is written to disk.
3. Config file at ~/.bug-tracker/mcp-config.json — legacy. Written by extension versions before the broker; a plaintext key on disk. VSIX 1.60.0+ stops writing it and deletes any copy it finds once the broker is in use.

If none is configured, the server exits with a clear error pointing to the API-key page.

Why the broker

An API key in a file is readable by anything that can read the file — backups, cloud-sync clients, screen shares, support bundles, another agent. The broker keeps the key in the keychain and in memory, and every handover is logged in the extension's diagnostics. If the extension is not running the server says so plainly rather than failing as a generic MCP error.

TLS / corporate proxy support

On Windows machines running TLS-inspecting AV (Avast, ESET, Defender, etc.) or corporate ZTNA gateways, Node's bundled CA list doesn't trust the inspecting CA. The server enumerates the OS root cert store at startup and grafts it onto Node's trust, with a 24h disk cache at ~/.bug-tracker/system-ca.pem. macOS gets equivalent treatment via the security CLI. Linux is a no-op (Node already honours /etc/ssl/certs).

Set BUG_TRACKER_SKIP_SYSTEM_CA=1 to disable the shim if your environment has its own TLS trust setup.

Source

github.com/digitalStreams/bug-traker → mcp-server/

Issues: github.com/digitalStreams/bug-traker/issues

License

MIT