SpinApp + built-in MCP for AI assistants

SpinApp bundles an “MCP server” so Cursor, Claude Desktop, or any MCP assistant can run dev commands inside the right containers.

Overview

SpinApp is a Laravel local dev product that embeds an MCP server for AI assistants. SpinApp lets AI assistants run development commands inside the correct Docker containers by connecting to the bundled MCP server and applying project rules.

MCP server per project

SpinApp includes a bundled MCP server with each project. You connect an MCP client (for example, Cursor or Claude Desktop) and then use SpinApp’s “Setup AI” to configure project rules and correct container context.

AI-driven actions provided by SpinApp

SpinApp provides specific MCP actions so an AI assistant can perform common development operations.

exec: run commands such as artisan, composer, and npm build/dev in app or queue containers
sql: run queries against a provisioned database
logs: view container output and Laravel log files
start/stop/status: control the full SpinApp environment
Audit log: SpinApp provides “an audit log of every tool call”

“Full stack, zero Compose” container wiring

SpinApp wires up containers for Laravel needs without requiring hand-written docker-compose.yml files. It provisions the containers required for the app, database, Redis, queue worker, and a web server, then exposes the app at the local hostname managed by SpinApp.

How AI assistant setup works

SpinApp’s workflow for AI assistant configuration includes these steps:

Connect your AI assistant via MCP.
Use “Setup AI” to write project rules.
Provide the assistant with correct container context.
Run tool calls (exec, sql, logs, start/stop/status) from the assistant.

What SpinApp reads from your Laravel repository

SpinApp can be pointed at a Laravel repository. It reads composer.json and detects:

PHP version
queue drivers
whether the project has a Vue or React frontend

SpinApp then provisions the environment accordingly, so AI tool calls run against the expected services.