Kirby MCP is a CLI-first server for Kirby CMS projects. It enables developers to inspect blueprints, templates, and plugins, interact with a real Kirby runtime, and access a bundled knowledge base. It connects to Kirby CMS projects and integrates with Claude for enhanced workflows.
git clone https://github.com/bnomei/kirby-mcp.gitKirby MCP is a Model Context Protocol server designed for Composer-based Kirby CMS projects, enabling developers and AI agents to inspect project structure, blueprints, templates, snippets, controllers, and plugins through an interactive CLI-first interface. It provides real-time interaction with a Kirby runtime environment, allowing agents to read page content, render templates, execute queries, and run CLI commands with built-in security controls. The server ships with a local knowledge base covering Kirby concepts, common tasks, and field update guides, plus fallback access to official Kirby documentation and plugin directory search. This integration allows Claude Code, Cursor, and other AI agents to make informed plans for content management, form building, configuration updates, and debugging tasks within Kirby projects, reducing reliance on external documentation lookups.
1. **Install Kirby MCP**: Ensure Kirby MCP is installed and running in your environment. You can verify this by running `kirby-mcp --version` in your terminal. 2. **Connect to Your Project**: Use the `connect` command in Kirby MCP to link to your Kirby CMS project. For example: `kirby-mcp connect /var/www/my-site`. 3. **Inspect Blueprints**: Run the inspection command (e.g., `kirby-mcp inspect blueprint article.yml`). Replace `article.yml` with the name of your blueprint file. 4. **Review Output**: Analyze the output for issues like missing fields, inconsistencies, or deprecated options. Use the suggestions to update your blueprints and templates. 5. **Iterate and Test**: After making changes, re-run the inspection to ensure all issues are resolved. Test the updated blueprints in your Kirby admin panel to confirm they work as expected.
Plan and implement new page types and blueprints with agent guidance
Debug template rendering issues using MCP dump and log tail tools
Search local Kirby knowledge base and official docs for configuration help
Read and update page content programmatically via agent interaction
No install command available. Check the GitHub repository for manual installation instructions.
git clone https://github.com/bnomei/kirby-mcpCopy the install command above and run it in your terminal.
Launch Claude Code, Cursor, or your preferred AI coding agent.
Use the prompt template or examples below to test the skill.
Adapt the skill to your specific use case and workflow.
Use Kirby MCP to inspect the [BLUEPRINT_NAME] blueprint in my Kirby CMS project located at [PROJECT_PATH]. Check for missing fields, incorrect validation rules, or deprecated options in the blueprint configuration. Then, list all templates that use this blueprint and identify any inconsistencies between the blueprint and template files. Finally, suggest improvements to standardize the field types and validation rules across all templates using this blueprint.
I’ve inspected the `article.yml` blueprint in your Kirby CMS project at `/var/www/my-site` and found the following issues: 1. **Missing Fields**: The `article.yml` blueprint is missing a `slug` field, which is critical for URL generation. The `title` field is present but lacks validation for minimum length (currently set to 3 characters, but no maximum limit is enforced). 2. **Inconsistent Templates**: Three templates (`article.php`, `blog-post.php`, and `news.php`) reference this blueprint. However, `news.php` uses a `text` field for the `body` instead of the `textarea` field defined in the blueprint. This inconsistency could lead to rendering issues in the admin panel. 3. **Deprecated Options**: The `status` field in the blueprint uses `draft`, `listed`, and `unlisted`, but the `unlisted` option is deprecated in Kirby 4.x. Replace it with `hidden` for future compatibility. **Suggested Improvements**: - Add a `slug` field with the `required: true` and `type: slug` options. - Standardize the `body` field across all templates to use `type: textarea` with a `maxLength: 5000` validation rule. - Update the `status` field to use `hidden` instead of `unlisted`. These changes will ensure consistency, improve validation, and align with Kirby 4.x best practices.
IronCalc is a spreadsheet engine and ecosystem
Get more done every day with Microsoft Teams – powered by AI
Enterprise workflow automation and service management platform
Automate your spreadsheet tasks with AI power
Agentic AI Workflow platform
Connected workspace for docs, wikis, and projects
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan