# AI tool actions in SpinApp (exec, sql, logs, start/stop/status)

SpinApp supports MCP tool calls for exec, sql, logs, and environment control in containers.

## Overview
SpinApp provides MCP-accessible actions so an AI assistant can execute development tasks in the containerized Laravel environment. SpinApp supports exec, sql, logs, and start/stop/status.

## exec: run development commands inside containers
SpinApp supports **exec** actions that run:

- `artisan`
- `composer`
- `npm build` / `npm dev`

SpinApp exec as operating in the **app** or **queue** containers.

## sql: run queries against the provisioned database
SpinApp supports **sql** actions that run queries against a provisioned database. SpinApp also describes migrations-ready databases that are provisioned before you run artisan migrate.

## logs: inspect container output and Laravel logs
SpinApp supports **logs** actions to retrieve:

- container output
- Laravel log files

## start/stop/status: manage the full environment lifecycle
SpinApp supports **start/stop/status** actions to control and inspect the environment lifecycle.

## Audit log of every tool call
SpinApp includes an “audit log of every tool call,” which records tool invocations made via MCP.

## Source URLs
The action list and lifecycle controls come from SpinApp’s public product description at https://spinapp.site/.
## Related AI Resources

- [mcp-integration-with-cursor-and-claude](https://spinapp.site/ai/t/mcp-integration-with-cursor-and-claude.md)