NativePHP Super Stack: Web, Mobile, Admin, and MCP in One Laravel Kit

Most Laravel starters pick one surface. Admin panel, or API, or a web app, or mobile.

On 14 Sep 2026, NativePHP released Super Stack, which tries to ship all of them in one repo: web app, Filament admin, NativePHP Mobile 4 SuperNative, Sanctum API auth, and a Laravel MCP server for AI agents.

The idea came from Povilas Korop asking on X if anyone had built a starter like this. Shane's answer was "now we do."

The tagline is "Web + Mobile + Admin + API + Robots."

I wanted to understand what the kit actually ships, what SuperNative really means for the mobile piece, and where the MCP server sits in terms of production readiness.

What Is Actually in the Box

Super Stack is open source, MIT licensed by Bifrost Technologies LLC.

You can create a new Laravel app using it as a starter kit:

laravel new my-app --using=nativephp/superstack
composer install
cp .env.example .env
php artisan key:generate
php artisan migrate
php artisan native:install both --no-interaction

Then create a Filament admin user:

php artisan make:filament-user

And run the mobile app locally:

php artisan native:run

The stack includes:

For mobile packaging, there is a cleanup_exclude_files config that strips Filament, the MCP server, API surfaces, and Filament public assets from the device bundle. The docs specifically warn: do not strip vendor/* wholesale. That breaks mobile builds.

The repo is at github.com/NativePHP/superstack.

How SuperNative Fits Here

SuperNative is NativePHP's approach to sharing one Blade view between web and mobile.

You write Blade templates using nativephp/web-ui and nativephp/mobile-ui. On the web, those render as normal HTML. On a phone, NativePHP Mobile 4 renders the same view natively using device UI components.

The goal is to avoid maintaining separate mobile templates or writing platform-specific layouts.

In Super Stack, the home page uses this pattern. The same Blade file serves both browser users and NativePHP mobile users, but the output is different depending on the environment.

This is not revolutionary, but it is practical if your app leans web-first and the mobile version does not need complex native interactions beyond what the UI library covers.

For apps that need deep platform-specific behavior, offline sync, or heavy native UI, you would still compare this carefully with Flutter, React Native, or native stacks. But for Laravel companion apps or internal tools, the shared-Blade model is interesting.

The MCP Server and the Auth Problem

Super Stack includes a Laravel MCP server.

MCP (Model Context Protocol) is what lets AI coding agents interact with your Laravel app. Agents can inspect routes, query the database, read logs, and more.

The starter includes one sample tool called app-info, which returns the app version and installed package versions.

MCP routes live in routes/ai.php. You can run the server locally:

php artisan mcp:start superstack

Or expose it via POST:

POST /mcp/superstack

There is also an MCP inspector for testing:

php artisan mcp:inspector mcp/superstack

Here is the part that matters: Super Stack's MCP server has no authentication yet.

The official docs and README make this clear. The server works fine for local development and exploration, but it is not production-ready as-is.

Laravel MCP supports authentication via middleware, including Sanctum (token-based with Authorization: Bearer) or OAuth via Passport. The Laravel MCP docs explain how to add it.

So the starter gives you the MCP server, but you still need to wire auth if you plan to expose it beyond localhost.

When I Would Try It

I would try Super Stack if I worked at a Laravel shop and wanted to explore:

I would not start here if:

For prototypes, companion apps, or Laravel-heavy internal tools, this is interesting. For complex mobile products, I would still compare it with Flutter or React Native first.

Super Stack is not trying to replace every starter. It is trying to make one specific combination (Laravel web + Filament + SuperNative + MCP) faster to start.

My Take

Most starter kits are opinionated about one thing. Super Stack is opinionated about four things at once.

That makes it useful if those four things match what you are building. It also makes it heavier if you only wanted two of them.

The SuperNative model is practical for web-first apps that want a lightweight mobile companion. The MCP server is interesting for exploring AI agents with Laravel, but the lack of default auth means you still need to finish the wiring.

If I were starting a new Laravel project and wanted Filament, mobile, and agent tooling from day one, I would try this. If I only needed Filament, I would start thinner.

Super Stack does not solve every problem. But it does solve the specific problem of wanting all four surfaces wired in one repo from the start.

Sources