- How do I install danielgnh/statamic-mcp in a Laravel Statamic project?
- Install it as a Composer dependency with composer require danielgnh/statamic-mcp, then follow the package README for MCP server registration and client configuration. Because it is a Laravel package for Statamic 6, confirm your PHP and Statamic versions satisfy the package constraints before rollout. After configuration, restart the MCP server or worker so clients receive the registered tool schema.
- Which Laravel and Statamic versions does danielgnh/statamic-mcp support?
- The package is described as an MCP server for Statamic 6, so Statamic 6 is the documented target. The provided context does not list a full Laravel or PHP support matrix, so check the Composer constraints and release notes for your exact Laravel and PHP versions. Validate in a development environment before upgrading production.
- What can I do with the MCP tools in danielgnh/statamic-mcp?
- The package connects MCP-capable AI assistants to Statamic content and structure through standardized tools. Documented workflows include inspecting blueprints with blueprints_get and managing navigation content with tools such as navigations_get and navigations_update. The intended pattern is to inspect the schema first, then perform permission-controlled content changes. It is aimed at Laravel and Statamic developers building AI-assisted content workflows.
- How does blueprints_get handle navigation blueprints in version 0.9.1?
- In v0.9.1, blueprints_get can read navigation blueprints where type is navigation and return branch data field definitions. It also exposes Replicator and Bard set schemas plus example_notes for branch keys such as title and url. Agents should pass title and url as branch keys rather than nesting them inside data. This is an additive, read-only capability.
- How are Statamic permissions enforced when AI assistants use this MCP server?
- The package is designed to manage content under Statamic's permission system and reuses the existing view {handle} nav gate for navigation blueprint access. Roles that can already call navigations_get should work with the related navigation introspection. Partial permissions can produce partial schemas, so test with the least-privileged role intended for production. Confirm how permissions are resolved per request in long-lived MCP sessions.
- Do I need migrations or content changes when updating to 0.9.1?
- No database migrations, content changes, or likely new configuration are required for the 0.9.1 navigation blueprint addition. The main steps are updating the Composer dependency, running your application test suite, and restarting the MCP server or worker. If the package is pinned, update the lockfile deliberately and review the release diff. Confirm that MCP clients refresh their tool definitions after the restart.
- What are the production risks of using a 0.x MCP package like this?
- The read-only navigation blueprint change is low risk for existing tools, but 0.x versioning means tool input and output shapes can still change. Pin the dependency, review release diffs, and test schema changes before production. Use a tool-level feature flag if supported and update agent prompts and runbooks with each release. Data exposure is also worth reviewing because example rows may derive from real content.
- Does danielgnh/statamic-mcp support multisite and cached blueprint definitions?
- The provided evaluation does not confirm multisite behavior or whether blueprints_get reads live blueprints versus cached definitions. It specifically raises these as questions to verify for your installation. Test whether the tool resolves the correct site's navigation blueprint and whether caching is configurable. If your site uses multisite or heavy blueprint caching, validate in staging before relying on it.
- How should I test navigation blueprint introspection before production?
- In development, call blueprints_get against a known navigation handle and inspect the response for a Replicator or Bard field. Confirm that set fields and example rows are present and that example_notes instruct agents to pass title and url as branch keys. Test with the least-privileged MCP role intended for production, then repeat in staging. Update agent system prompts to require blueprints_get before navigations_update on navigation content.
- What alternatives should I consider to danielgnh/statamic-mcp?
- This package is a focused MCP server for Statamic 6, so alternatives include building a custom MCP server around Statamic's APIs or using existing Statamic and Laravel tooling directly without an MCP layer. The right choice depends on whether your AI host needs standardized MCP tools and permission-aware navigation workflows. Compare version support, schema stability, and maintenance activity before adopting a 0.x package. If you only need internal automation, a smaller custom integration may be easier to control.