$ the-wire · showcase
LARAVEL OPENS MCP TO THE NETWORK
By RepoJournal · Filed · About Laravel · Composed from the cited sources · methodology
3 people shipped this
The MCP client can now reach remote servers over HTTP, not just local stdio, fundamentally expanding what Laravel can do with external AI providers and tools.
Laravel's MCP integration just broke out of the localhost box [1]. You could only talk to local MCP servers via stdio before; now you're adding Streamable HTTP transport that lets you call remote servers with a simple Bearer token. This is the infrastructure play that matters. Meanwhile, the framework is tightening its grip on observability [2]: you can now detect when a job was actually skipped due to mutex contention instead of guessing. The Cache attribute is learning memoization [3], which pairs perfectly with Laravel 13's cache memoization feature for cleaner dependency injection. On the AI front, Claude Opus 4.8 just landed as Anthropic's smartest model [4], and Laravel AI bumped it immediately with zero breaking changes. Anthropic kept the API surface the same: same context window, same output limits, same adaptive thinking. Your `#[UseSmartestModel]` attribute just got smarter without requiring any code changes [5].
Action items
- → Integrate the new HTTP transport into remote MCP workflows if you're using hosted tool servers laravel/mcp [plan]
- → Update Laravel AI to v0.7.2 for Opus 4.8 support on your next deployment laravel/ai [plan]
- → Review mutex-heavy queue jobs to use the new skipped event indicator for better monitoring laravel/framework [monitor]
References
- [1] Add MCP client Streamable HTTP transport ↗ laravel/mcp
- [2] [13.x] Indicate an event was skipped ↗ laravel/framework
- [3] [13.x] Enhance Cache attribute to support memoization ↗ laravel/framework
- [4] Set claude-opus-4-8 as Anthropic's smartest text model ↗ laravel/ai
- [5] v0.7.2 ↗ laravel/ai
