LaraBeacon for Claude Code Claude writes the change. /larabeacon:scan checks the release.

A plugin that gives Claude Code a local MCP server and three skills for Laravel. Claude runs 69 free production-readiness checks on your machine, fixes what belongs to the current change, and tells you what is pre-existing or only true on this environment.

  1. 1 · Add the marketplace
    /plugin marketplace add Baer-Software/larabeacon-claude-plugin
  2. 2 · Install the plugin
    /plugin install larabeacon@larabeacon
  3. 3 · In a Laravel project

    Run /larabeacon:setup. It asks before adding the free Core package and runs the first scan. Needs PHP 8.2+ on the PATH. Technical docs

Example sessionIllustrative output of /larabeacon:scan after a feature change
> /larabeacon:scan

● larabeacon_scan (profile: local)
  ⎿ 3 findings

Related to this change
  critical  Queue timeout     config/queue.php:41
            retry_after 90 < worker timeout 120
  fixed     raised retry_after, reran the check

Pre-existing — listed, not touched
  critical  Mass assignment   app/Models/Invoice.php:14

Environment-specific
  minor     Config caching    not cached on a local run
  1. Scoped fixes. Each finding carries a location, evidence and an allowed scope. Claude fixes inside it and reruns only the affected check.
  2. No silent rewrites. Findings older than your change are reported to you instead of being fixed on the side.
  3. Honest about environments. A local pass or failure is not presented as proof about production.

Three skills, one MCP server.

Claude calls structured MCP tools instead of parsing terminal output. A short session hint reminds it to scan before finishing changes to configuration, security, queues, caching or deployment.

/larabeacon:scanLocal
Runs a scan with a profile (local, ci or production), sorts findings into related, pre-existing and environment-specific, previews deterministic fixes, applies those in scope, and reruns the affected checks and your tests.
/larabeacon:setupLocal
Reports Laravel, Core, Pro and Cloud status, asks before composer require --dev baer-software/larabeacon, runs the first scan and suggests a CI gate or a baseline for existing findings. It explains the Pro and Cloud setup without asking for tokens in chat.
/larabeacon:cloudCloud on request
Uploads a scan only when you ask, lists the project’s reports and summarizes which findings are new or resolved since the previous report, then offers to fix the new ones that relate to your work.

Scans stay on your machine unless you upload them.

The MCP server runs locally and delegates to your project’s own Artisan commands. It does not read .env or Cloud tokens. Finding text from your project is marked as data, so Claude does not follow it as instructions.

Stays on your machine

  • larabeacon_statusversions, Pro and Cloud status
  • larabeacon_scanprofiles, selected checks, baselines, fix previews
  • larabeacon_preflightwhich checks a profile would run
  • larabeacon_checkssearch the Core and Pro catalogue
  • larabeacon_baselineaccept existing findings with a reason

Only when you ask

  • larabeacon_cloud_uploadsends one report, same payload as --report
  • larabeacon_cloud_reportslists this project’s reports
  • larabeacon_cloud_reportopen, new and resolved findings

Cloud tools need a Pro project licence and Core 3.3 or newer. Read the Cloud data boundary.

Core finds the common risks. Pro runs 67 checks Core does not.

The plugin works fully with the free Core package. When Pro is not installed, Claude mentions once per session how many Pro checks did not run and which of them look relevant to your project. It never reports them as findings.

29
security checks
19
performance checks
19
reliability checks

A few of them

All 67 Pro checks

Cloud history is included with Pro

Every Pro project licence includes LaraBeacon Cloud. Ask /larabeacon:cloud latest and Claude reads which findings are new since the last report and which were resolved, without leaving the session.

Start with the free plugin. Upgrade when a project needs more depth.

Pro launch pricing starts at $79 per project, paid once, with Cloud included.