Weave Code
Mcp Bundle Laravel Package
php-llm/mcp-bundle
A Symfony bundle that turns your app into a Model Context Protocol server for AI clients. Register tools, resources, and prompts with PHP attributes, then expose them over JSON-RPC transports such as stdio and HTTP.
Symfony integration bundle for Model Context Protocol (via php-llm/mcp-sdk)
Frequently asked questions about Mcp Bundle
- What is php-llm/mcp-bundle used for?
- It is a Symfony integration bundle for the Model Context Protocol built on php-llm/mcp-sdk. It lets you register tools, resources, and prompts with PHP attributes and expose them to AI clients over JSON-RPC transports such as stdio and HTTP. It is a thin transport and wiring layer rather than a standalone MCP implementation.
- Is there a Laravel service provider or publishable config for php-llm/mcp-bundle?
- No first-class Laravel support is documented; the package is structured as a Symfony bundle using Symfony DI and extension conventions. Laravel integration would likely require a service provider, publishable config, and container bindings, which should be validated in a short spike. Do not assume Laravel compatibility from the package name alone.
- How do I install php-llm/mcp-bundle with Composer?
- Install it with Composer, version-constrained alongside php-llm/mcp-sdk because the bundle is hard-pinned to SDK 0.1. There are no infrastructure prerequisites, but you should lock the bundle and SDK together as a pair rather than resolving them independently. In Laravel you would also need to confirm or build the service provider wiring.
- Which MCP transports does php-llm/mcp-bundle support?
- Release 0.1 exposes capabilities over JSON-RPC transports including stdio and HTTP, and it adds client transports so the package can also consume external MCP servers. It is still an open question whether client transport coverage includes all the transports you need or only a subset. Validate the specific HTTP and SSE behavior for your use case before committing.
- How do I register tools, resources, and prompts in php-llm/mcp-bundle?
- You register them using PHP attributes, and the bundle exposes them to AI clients through its MCP server wiring. The exact attribute API is part of the 0.1 public surface, which the maintainers have marked as work in progress. Keep an internal abstraction so attribute or SDK changes do not leak into application code.
- Is php-llm/mcp-bundle production ready?
- Treat it as early-stage: 0.1 is the first public release, carries an explicit WIP disclaimer, and has a single contributor across the merged PRs. There is no production usage data and no API documentation in the available evidence. It can be introduced behind a feature flag and an internal abstraction boundary, but not as a hardened dependency.
- What are the risks of the mcp-sdk 0.1 dependency pin?
- The bundle is hard-pinned to php-llm/mcp-sdk 0.1, so any SDK fix or MCP spec change needs a coordinated bundle release. That creates an external release gate and means you should never resolve the bundle and SDK independently. Lock them as a pair in Composer and confirm whether 0.1.x patch releases may include breaking changes.
- Does php-llm/mcp-bundle handle authentication for exposed endpoints?
- Authentication and transport security remain open questions; it is unclear whether the bundle enforces auth or merely permits you to add it. For HTTP or SSE endpoints you should assume you need your own auth layer until the bundle documents otherwise. Validate stdio versus HTTP exposure before putting it in front of real AI clients.
- What is the maintenance and bus-factor risk of php-llm/mcp-bundle?
- The available evidence shows a single author across all three merged PRs, which creates bus-factor and responsiveness risk for a dependency in the LLM integration path. There is also no stated path to 1.0 or deprecation policy in the available evidence. Ask the maintainer about roadmap, release cadence, and long-term ownership before committing.
- Are there tests or CI signals for php-llm/mcp-bundle, and what are the alternatives?
- The available evidence is limited to three merged PRs and a changelog, with no confirmed test suite or CI signal. Inspect the repository for tests and CI before adopting it. Alternatives include wiring php-llm/mcp-sdk directly or building a thin adapter yourself, which avoids inheriting the bundle release gate but adds integration work.
Weaver
How can I help you explore Laravel packages today?