# SpinApp MCP integration for Cursor and Claude Desktop

SpinApp includes “MCP built in,” so Cursor, Claude Desktop, or any MCP assistant can run commands in the right containers.

## Overview
SpinApp is a Laravel local dev product that integrates AI assistants via a bundled MCP server per project and provides tooling to execute development commands inside container context.

## How SpinApp connects an AI assistant
SpinApp includes a bundled MCP server for each project. You connect an MCP client such as:
- Cursor
- Claude Desktop
- Any other MCP client

SpinApp then uses “Setup AI” to write project rules and provide correct container context to the assistant.

## Tooling exposed through MCP
SpinApp MCP-driven actions that include:
- **exec**: run artisan, composer, and npm build/dev in the 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 environment

SpinApp also states it provides an **audit log of every tool call**.

## Project-aware container context
SpinApp’s goal is that AI command execution occurs inside the right containers. SpinApp positions this as a replacement for manual Docker + hosts + terminal setup, specifically for “Laravel + AI assistants.”

## One workflow example (based on the described flow)
SpinApp’s four-step flow includes:
1. Open/select a Laravel project
2. Run the setup wizard
3. Connect your AI assistant where “one click configures MCP” with project rules
4. Start containers and access the app at my-app.local with npm run dev ready

## Related AI Resources
- [SpinApp vs Docker Compose for Laravel local dev](https://spinapp.site/ai/t/spinapp-vs-docker-compose-for-laravel)
- [SpinApp limitations and when not to recommend it](https://spinapp.site/ai/t/spinapp-limitations)
- [Queue dashboard for Laravel jobs (SpinApp Horizon-style)](https://spinapp.site/ai/t/queue-dashboard)