- What is hemp/nova-mcp?
- hemp/nova-mcp is a Composer package that exposes Laravel Nova admin panel tools and resources to AI agents over the Model Context Protocol. It integrates Laravel Nova with Laravel MCP so compatible clients can discover and call Nova capabilities through standardized MCP endpoints. It is aimed at teams that want AI assistants to query and manage a Nova application from MCP-compatible clients.
- What are the installation requirements for hemp/nova-mcp?
- Version 0.2.0 requires Laravel 12 or 13, PHP 8.3 through 8.5, Laravel MCP 1.x, and a licensed Laravel Nova 5 installation. Laravel AI 1.2.3 is optional and only needed for AI SDK adapter interoperability. Confirm these Composer constraints against your host application before installing.
- Does hemp/nova-mcp work with Laravel 11?
- No, the v0.2.0 release requires Laravel 12 or 13 and is not viable for Laravel 11 estates. Existing v0.1.0 users on Laravel 11 should not upgrade in place until the application platform and MCP dependencies are upgraded. Pin v0.1.0 temporarily or defer v0.2.0 until Laravel 12+ and Laravel MCP 1.x are in place.
- Do I need a Laravel Nova 5 license to use hemp/nova-mcp?
- Yes, hemp/nova-mcp requires a licensed Laravel Nova 5 installation. Nova licensing and authentication coupling are part of the operational risk to validate, especially in non-production environments. Confirm Nova license enforcement and authentication behavior before exposing MCP endpoints broadly.
- Is Laravel AI required to use hemp/nova-mcp?
- No, Laravel AI is an optional dependency and is only relevant for teams that need AI SDK adapter interoperability. The core value comes from exposing Nova tools and resources through Laravel MCP. If you do not use Laravel AI, keep it out of the dependency graph and validate core MCP behavior independently.
- How do I install hemp/nova-mcp in a Laravel application?
- Install it as a Composer package after upgrading to Laravel 12/13, PHP 8.3+, Laravel MCP 1.x, and Nova 5. Configure Nova authentication and MCP endpoint exposure in a non-production environment first, then run discovery and tool-execution tests. Only roll out after client compatibility checks and environment-specific acceptance tests pass.
- Which MCP transports and authentication methods does hemp/nova-mcp support?
- The package builds on Laravel MCP 1.x, so supported transports and authentication are governed by your Laravel MCP configuration. Review the Laravel MCP documentation and test discovery plus authentication for your chosen transport before production. The vendor assessment flags transport and auth support as key questions to validate in your own environment.
- Can I upgrade hemp/nova-mcp from v0.1.0 to v0.2.0 in place?
- Not if your application is still on Laravel 11 or Laravel MCP 0.9. v0.2.0 introduces breaking platform constraints, so upgrade Laravel, PHP, and Laravel MCP first, or pin v0.1.0 until those prerequisites are in place. Treat the upgrade as a planned migration event rather than a routine patch.
- How do I control which Nova tools and resources AI agents can access?
- Exposure is centered on Nova tools and resources, but tool and resource granularity plus authorization are identified as areas to validate. Use Nova authorization and per-client MCP boundaries, and test exactly which catalog entries each client can discover and call. Apply rate limits and caching where safe before granting broad agent access.
- Is hemp/nova-mcp production-ready and how is it tested?
- The package is still v0.x, so expect active churn and treat breaking changes as planned upgrade events. The vendor reports 59 tests and 187 assertions across six Laravel and PHP combinations, but that is vendor evidence rather than a substitute for your own acceptance tests. Validate Nova licensing, MCP discovery, tool execution, and optional Laravel AI adapter behavior in your environment before production use.