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

Authorize the account and your agent has all 4 actions from the first conversation.
