Boost Laravel Package

Technical Evaluation

Architecture Fit

Laravel Boost (v2.4.8) remains a MCP (Model-Context-Plan) server tightly integrated with Laravel’s ecosystem, offering AI-powered local development assistance. The core architecture—leveraging Laravel’s service container, Artisan, and Blade/Livewire—remains unchanged. However, the pinning of laravel/mcp below 0.7.1 introduces a namespace stability constraint, ensuring backward compatibility with existing skills and configurations. This change mitigates risks from MCP’s breaking namespace renames but may limit access to future MCP features (e.g., v0.7.1+ improvements).

Integration Feasibility

• Laravel Projects: Unchanged (high feasibility).
• Monorepos: Still requires mcp_config_path (v2.4.2+), but MCP’s pinned version may affect skill portability if future MCP updates introduce breaking changes.
• Non-Laravel PHP: Low feasibility (unchanged).
• AI Dependency: Unchanged, but MCP’s stability now depends on an older version, which could introduce technical debt if MCP evolves significantly.

Technical Risk

1. MCP Version Lock-In:
   • New Risk: Pinning laravel/mcp <0.7.1 prevents access to potential fixes or features in MCP v0.7.1+. Future Laravel Boost updates may need to unpin this, requiring skill migrations.
   • Mitigation: Monitor MCP’s changelog for critical fixes. Plan for a controlled unpinning strategy if MCP stabilizes post-v0.7.1.
2. Skill Compatibility:
   • Skills relying on MCP v0.7.1+ features (e.g., new namespaces, APIs) will fail silently or throw errors until Boost unpins MCP.
   • Mitigation: Audit custom skills for MCP v0.7.1+ dependencies. Use composer why-not laravel/mcp:^0.7.1 to detect conflicts.
3. AI Dependency Risk:
   • Unchanged, but now compounded by MCP’s stability risks. Downtime in either Boost or MCP could disrupt workflows.
   • Mitigation: Reinforce fallback mechanisms (e.g., cached responses, local LLM integration).
4. Performance Overhead:
   • Unchanged, but MCP’s older version may lack optimizations in newer releases.
   • Mitigation: Benchmark performance with pinned MCP vs. hypothetical v0.7.1+ to justify future upgrades.

Key Questions for TPM

1. MCP Upgrade Strategy:
   • When should we evaluate unpinned laravel/mcp (e.g., v0.7.1+)? What’s the risk tolerance for skill breakage during migration?
2. Skill Future-Proofing:
   • How will we test custom skills against MCP v0.7.1+ before unpinning? Should we adopt a canary release for MCP updates?
3. AI Provider + MCP Resilience:
   • What’s the maximum acceptable downtime for AI/MCP failures? Should we implement circuit breakers for AI calls?
4. Laravel Version Alignment:
   • Will Laravel 14+ require MCP v0.7.1+? How will Boost’s MCP pinning affect compatibility?
5. Technical Debt Tracking:
   • How will we quantify the risk of pinning MCP? Should we log MCP-related issues in a separate Jira project?
6. Community vs. Curated Skills:
   • With MCP pinned, how will we prioritize skill updates? Will we deprioritize skills needing MCP v0.7.1+?

Integration Approach

Stack Fit

• Core Fit: Unchanged (Laravel 10–13, PHP 8.1+, Composer, Artisan).
• Extended Fit:
  • Livewire/Inertia: High (native skills).
  • Testing: High (Pest/PHPUnit skills).
  • Monorepos: Medium (requires mcp_config_path + MCP v0.7.1+ features may be unavailable).
• Non-Fit: Unchanged (Symfony, Lumen, non-Composer setups).
• New Constraint:
  • MCP v0.7.1+ Features: Skills using laravel/mcp:^0.7.1 will not work until Boost unpins the dependency.

Migration Path

1. Assessment Phase:
   • Audit MCP Dependencies: Run:

     composer why laravel/mcp
     composer why-not laravel/mcp:^0.7.1
     

   • Identify skills/custom code using MCP v0.7.1+ features (e.g., new namespaces like MCP\Contracts\v1).
2. Pilot Phase:
   • Install v2.4.8 in a non-production environment:

     composer require laravel/boost:^2.4.8
     php artisan boost:install
     

   • Test critical skills (e.g., Livewire, Eloquent) for regressions.
3. Gradual Rollout:
   • Phase 1: Deploy to teams using only MCP v<0.7.1 features.
   • Phase 2: Isolate teams using MCP v0.7.1+ skills for migration planning.
4. Fallback Plan:
   • Disable AI features (BOOST_AI_ENABLED=false) and use Boost as a context-only tool (e.g., guidelines without AI responses).
   • MCP Fallback: If MCP v0.7.1+ is critical, consider forking Boost to use the newer version temporarily.

Compatibility

Sequencing

1. Prerequisites:
   • Laravel 10+ with PHP 8.1+.
   • Composer installed.
   • (Optional) AI API keys.
2. Installation:
   • Update to v2.4.8:

     composer require laravel/boost:^2.4.8
     

   • Run:

     php artisan boost:install
     

3. Configuration:
   • Publish config:

     php artisan vendor:publish --provider="Laravel\Boost\BoostServiceProvider"
     

   • Critical Step: Verify config/boost.php for MCP-related settings (e.g., mcp_config_path).
4. Skill Validation:
   • List installed skills:

     php artisan boost:skills
     

   • Test MCP-dependent skills (e.g., php artisan boost:generate --skill=livewire).
5. MCP Dependency Audit:
   • For each custom skill, check:

     grep -r "MCP\\\\Contracts\\\\v1" ./skills/
     

   • Document findings in a migration tracker.

Operational Impact

Maintenance

• Dependency Updates:
  • MCP Pinning: Treat laravel/mcp <0.7.1 as a hard constraint. Plan for:
    • Quarterly audits of MCP’s changelog for critical fixes.
    • A dedicated ticket to track MCP upgrade readiness (e.g., "Boost: MCP v0.7.1+ Migration").
  • Boost Updates: Prioritize patches over minor versions until MCP is unpinned.
• Skill Management:
  • Block MCP v0.7.1+ Skills: Use boost:ignore for skills requiring newer MCP.
  • Skill Versioning: Tag skills with MCP compatibility (e.g., skill.livewire.mcp<0.7.1).
• AI Model + MCP Resilience:
  • Implement health checks for MCP and AI providers:

    // Example: Check MCP namespace availability
    if (!class_exists('MCP\Contracts\v0')) {
        Log::warning('MCP v0.7.1+ features unavailable; pinned to <0.7.1');
    }
    

Support

• Developer Onboarding:
  • Training Update: Add a 15-minute module on MCP pinning risks and skill compatibility.
  • Cheat Sheet: Include commands to audit MCP dependencies: