Record a walkthrough, pin what’s broken, and say what you see. Toado turns it
into tickets with a transcript, the element, the screenshot, and a clip. Your agent
reads them with get_ticket, pulls the media with
get_capture_asset, writes the fix, and moves the ticket to In Review.
You approve.
“Button broken on settings page” sends an agent on a scavenger hunt. A Toado ticket sends it to the line. Here is what a walkthrough ticket hands over:
However you file it, the ticket arrives in one shape, so your agent does not need a different strategy per source. A recorded walkthrough adds a transcript; a pin adds an element anchor; a capture adds the console and network arrays.
Claude Code, Cursor, Cline, or any MCP client calls get_ticket for the transcript and context, then get_capture_asset for the screenshot and clip. It now has what you saw and what you said about it.
It calls start_work_on_ticket to record the branch, then works the way it already does: edits the code, runs the tests. Toado stays out of the way on this step.
It calls add_comment with a summary of what changed and why, plus a link to the branch, then move_ticket to advance it to In Review.
Review the branch, merge if it’s good, drop the ticket into Done. If the agent missed something, leave a comment. It reads it and iterates. No copy-paste, no retyped repros.
Everything an agent needs to find the bug, understand it, fix it, and close it without a human translating anything.
get_ticket Ticket details, transcript, capture summary, and available evidence. Fetch detailed console and network evidence only when needed.
get_devtools Read console, network, errors, and performance details on demand, with filters and pagination.
get_walkthrough_frame Retrieve a still frame from a walkthrough at a chosen time.
get_capture_asset A download URL for the screenshot, the annotated overlay, an attachment, or the walkthrough clip.
get_annotations The shapes you drew, as vectors with coordinates: circles, arrows, strokes, redactions, text.
list_capture_assets Every asset on a ticket, with kind and id, before downloading any bytes.
list_comments The thread so far, oldest first, so the agent knows what has already been said.
list_tickets Tickets in a project with filters. Defaults to active, non-archived.
search_tickets Full-text search across everything the token can see.
list_companies Every company the token can see, so the agent knows where it is allowed to work.
list_projects Projects in a company, or across all of them.
list_columns The workflow columns of a project. Required before a move.
list_members Members with ids, names, and roles, so assignments use real ids.
list_ticket_types The workspace’s built-in and custom ticket types and markers.
list_my_tickets The caller’s assigned work and tickets waiting for attention.
start_work_on_ticket Records the git branch the ticket is being worked on. Bundles related tickets under one branch.
add_comment Post a summary of the fix, attributed to the token and the person who owns it.
move_ticket Advance a ticket to In Review, or move it to another project in the same company.
bulk_move_tickets Move a batch of tickets at once, with a per-ticket result.
update_ticket Edit the title, description, or resolved state.
create_ticket File a bug the agent found while fixing something else.
assign_ticket Route a ticket to a teammate or to the token owner.
unassign_ticket Take someone off a ticket.
bulk_assign_tickets Assign one set of people to many tickets in one call.
archive_ticket Take a ticket off the board without deleting anything.
restore_ticket Bring an archived ticket back to the column it left.
record_fix Record what changed, the commit, and verification with the ticket.
send_to_jira Send a ticket to the mapped Jira project on Team and above.
unlink_jira_issue Remove a ticket’s Jira link without deleting the Jira issue.
find_similar_tickets Find related reports before starting another fix for the same problem.
mark_duplicate Connect a duplicate report to the ticket tracking the original problem.
request_info Ask for missing information and record that the ticket is waiting for it.
get_error_hotspots Find recurring captured errors across the accessible workspace.
get_page_hotspots Find the pages producing the most reports.
Pre-built skill New
The tools are the vocabulary. The skill is the habit. Download the Toado triage
skill from your settings, drop it in .claude/skills/, and Claude Code
picks it up on its own. After that you talk to it in plain English and it already
knows what your columns mean.
You say “fix t-lIMPHR”
You say “work the To Do queue for Toado Site”
You say “review the In Review tickets”
Requires Claude Code and the Toado MCP connector. Both are set up from the same settings area, and the skill is a single Markdown file you can read before you install it.
Per-user tokens, scoped to projects. Revocable from your Toado settings in one click.
10 req/sec per token default, 1 req/sec on sensitive endpoints. Prevents runaway agents.
Every MCP call is logged: who, what tool, which ticket, when. Exportable for compliance reviews.
Connect your agent on Free or a paid plan. Tools follow your permissions and plan allowances; Jira operations require Team or above.
Toado talks to your AI coding agent through the Model Context Protocol, an open standard. If it supports MCP, it supports Toado. As the AI tooling landscape shifts, your bug-fix loop comes with you.
Free plan, 40 tickets a month. Install the Chrome extension, point your agent at the Toado MCP endpoint, record a walkthrough, and watch the loop close.
First time setting up? Watch the end-to-end walkthrough.
