How to connect Bugbug to Claude

Connect Claude Web, Desktop and Cowork to Bugbug MCP. List all test suites in your workspace, run the login flow test on chrome, and more using natural language, with authentication handled for you.

Bugbug logoBugbug
Api Key

Bugbug is a platform for end-to-end software testing and monitoring. It helps developers catch bugs early and automate test coverage for their code.

4 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Bugbug account to Claude via Composio Connect, enabling it to list all test suites in your workspace, run the login flow test on Chrome, get details for yesterday's failed test runs, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Bugbug with

Connecting Bugbug to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Bugbug account

Back in Claude, ask it to connect to Bugbug or give it any Bugbug-related task.

For example, ask Claude to:

  • "List all test suites in your workspace"
  • "Run the login flow test on Chrome"
  • "Get details for yesterday's failed test runs"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Bugbug account is ready to use.

What is the Bugbug Claude Connector, and what's possible with it?

The Bugbug MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Bugbug account. It provides structured and secure access to your automated testing environment, so your agent can run tests, retrieve test run details, explore test suites, and manage tests with ease.

  • Execute automated tests on demand: Direct your agent to run specific tests instantly, including custom configuration for browser, device, or viewport settings.
  • Fetch detailed test run reports: Retrieve comprehensive information about past and ongoing test runs, including step-by-step execution statuses and results.
  • List and manage test suites: Ask your agent to list all available test suites in your Bugbug account for quick navigation and organization.
  • Explore and review all tests: Let your agent pull up a full list of tests, complete with IDs, names, descriptions, and timestamps for streamlined test management.

Troubleshooting

1. Why does Claude not use the Composio connector for Bugbug?

The connector can show as connected, but Claude must use it in each Bugbug conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Bugbug again.

2. Why does Claude show an MCP server error before Bugbug connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Bugbug.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Bugbug.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Bugbug authorization link not work?

The Composio connector is one server. Your Bugbug account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Bugbug connection.
  • Composio creates a fresh Bugbug authorization link.
  • Open that link in your browser and finish the Bugbug sign-in.

4. Why do Bugbug actions fail after they worked before?

The Bugbug connection can expire or lose permission.

  • Ask Claude to inspect the Bugbug connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Bugbug account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Bugbug.
  • If the action still fails with a permission error, check that the connected account has that permission in Bugbug itself.

5. How do I switch to a different Bugbug account?

Claude can manage the Bugbug connection for you.

  • Ask Claude to disconnect or delete the current Bugbug account.
  • Ask Claude to connect Bugbug again.
  • Open the new Composio authorization link for Bugbug.
  • Sign in with the other Bugbug account in the browser.
  • After the account connects, ask Claude to retry the Bugbug task.

6. Why is my Bugbug connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Bugbug connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click and click Clear cache.
  • If Bugbug tools still do not appear, click , disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Bugbug.
TOOLS

Supported Tools

Every Bugbug action and event your agent gets out of the box.

Get test run details

Get detailed information about test runs from BugBug.

List suites

List all available test suites in the Bugbug platform.

List tests

Retrieves a list of all available tests in the BugBug account.

Run test

Execute a test in BugBug and return the test run details.

FAQ

Frequently asked questions

With a standalone Bugbug MCP server, the agents and LLMs can only access a fixed set of Bugbug tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Bugbug and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Bugbug tools.

Yes, absolutely. You can configure which Bugbug scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Bugbug data and credentials are handled as safely as possible.

Start with Bugbug.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Bugbug tool your agent needs.Free to start.

Start building