- What is chrisvasey/statamic-boost and what does it do?
- Statamic Boost is a developer-experience package that extends Laravel Boost with Statamic-specific MCP tools and AI guidelines. It gives AI coding assistants context about collections, blueprints, fields, fieldtypes, and Antlers templates so generated addon and site code is more accurate. It is a context and tooling layer, not an application-runtime dependency.
- Is statamic-boost a production dependency or dev-only?
- Treat it as require-dev. The package is a developer-experience and agent-context layer, so it should not be installed as a production dependency. Verify that the service provider self-registers and that no MCP server or tools are reachable in production before you ship. The safest adoption path is a require-dev install plus a review of what loads at boot.
- Which Laravel, Statamic, Boost, and PHP versions does statamic-boost support?
- The 1.3.x line targets Laravel Boost 2 with laravel/mcp ^1.0.1 and Statamic 5 or 6. CI verifies PHP 8.5, Laravel 13, Statamic 6, and Boost 2, but that matrix is tested on fresh installs rather than guaranteed as a supported combination. Statamic 4 and Boost 1 are out of scope, so upgrade those first. Confirm the PHP floor against your own estate because 8.5 is CI-verified, not required.
- How do I install chrisvasey/statamic-boost in my Laravel Statamic project?
- Install Laravel Boost 2 and laravel/mcp ^1.0.1 first, confirm the app boots without the new package, then add chrisvasey/statamic-boost:^1.3 as a dev dependency with a committed lockfile. Run the package installer and capture the git diff before and after. Only then template the change across additional repositories.
- Does the statamic-boost installer overwrite my existing Laravel Boost configuration?
- Version 1.3.0 fixed Statamic-environment preservation in the Boost configuration, so the earlier clobbering failure class is addressed. The installer still mutates your existing Boost configuration, so treat it as a config-mutating migration rather than a drop-in. After running it, explicitly verify the Statamic environment value survives a Boost config rebuild and review the resulting diff.
- Is the statamic-boost installer idempotent, and what happens if I re-run it?
- Full idempotency is not proven by the release notes alone, so test it yourself. Run the installer, then run it a second time and inspect whether the re-run produces a clean or dirty git diff. Also induce a bad config to confirm installer failures now surface instead of passing silently.
- Does statamic-boost need network access, or does it bundle offline Statamic docs?
- The package bundles offline Statamic 5 and 6 documentation with licenses attached, and fieldtype discovery runs against your own site. Doc freshness depends on an automated upstream sync pipeline, so a lagging pipeline can yield outdated Antlers or fieldtype guidance. Confirm whether anything in the install path still needs network access before adopting in an air-gapped environment.
- What MCP tools does statamic-boost add for AI coding assistants?
- It adds Statamic-aware MCP tools and AI guidelines covering collections, blueprints, fields, fieldtypes, and Antlers templates, plus an offline documentation bundle. The goal is to reduce guesswork when an assistant writes Statamic addon or site code. Confirm which tools are exposed and whether any could be reachable outside development environments.
- How do I test that statamic-boost tools work with my blueprints and Antlers templates?
- Exercise the generated tools on a real site rather than a fixture: run fieldtype discovery against a non-trivial fieldset and check Antlers examples against your actual templates. Re-run the installer to prove idempotency, then break the config deliberately to confirm errors surface. Keep ^1.3 pinned with a committed lockfile so upgrades are reviewed.
- What are the risks of using statamic-boost, and what alternatives exist?
- Main risks are upstream pin drift across Laravel Boost, laravel/mcp, and Statamic, a bleeding-edge CI matrix, high release noise from weekly automated minor releases, and a single-maintainer bus factor with an unstated package license. The alternative is hand-written AI guidelines or Laravel Boost alone, which gives no Statamic-specific context. Verify the license and security disclosure process before adoption, and avoid it entirely if your team does not run an MCP-capable assistant.