redberry/mcp-client-laravel
Laravel-native MCP client to connect to Model Context Protocol servers via HTTP or STDIO. Discover and call server tools, access structured resources and memory, and integrate AI/agent toolchains into Laravel apps (used by frameworks like LarAgent).
Architecture fit: Excellent fit for Laravel ecosystems. Leverages Laravel's service container, config publishing, and facades for seamless integration. Supports both HTTP and STDIO transporters with clear configuration patterns. Built as a framework-agnostic client but optimized for Laravel's conventions.
Integration feasibility: High. Simple composer install, config publishing, and minimal code changes required. Facade and DI patterns enable quick adoption in existing codebases. Documentation provides clear examples for common use cases (tools, resources, callTool).
Technical risk: Moderate. Low adoption (0 dependents, 13 stars) indicates limited real-world validation. Future-dated release (2025-11-07) suggests metadata inconsistency. STDIO transporters explicitly incompatible with php artisan serve – critical for local development. Limited test coverage evidence beyond basic unit tests.
Key questions: What MCP server versions are officially supported? How does the package handle transient network failures or server timeouts? Are there known compatibility issues with Laravel 12+? What is Redberry's formal support SLA for this package?
Stack fit: Native Laravel compatibility (Laravel 10-12, PHP 8.3-8.4). Uses standard Laravel patterns (config, DI, facades) without external dependencies beyond core framework components. Ideal for projects already using Laravel's ecosystem tools.
Migration path: Minimal for
How can I help you explore Laravel packages today?