Kirby FAQs

Question 1

What is Kirby MCP?

Accepted Answer

Kirby MCP (Model Context Protocol) is a CLI-first tool designed for Composer-based Kirby CMS projects. It provides a powerful interface for IDEs and AI agents to inspect project assets, interact with a live Kirby runtime, and access a local knowledge base.

Question 2

How does Kirby MCP integrate with AI agents and IDEs?

Accepted Answer

It functions as an MCP server, providing a structured interface that allows AI clients like Cursor, Claude Code, and Codex CLI to deeply understand and interact with your Kirby project, facilitating agent-driven development, debugging, and content manipulation.

Question 3

What specific development tasks can Kirby MCP assist with?

Accepted Answer

Kirby MCP helps developers and agents inspect project assets (blueprints, templates, plugins), interact with live Kirby data, debug issues, plan content migrations, and scaffold projects. It also offers a runtime for evaluating PHP within the Kirby context.

Question 4

Does Kirby MCP include its own knowledge base?

Accepted Answer

Yes, Kirby MCP ships with a local knowledge base containing essential Kirby concepts, common tasks, and update guides. This built-in resource significantly reduces the need for external searches, speeding up development and agent efficiency.

Question 5

What are the primary benefits of using Kirby MCP for Kirby CMS projects?

Accepted Answer

The main benefits include a streamlined CLI-first workflow, deep project introspection, live runtime interaction for dynamic data, integrated AI agent support for advanced automation, and a comprehensive local knowledge base, all contributing to faster and more efficient Kirby CMS development.

Kirby

Kirby

Key Features

Use Cases

Key Features

Use Cases