Skip to main content
Connect your AI coding assistant to BugRadar for seamless documentation access and test flow management directly from your IDE.

Configuration

Connect BugRadar with your existing account using browser sign-in. Devin currently uses the API-key setup described below.
If you added BugRadar from the Claude connector directory and sign in to Claude Code with your Claude account, it already appears in /mcp.Otherwise, run in your project directory:
Open Claude Code, run /mcp, select BugRadar, and follow the browser sign-in prompt.
In the browser, sign in to BugRadar, check the agent name and company, and click Connect. The agent can work in any workspace you can access in that company. Return to your agent and ask it to list your BugRadar flows. If the authorization session ends before you approve, start a fresh connection from your agent. Do not reuse the old browser tab. Existing API-key connections continue to work. To switch one to browser sign-in, remove its x-api-key header and reconnect. Keep the key until the new connection works; revoke it only if no other integrations use it. You may need to restart your agent for the changes to take effect.

Verify the Connection

Once configured, test the server:
If the connection is successful, you’ll receive responses from both questions.

Available Tools

The BugRadar MCP server provides comprehensive test management, debugging, and documentation access.

Flow Management

Suite Management

Folder Management

Hook Management

To attach a built-in hook such as Lease email address, pass {"type": "builtin", "builtin_key": "lease_email_inbox", "hook_type": "setup"} in the hooks list of flows_create, flows_update, suites_create, or suites_update. It’s added to your organization automatically if it isn’t there yet.

Apps & Environments

Filter apps_list with platform: "chrome-extension" to discover extension apps and their UUIDs. Use devices_list to choose a model and OS. Set model or os_version to "latest" for explicit rolling resolution, or omit device to use the newest supported default for both. Both flows_run and suites_run accept dependencies as a JSON array string for web runs:
Omit dependencies to use the web app’s attached defaults. Pass "[]" to explicitly run without extensions. An app UUID uses that extension’s active build; an object with app_build_id pins the exact build. Extension-enabled runs use Chrome by default or Chromium, and one suite run uses the same extension loadout for every flow in its shared browser session. Run and automation tools accept locale (such as "de-DE") to open the app in that language, and most accept location (such as "MX") to send traffic from that country. Language & region and Proxy location list which tools take each one. Run responses from flows_run, suites_run, and labels_run include a Batch link for viewing or sharing all runs launched together. To run code-managed tests as they are on a branch, pass repo_full_name and branch_name to labels_run, suites_run, or folders_run. The run uses that branch’s .BugRadar/ files, including tests that exist only on the branch, and the newest build uploaded for the branch. A suite that exists only on the branch has no ID yet, so pass suite_key (its folder path under .BugRadar/) to suites_run instead of suite_id. For a folder that exists only on the branch, pass folder_paths (for example Auth/Onboarding) to folders_run instead of folder_ids. Without a branch, runs use the default branch’s tests. If the branch has an open pull request, a branch run shows its results on that pull request, for that commit only. A later push does not run those tests again.

Workspaces

Every other tool acts in your active workspace. These two tools need a browser sign-in connection. An API key always acts in the workspace it was created in. Switching applies to your whole BugRadar login, not just one agent. The dashboard and any other agent signed in as you switch too.

Results & Debugging

read_flow_run reports the exact dependency build IDs and available extension metadata such as app/build IDs, app name, platform, source, branch, commit, and upload time. It also returns a public link to the run’s screen recording (MP4), one per device for a two-device run.

Labels, Automations & Environment Variables

Issues & Pull Requests

Account & Documentation


Example Usage

Generate E2E tests from your codebase

Increase test coverage from a PR

Debug failing tests

Create hooks for backend setup

Check test run history

Identify coverage gaps


Permissions and Data

The server acts in your workspace with your access. An API key acts in the workspace where it was created. Secret values are never returned.
  • Reads and changes your BugRadar data: flows, suites, apps, run results and settings.
  • Commits passing flows to your linked GitHub repo with pr_commit_flow_as_code.
  • Starts runs that count toward your plan’s usage.
  • Labels every tool as read-only or able to change data, so your assistant can ask before making changes.
To disconnect, remove BugRadar from your assistant’s MCP settings. See our Privacy Policy and Terms of Service, or email founders@usebugradar.com.

Resources