Genai Laravel Laravel Package

Product Decisions This Supports

• Async/queued MCP tool execution: Supports product features where MCP tool calls cannot complete synchronously—long-running jobs, rate-limited third-party APIs, or human-in-the-loop approvals—by persisting request/delivery scheduling and claim-expiry state.
• Build vs. buy: Provides a Laravel-native scheduling, delivery, and claim/lease layer for MCP workflows. Teams can avoid building their own queue-backed request lifecycle, expiry handling, and database-schema management.
• Operational reliability roadmap: v0.2.6 is a data-integrity correction, not a feature release. It reduces the risk of MariaDB silently mutating scheduling timestamps during unrelated bookkeeping updates, which matters for SLAs, retry windows, and delivery guarantees.
• Database compatibility decisions: Explicit validation on MariaDB 10.6 and 11.4 supports adoption in teams standardized on MariaDB/MySQL. The migration strategy also informs whether to standardize on this package versus a custom queue abstraction.
• Release-management policy: Because the package is pre-1.0 and requires installations to run migrations after upgrade, PMs should treat adoption as a pilot with pinned versions, migration testing, and rollback rehearsal—not a set-and-forget dependency.

When to Consider This Package

Consider it when:

• You are building a Laravel application that exposes or consumes MCP tools and needs asynchronous request/delivery scheduling rather than purely synchronous calls.
• You need claim-receipt expiry semantics—leases that prevent duplicate processing or stalled work—without designing that state machine yourself.
• Your production database is MariaDB/MySQL, especially MariaDB 10.6 or 11.4, and you value tested migration paths.
• You can accept 0.x maturity: APIs and schemas may still change, and each upgrade may require running package migrations.
• You have a deployment process that can run migrations safely and verify schema changes in staging before production.

Look elsewhere when:

• You require a stable 1.0 API contract or long-term support guarantees.
• You cannot run package migrations during upgrades, or you need zero-downtime schema changes without operational coordination.
• You need recovery of scheduling values already overwritten by MariaDB’s implicit TIMESTAMP behavior—this release prevents future corruption but does not restore historical data.
• Your MCP usage is simple and synchronous, making a queue/scheduling layer unnecessary overhead.
• You are not on Laravel or need a database-agnostic scheduling layer outside this package’s supported stack.

How to Pitch It (Stakeholders)

For executives: This package lets our Laravel product run MCP tool calls asynchronously with managed scheduling and expiry, which is important for long-running AI-agent workflows and external API rate limits. The new v0.2.6 release is a reliability fix: it prevents MariaDB from silently changing scheduling timestamps during unrelated updates. That reduces the risk of missed delivery windows and inconsistent retries. It is a pre-1.0 dependency, so we should adopt it as a controlled pilot with pinned versions and migration testing rather than as a critical-path platform commitment.

For engineering: v0.2.6 adds a forward migration converting request/delivery available_at and claim-receipt expires_at to required DATETIME columns, removing MariaDB’s implicit first-TIMESTAMP auto-update behavior without changing stored values. Rollback keeps the corrected backward-compatible types. Existing installations must run package migrations after upgrading. CI covers six jobs, including MariaDB 10.6 and 11.4 migration lanes, PHP 8.4/8.5, formatting, and static analysis. The release is corrective only—no new features—and does not recover previously overwritten scheduling values. Pin the version, test migrations in staging, and confirm rollback behavior before production rollout.