mcp-artisan
Related Servers
Alternatives to mcp-artisan
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to introspect a Laravel application's routes, models, controllers, migrations, and more through the Model Context Protocol, running locally via php artisan commands and filesystem scanning.10 npmMIT
- AlicenseNot gradedqualityBmaintenanceSecure bridge between AI clients and local Laravel projects, enabling AI to run artisan commands, read logs and routes, and safely read/write code with layered security protections.7 npmMIT
- AlicenseAqualityAmaintenanceEnables AI assistants to perform read-only introspection of Symfony applications, exposing routes, controllers, services, entities, database schema, migrations, logs, and more via MCP tools.554 npmMIT
- FlicenseBqualityDmaintenanceProvides LLMs with safe, read-only access to local codebases for searching, reading files, and finding function definitions. All source code remains local, ensuring privacy while enabling AI assistants to explore project structures and functionality.4-
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with secure, read-only file system access to analyze and understand project codebases, enabling multi-repository context aggregation and cross-project code tracing.5MIT
- AlicenseNot gradedqualityAmaintenanceProvides AI coding agents with ground truth about a Rails app via 45 read-only tools covering schema, models, routes, controllers, views, jobs, and conventions, working over MCP or CLI and functioning even when the app cannot boot.158MIT
TDQS
Scored across 8 tools
Each tool targets a distinct aspect of a Laravel application: routes, migrations, models, jobs, config, dependencies, and a summary. describe_route is the only detailed view of list_routes, which is a common and clear pattern. No two tools overlap in purpose.
Most tools follow a verb_noun snake_case pattern (list_routes, list_migrations, config_get). However, composer_deps and project_summary are noun-first, deviating from the otherwise consistent verb-first style. The naming is still predictable and readable.
With 8 tools, the set is well-scoped for a Laravel artisan inspection server. Each tool covers a meaningful portion of the domain without redundancy or bloat. The count feels appropriate for orientation and common development tasks.
The surface covers core Laravel inspection needs: routes, migrations, models, jobs, config, and dependencies. Minor gaps exist, such as lack of direct controller listing or cache/event inspection, but these are workarounds and not critical for the stated purpose of cheap orientation.