Weave Code
Laravel Vurb Laravel Package
vinkius-labs/laravel-vurb
Laravel Vurb is a lightweight package from Vinkius Labs that adds a focused, configurable utility to Laravel applications. It installs via Composer and follows standard Laravel conventions, making it easy to integrate into existing projects with minimal setup and no unnecessary complexity.
Transform any Laravel application into a production-grade MCP Server — zero TypeScript required.
Frequently asked questions about Laravel Vurb
- What is laravel-vurb and what does it actually do?
- laravel-vurb is a Laravel-native package from Vinkius Labs that lets an existing Laravel application expose tools, resources, middleware, state gates, and governance controls to AI agents over the Model Context Protocol (MCP). The intent is to keep your domain logic in PHP instead of rewriting an agent integration in TypeScript. It ships as a standard Composer package with a service provider, config publishing, and Artisan commands. The v1.0.0 assessment treats it as a first-pass evaluation rather than a production approval.
- How do I install laravel-vurb in a Laravel application?
- The documented path is three steps: run composer require vinkius-labs/laravel-vurb, then php artisan vurb:install to publish configuration and scaffold the initial setup, then php artisan vurb:serve to start the MCP surface. Laravel package auto-discovery means no manual service provider registration is normally required. After install, review the generated configuration and tool definitions before enabling anything beyond read-only access.
- Which Laravel and PHP versions does laravel-vurb support?
- Based on the v1.0.0 release notes, the package targets PHP 8.2 and above and Laravel 11, 12, and 13. That covers reasonably modern Laravel estates but excludes older Laravel 9 and 10 applications. Confirm the exact constraint in the package's composer.json before planning an upgrade path, and check whether a formal compatibility policy exists for future Laravel releases.
- Do I need Node.js installed to use laravel-vurb?
- Yes in practice. Despite the zero-TypeScript authoring experience, the package auto-manages a Node.js bridge process (Vurb.ts) launched through npx, so a Node runtime must be present. That means your deployment model includes both PHP and Node, plus the process lifecycle of the bridge. If your environment blocks dynamic npx execution, validate whether a pre-installed and pinned bridge is supported before committing.
- How do I run the laravel-vurb bridge daemon in Docker, Kubernetes, or Laravel Octane?
- This is one of the open questions in the v1.0.0 assessment rather than a documented answer. Auto-managed Node processes can orphan, restart-loop, or conflict with process managers, so you need to confirm how the bridge is started, monitored, and stopped in each target environment. For containers, verify whether the bridge runs as a supervised sidecar or an in-process child, and test Octane's long-lived workers carefully. A bounded pilot deployment is the safest way to answer this for your stack.
- What do FSM state gates, DLP redaction, and governance actually enforce in laravel-vurb?
- The release notes describe these as controls that constrain what AI agents can do and what data they can see, including state-machine gating of tool calls, redaction of sensitive payloads, and governance policies around agent access. Because these are high-value security claims, they must be validated against your real policies, bypass paths, and audit requirements. Confirm specifically whether policies can be scoped per tenant, role, tool, and environment. Treat the defaults as a starting point, not a compliance guarantee.
- What observability does laravel-vurb emit?
- The package advertises observability as part of its MCP surface, but the v1.0.0 assessment flags the specifics as unconfirmed. You should verify which signals are produced, such as logs, metrics, traces, or audit events, and which backends they can be shipped to. For regulated environments, confirm that tool invocations and policy decisions are captured in an audit trail you can retain and query.
- Which MCP transports and authentication methods does laravel-vurb support?
- This is listed as a key open question: it is not confirmed from the v1.0.0 release notes whether the package supports stdio, SSE, HTTP, or a subset of those. Equally important is how authentication and authorization are enforced on incoming agent connections and how sessions are handled. Resolve both before you commit to an integration contract, since transport choice drives your network and deployment topology.
- Is laravel-vurb production-ready at version 1.0.0?
- Not automatically. Strong test counts and coverage are positive signals, but they do not substitute for production hardening, load testing, and security review. The recommended rollout is to start in a non-production Laravel app, expose only low-risk read-only tools, then add authentication, DLP policy, and observability before enabling write-capable or state-changing tools. From there, move to staging with realistic agent clients and finally to a canary production deployment.
- How does laravel-vurb compare to building an MCP server in TypeScript?
- The core trade-off is language boundary versus runtime surface. Building in TypeScript keeps a single runtime if your team already operates Node, but it duplicates domain logic that already lives in your Laravel app. laravel-vurb keeps tools and policies in PHP and follows Laravel conventions, at the cost of running a Node bridge alongside PHP. It is the better fit for Laravel-centric teams that want the application to remain the source of truth, and a worse fit for teams that prohibit dynamic Node execution.
Weaver
How can I help you explore Laravel packages today?