AI and MCP

Your agent can read your errors

LaraBug ships an MCP server. Point Claude, Cursor or any MCP client at it and your agent can list your applications, read a stack trace, pull the latest occurrence and close an issue when it has fixed it.

✔︎ 14-day free trial ✔︎ No credit card required

myawesomeai · ~/sites/intilli.be

* Welcome to MyAwesomeAI!

/help for help, /mcp for your servers

cwd: ~/sites/intilli.be

mcp: larabug connected · 11 tools

> Checkout has been failing since this morning. What happened?

larabug - list_issues (MCP)(status: "open")

3 open issues, newest first

larabug - get_latest_occurrence (MCP)(issue_id: "4821")

SQLSTATE[40001]: Deadlock found when trying to get lock app/Services/StockReserver.php:142 · POST /checkout

A deadlock in StockReserver::reserve() since the 09:12 deploy: two checkouts lock the same stock rows in a different order.

> Fix it and open a PR.

Update(app/Services/StockReserver.php)

+ sort($ids);   Stock::whereIn('id', $ids)->lockForUpdate()->get();

Bash(gh pr create --fill)

#318 Fix the checkout deadlock in StockReserver

larabug - add_issue_comment (MCP)(issue_id: "4821", body: "Fix in #318")

Comment added

larabug - update_issue_status (MCP)(issue_id: "4821", status: "fixed")

Marked fixed

Sorted the ids before the lock and opened #318. The issue links to it and is marked fixed; if the deadlock comes back, LaraBug reopens it.

>
AI and MCP

What your agent can do

All features

Read-only until you say otherwise

Access is a personal token with scopes, revocable from your profile and limited to the applications its owner can already see. Read lets an agent browse; write is a separate scope for status, priority, assignee, snooze and comments, each recorded on the issue's trail, so an agent never deletes anything. It works with any MCP client.

Keep reading

Catch the next bug before your users do

Two minutes to install, a free plan that stays free, and your data kept in the EU. Teams have trusted LaraBug with their Laravel errors since 2016.