Laravel Codebase Introspection
CapevaceLABSCO SUMMARY
Read the banner, then decide.
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.
What it is
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.
What you get
- 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, andenv()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 incroft.php, then restart the server or ask the client to relist
Requirements
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.
Setup effort
One command — composer require usecroft/laravel --dev
USE CASES
01
Stopping the assistant inventing route names
Let it list and filter the project's real routes rather than reconstructing them from the controllers it has seen.
02
Answering a question about the schema
Read tables, columns, indexes and foreign keys directly, and query the database read-only when reading the structure is not enough.
03
Debugging from the log
Pull the last entries into the conversation instead of switching to a terminal and tailing a file.
04
Checking configuration without exposing secrets
List config() keys in dot notation, and env() keys by name only.
BEFORE YOU INSTALL
What to know first
Requires
A Laravel 10, 11 or 12 project on PHP 8.1+, with Composer
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
composer require usecroft/laravel --devMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"croft": {
"command": "./artisan",
"args": [
"croft"
]
}
}
}
