You capture the bug.
Click the Toado Chrome extension. Toado grabs the screenshot, console, network HAR, DOM snapshot, URL, and user agent, everything Claude will need to diagnose, and creates a ticket.
Open-source MCP server
Your visual bug tracker, wired into Claude Code .
Claude reads the ticket with read_ticket, fetches the screenshot with
get_capture_asset, reads the console errors, opens a branch, writes
the fix, comments on the ticket, and moves it to In Review. You approve.
Works with
- Claude Code
- Claude Desktop
- Cursor
- Cline
- Continue
- Any MCP-compatible agent
The loop
From screenshot to shipped fix, on one page.
Claude sees the ticket.
Your AI coding agent (Claude Code, Cursor, Cline, or any MCP client) hits the Toado MCP server and calls read_ticket, then get_capture_asset. The agent now has the image, the stack trace, and the network call that triggered it.
Claude writes the fix.
Same workflow you already use, Claude opens a branch, edits the code, runs tests. Toado stays out of the way on this step. Claude is just coding.
Claude updates the ticket.
Claude calls add_comment to drop in a summary, what changed, why, and a link to the branch, then calls move_ticket_to_column to advance it to In Review.
You approve.
You review the branch, merge if it’s good, and drop the ticket into Done. Or, if Claude missed something, leave a comment, Claude reads it and iterates. No copy-paste, no retyped repros.
MCP tools
Eleven tools. One envelope.
The Toado MCP server exposes everything Claude needs to triage, fix, and close a bug without a human translating anything.
read_ticket Fetch a ticket with its screenshot, annotations, console, and network capture.
list_tickets Query tickets by project, column, assignee, or label.
move_ticket_to_column Advance a ticket through your kanban flow after a fix or review.
add_comment Post a threaded comment with markdown, mentions, and code blocks.
assign_user Route a ticket to a specific team member or yourself.
edit_ticket_fields Rename, retag, re-prioritize, or restructure a ticket in place.
get_capture_asset Pull the raw screenshot (or annotated PNG) so Claude can see what you saw.
list_projects Enumerate projects so Claude knows where to file a new ticket.
create_ticket Let Claude open its own tickets for bugs it finds while fixing something else.
resolve_ticket Close a ticket with a resolution note when the fix is shipped.
get_audit_trail Retrieve who did what, when, for forensics or teammates stepping in.
Safe by default
Audited, rate-limited, Bearer-token auth.
Bearer-token auth
Per-user tokens, scoped to projects. Revocable from your Toado settings in one click.
Rate-limited
10 req/sec per token default, 1 req/sec on sensitive endpoints. Prevents runaway agents.
Fully audited
Every MCP call is logged: who, what tool, which ticket, when. Exportable for compliance reviews.
Open source
The MCP server is OSS. Audit it yourself, self-host if you need to, contribute if you want.
Open standard
Not locked to any one vendor.
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.
Feed Claude Code a bug.
First 40 tickets free. Install the Chrome extension, point Claude Code at the Toado MCP endpoint, and watch the loop close.
First time setting up? Watch the end-to-end walkthrough.
