Skip to content

Release status and versions

Laravel package

ardanayatraa/laravel-mcp-hub 1.0.2 is the current stable release. It hides a single value that looks personal instead of failing a page, applies the Hub 1.1 privacy rules, and checks the Hub's version. 1.0.1 was published November 9, 2026. Install it with ^1.0, without an @alpha flag or -W.

Release and verified ZIP · Packagist · Version 1.0.1 CI

Version 1.0.1 installs on a fresh Laravel 13 application, which ships Guzzle 8, and its Hub calls work without listing the application in the Hub's ALLOWED_ORIGINS. It also removes a PHP 8.2+ deprecation, gives the package's rate limits their own counters, and renders tables and lists in chat answers. No migration or configuration change is required; see the Laravel upgrade guide. All 16 release jobs passed: 13 PHP/Laravel combinations, PostgreSQL, chat assets and distribution checks. The package suite collects 119 tests with two opt-in tests; PostgreSQL checks run separately. CI results are not a production capacity benchmark.

1.0.0, the first stable release (November 3, 2026), added pairing, SQL nonces, CRUD proposals, settings and chat, the Gateway SDK and private exports. Release · Version 1.0.0 CI

Tested compatibility

Laravel PHP
5.8 7.2, 7.4
6 7.2
7 7.2
8 7.3
9 8.0, 8.2
10 8.1
11 8.2
12 8.2, 8.4
13 8.3, 8.4

Effective PHP requirements depend on the host framework and dependencies. The matrix tests the reference patches listed in the package README, rather than every patch combination. Package compatibility does not restore expired upstream security maintenance.

Hub server

MCP Hub 1.1.0 is the current release. It adds monitoring, sealed backups, settings in the admin UI, administrator password changes and reset links, fewer false privacy matches, and reports its version to connected applications. See What changed.

Laravel package MCP Hub
1.0.2 1.1.0 or later (php artisan mcp-hub:doctor --online checks it)
1.0.0 – 1.0.1 Hubs with pairing, from November 2026

Hub documentation follows the Python edition on main. The Laravel package's stable version does not automatically become the server's release number. Review the server commit, database schema, and API contracts before a coordinated upgrade. The JavaScript edition on mcp-js is outside this operations guide.

Keep the host application's lock file and follow the Laravel upgrade guide. Release corrections use a new patch version; published tags are not moved.