Weave Code
Mcp Bundle Laravel Package
symfony/mcp-bundle
Symfony integration bundle for the Model Context Protocol, built on the official mcp/sdk. Exposes tools, prompts, and resources as an MCP server over HTTP or STDIO. Experimental, with resource templates awaiting SDK support.
Symfony integration bundle for Model Context Protocol (via official mcp/sdk)
Frequently asked questions about Mcp Bundle
- Can I use symfony/mcp-bundle in a Laravel application?
- It is a Symfony bundle, not a native Laravel package, so you cannot drop it in without adaptation. You can install it via Composer, but you will need custom service providers, routing bridges, and middleware to replace Symfony's HttpKernel, EventDispatcher, and Validator assumptions. Treat it as a reference implementation for MCP server behavior rather than a ready-made Laravel integration.
- How do I install symfony/mcp-bundle for Laravel?
- Run composer require symfony/mcp-bundle in your Laravel project. Because it expects Symfony's bundle registration and container conventions, you will likely need to manually register its services in AppServiceProvider or a dedicated McpServiceProvider. Also pin the mcp/sdk version in composer.json, since the bundle is experimental and SDK changes may break compatibility.
- Does symfony/mcp-bundle support Laravel 11 or Laravel 12?
- The bundle is built for Symfony and does not declare Laravel version support. It can coexist in a Laravel 11 or 12 codebase via Composer, but official compatibility is not provided. You must test adapter layers yourself, especially around routing, dependency injection, and HTTP transport.
- What MCP capabilities does symfony/mcp-bundle expose?
- It exposes MCP tools, prompts, and resources as a server over HTTP transport and STDIO. Resource templates are implemented but await support in the official mcp/sdk. That means tools and prompts are the safest features to prototype in a Laravel context.
- Is symfony/mcp-bundle production ready for Laravel?
- No. The bundle is explicitly experimental and not covered by Symfony's backward compatibility promise. For Laravel production use, you should pin versions, isolate MCP endpoints behind middleware, and avoid relying on unsupported resource templates. Start with non-critical AI workflows and monitor SDK changes closely.
- How do I wire MCP tools into Laravel routing with this bundle?
- The bundle relies on Symfony routing and HttpKernel, so you cannot use its routes directly in Laravel's router. A practical approach is to create a Laravel route group such as Route::post('/mcp/{tool}', [McpController::class, 'invoke']) and forward requests to an MCP handler or HTTP transport. You will also need auth and rate-limiting middleware to replace Symfony's listeners.
- What Laravel components replace Symfony dependencies in symfony/mcp-bundle?
- Laravel's Illuminate\Http\Request can replace HttpFoundation, Illuminate\Events\Dispatcher can replace EventDispatcher, and Laravel's Validator facade can replace ValidatorInterface. However, you must write adapters because the bundle's services are type-hinted against Symfony contracts. Expect to bridge HttpKernel, routing, and bundle extension loading manually.
- Can symfony/mcp-bundle handle multi-tenant context for Laravel SaaS apps?
- MCP's context annotations can propagate values like tenant_id or user_tier, which aligns with Laravel multi-tenancy patterns such as Stancl/Tenancy. But the bundle does not provide Laravel-specific tenancy integration, so you must inject context through middleware or a custom MCP client wrapper. Validate that your chosen MCP transport carries that context end to end.
- What are alternatives to symfony/mcp-bundle for Laravel MCP servers?
- There is no official Laravel MCP bundle from Symfony, so developers often evaluate the official mcp/sdk directly or build a thin Laravel wrapper around it. You can also use Laravel's HTTP client to call external MCP servers instead of hosting one inside your app. Compare maintenance cost, SDK stability, and whether you need STDIO versus HTTP transport.
- How do I test symfony/mcp-bundle integration in a Laravel test suite?
- Write feature tests that hit your Laravel MCP routes with HTTP assertions, and unit test any adapter classes that translate Laravel requests into MCP payloads. Use mocked mcp/sdk transports to avoid real STDIO or network calls. Because the bundle is experimental, include contract tests that fail when the SDK changes tool or prompt schemas.
Weaver
How can I help you explore Laravel packages today?