Bugbrain

tech.bugbrainPublished by bugbrain.techv0.2.0Updated Oct 25, 2026

BugBrain QA platform for AI coding tools: autonomous exploratory testing, test plans, a11y audits.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

BugBrain's local MCP server that connects an AI coding assistant to its QA platform for exploratory testing, test plans and accessibility audits.

What you can do
Connect an AI coding assistant to the BugBrain QA platform from the local machine via an API key and base URL setting, with an optional custom tunnel command for the create_tunnel tool. The manifest lists no individual tools, so the exact operations are not documented here; the platform is described as covering autonomous exploratory testing, test plans and accessibility audits.
When to use it
Worth considering if your team already uses BugBrain for QA and you want an AI coding assistant to drive exploratory testing, test plans or accessibility audits from the same session.
Requirements
Runs locally over stdio, typically via npx from the npm package. Requires a BugBrain API key in BUGBRAIN_API_KEY, created in the BugBrain settings under API Keys. Network access to the BugBrain API is needed; BUGBRAIN_BASE_URL can override the default endpoint, and the tunnel tool defaults to cloudflared unless BUGBRAIN_TUNNEL_CMD is set.
Before you install
The server needs a live API key (BUGBRAIN_API_KEY) that grants access to your BugBrain account, so keep it out of shared configs. Testing and tunnel tools may run commands or open network tunnels on your machine, and the default tunnel relies on cloudflared. Data from your project is sent to the BugBrain service.

Installation

In SourceWeft

  1. Open Bugbrain in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.