The author states plainly that Croft is finished and became Laravel Boost — so anyone starting today should look there first. What is here still runs, and the idea it demonstrates remains the right one: an assistant that can read your actual routes, schema and config keys stops guessing at names, and the custom-tool base class means project-specific knowledge can be exposed the same way.
A Laravel package that turns `php artisan croft` into an MCP server for the project it is installed in, deliberately scoped to things that are useful locally. Its author says Croft is no longer maintained and eventually became Laravel Boost, and points people there instead.
- Database access, read-only or read-write, plus schema inspection you can filter — tables, columns, indexes, foreign keys
- Routes listed and filtered, and the project's artisan commands listed
- The last N log entries, read without leaving the conversation
- `config()` keys in dot notation, optionally with their values, and `env()` keys listed without leaking their secrets
- A URL screenshot tool, and conversion of a relative path into an absolute URL
- Current date and time
- Your own tools: extend `Croft\Feature\Tool\AbstractTool`, register the class in `croft.php`, then restart the server or ask the client to relist
A Laravel project. `composer require usecroft/laravel --dev`, then `php artisan vendor:publish --tag="croft-config"` for the config file and `php artisan croft:install` to add it to your editor. The MCP client runs `./artisan croft`, and the recommended pattern is committing a `.cursor/mcp.json` alongside the project so the whole team gets it. Note the direction of travel first: the author's own banner sends new users to Laravel Boost.
One command — composer require usecroft/laravel --dev