Nova Mcp Laravel Package

Product Decisions This Supports

• Whether to expose the admin surface to AI agents at all. The package turns existing Nova resources and tools into MCP tools, which forces an explicit decision about which resources are agent-visible, which are read-only (list/get) versus write-capable (create/update/action execution), and which staff or clients may call them.
• Build vs buy for internal agent tooling. The alternative is a bespoke MCP server wrapping your Eloquent models and business actions. This package is the "buy" option at the cost of a composer dependency, so the comparison is roughly weeks of internal plumbing plus ongoing maintenance versus adopting a pre-1.0 dependency.
• Roadmap sequencing and platform prerequisites. v0.2.0 requires Laravel 12/13, PHP 8.3+, Nova 5, and Laravel MCP 1.x. Adopting it is therefore a scheduling commitment to those upgrades — useful as a forcing function for the platform-upgrade workstream, and a blocker if you're still on Laravel 11.
• Model-layer architecture. The release verifies executing a Nova catalog tool through the Laravel AI SDK adapter (Laravel AI v1.2.3) while keeping Laravel AI optional. That de-risks standardizing on Laravel AI as your abstraction rather than wiring provider SDKs directly, and it lets you keep the MCP surface independent of the model layer.
• Scope of the "agentic ops" bet. This is a realistic spike candidate — support consoles, ops copilots, internal data lookup — but not a customer-facing surface. Treat it as a timeboxed prototype that produces a go/no-go on agent access to admin data before you fund a bigger initiative.
• Guardrail requirements as product requirements. Authorization, audit logging, rate limiting, and tenant isolation are not provided here; they live in Nova policies and your app. Deciding they're required is a product decision that materially changes the integration cost.

When to Consider This Package

Consider it when:

• You're on Laravel 12 or 13, PHP 8.3+, with a licensed Nova 5 installation. Laravel 11 and Laravel MCP 0.9 are hard-dropped in v0.2.0, so older stacks are blocked until upgraded, not merely untested.
• Your Nova resources already mirror the business objects an agent would want to touch. The package is largely a bridge, so its value scales with how much of your domain is already expressed in Nova.
• You need a fast internal prototype — staff-facing assistants, admin lookups, routine operational actions — and want to speak the MCP standard rather than ship a bespoke API.
• Your MCP client is already in place (Claude Desktop, IDE agents, or a custom agent runtime) and you'd rather standardize on Laravel MCP 1.x than maintain a custom protocol shim.
• You want a small, actively maintained adapter: v0.2.0 runs 59 tests and 187 assertions across six Laravel 12/13 × PHP 8.3/8.4/8.5 combinations, including the AI adapter path, with repeatable CI.

Look elsewhere or wait when:

• You're on Laravel 10/11 or Nova 4 — there is no supported path without upgrading the platform first.
• You don't already hold a Nova 5 license. It's a hard prerequisite and a real incremental cost if it would be bought solely for this.
• You need production-grade guarantees. This is 0.x software that has already shipped breaking changes, with no published deprecation or LTS policy. Pin versions and budget for churn.
• You require fine-grained authorization, audit trails, or multi-tenant isolation out of the box. That responsibility sits with Nova policies and your application, and is unproven here.
• You aren't a Nova shop. A plain Laravel MCP server is a smaller, more portable dependency with less coupling to Nova's release cadence.
• You need a stable public contract for external consumers. A 0.x package is a poor foundation for third-party integration promises.
• Single-maintainer bus factor matters to you. Vendor-alignment with the Nova ecosystem helps, but it's still one maintainer and a small surface.

How to Pitch It (Stakeholders)

For executives: Nova already models our admin data and the actions we perform on it. This package exposes those resources to AI assistants over MCP — the emerging standard protocol — with no bespoke integration to build or maintain. Cost is a composer dependency plus a Nova 5 license we likely already hold; upside is agent-assisted operations: faster support lookups, routine admin actions driven by assistants, and a cheap, evidence-based way to test the agentic roadmap before funding it. Two caveats to state plainly: it's pre-1.0 software requiring Laravel 12/13 (Laravel 11 apps must upgrade first), and any tool we expose to an agent is a real, permissioned action on real data — so access control and audit logging are product decisions, not configuration details.

For engineering: The package is a thin adapter mapping Nova resources and tools onto Laravel MCP 1.x (verified against v1.0.2). Laravel AI is optional and verified end-to-end by executing a Nova catalog tool through the AI SDK adapter against v1.2.3. v0.2.0 dropped Laravel 11 and MCP 0.9, so the upgrade path is a prerequisite, not a runtime concern. Test posture is solid for a 0.x package: 59 tests / 187 assertions across Laravel 12 and 13 on PHP 8.3, 8.4, and 8.5, plus repeatable Amp CI with cached PHP and JavaScript dependencies and in-memory Nova package authentication. Recommendation: timeboxed spike on a non-production Nova instance, pin to 0.2.x, gate write-capable tools behind Nova policies with request logging, and assume interface churn until a 1.0 lands.