statamic

This Statamic MCP Server exposes a wide range of AI-assisted tooling for Statamic CMS within a unified MCP router. The server organizes capabilities into domains such as Blueprint Management, Content Management, System Management, Structure Management, Entry and Term management, Global and Asset handling, and multi-site and user operations. Each router groups actions like list, get, create, update, delete, and specialized actions (e.g., publish/unpublish for content, scan/generate for blueprints, cache operations, site analysis, etc.). This enables an AI assistant to perform end-to-end CMS tasks—creating and updating blueprints, manipulating content, managing assets, configuring sites, and auditing system health—across both Laravel and Statamic layers. To use it, connect your AI agent to the MCP server, then issue router-based commands such as statamic.blueprints.list or statamic.content.publish, which the server translates into Statamic and Laravel operations under the hood.

Prerequisites:

• PHP 8.3+
• Composer installed
• Laravel 11+/12+ project with Statamic 5.65+ or 6.0+

Installation steps:

1. In your Statamic project, require the MCP package: composer require cboxdk/statamic-mcp

2. Run the MCP installation command to register the MCP server with Laravel: php artisan mcp:statamic:install

3. Optionally install Laravel Boost for an enhanced development experience: composer require laravel/boost --dev

4. Start your local development server as you normally would (e.g., php artisan serve) and ensure the MCP router is accessible for AI agents to issue requests via the MCP interface.

5. Verify MCP registration in Laravel’s MCP dashboard or via the CLI tooling to confirm the statamic router and actions are available.

Tips and considerations:

• The MCP server provides a broad set of tools; test critical workflows in a development environment before using in production.
• If you enable Laravel Boost, you gain richer debugging and database tooling that complements Statamic operations.
• Ensure PHP 8.3+ and compatible Statamic versions (5.65+ or 6.0+) are aligned with your Laravel application.
• When using actions that mutate data (create/update/delete), always consider enabling safety checks and backup strategies.
• Environment variables can influence behavior (APP_ENV, APP_DEBUG, database connections). Consider adding additional vars (e.g., STATAMIC_API_TOKEN) if you extend the MCP with external services.
• If you encounter issues, consult the MCP server’s logs and the Statamic error logs to isolate whether problems stem from the MCP layer, Statamic routing, or underlying Laravel services.