Bugbug MCP integration
Triggers a named browser test, reports its status, timing and errors, and lists what the account actually covers.
4actions available
Three actions you can hand over today
Every action runs live through MCP. Nothing to build, nothing to maintain.
Get test run details
Lyro retrieves detailed information about test runs from BugBug. Agents see exact pass/fail results and timing for investigation.
List tests
Lyro retrieves a list of all available tests. Agents find which tests exist without leaving the chat.
Run test
Lyro executes a test in BugBug and returns results immediately. Customers verify fixes without manual test platform access.
How businesses use Bugbug + Lyro
Each card is one request a support team gets, and the Bugbug actions Lyro runs to close it.
Trigger a test run and report the outcome
Lyro starts the requested test with the browser, device and viewport it should use, then reads the run back and returns the status, timing and any error detail with a link to the full results.
Run TestGet Test Run DetailsAnswer what the test account already covers
Lyro lists the tests in the account with their active and recording status, and the suites they are grouped into, so a question about coverage is answered without anyone opening BugBug.
List TestsList Suites
How it works
Get started in 3 steps
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Bugbug actions it has and picks the ones a request needs.
Connect Bugbug
Authorize the Bugbug account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Bugbug actions that close it and chains as many as the request needs.
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free
Bugbug · Lyro
What can you do in Bugbug without me setting anything up?
These, right away:
- Get test run details
- List suites
- List tests
Great, let's start with the first one.
FAQ
Everything else about Bugbug
Setup, permissions, and the limits of what Lyro can do inside Bugbug.
No. The toolkit exposes four actions - Run Test, Get Test Run Details, List Suites and List Tests - so Lyro can start a test and report on it but cannot record, author or modify one. Test authoring stays in BugBug.
Every action available in Bugbug
All 4 actions your agent can call on Bugbug, straight from the live MCP connection.
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.
The tools Bugbug sits next to
Same connection, same setup. Pick the next one your team already uses.
Blazemeter
Starts and stops performance tests, uploads test files, reports run summaries, and schedules the API monitoring that catches regressions.
CrowTerminal
Ingests creator analytics in bulk, explains how a client's memory changed, validates proposed updates against history, and reports service health.
GitLab
Reads issues, merge requests, and pipeline jobs, files new issues, cuts branches, and keeps project membership current.
New relic
Runs NRQL queries and reads the numbers back, checks open alert violations, wires notification channels onto policies, and marks deployments on the timeline.
Screenshot fyi
Turns a URL raised mid-conversation into a rendered screenshot, with capture options chosen at the moment of the request.
Uptimerobot
Reports live monitor status, separates planned maintenance from real outages, and adds monitors and status pages on request.
Ready to connect Bugbug?
Authorize the account and your agent has all 4 actions from the first conversation.