Kirby MCP Server

CLI-first MCP server for Composer-based Kirby CMS projects. It lets an IDE or agent inspect your Kirby project (blueprints, templates, plugins, docs)

Local serverstdio

What is the Kirby MCP Server?

CLI-first MCP server for Composer-based Kirby CMS projects. It lets an IDE or agent inspect your Kirby project (blueprints, templates, plugins, docs) and interact

What you get

  • kirby_blueprint_read — read a single blueprint by id
  • kirby_blueprints_index — index blueprints, includes plugin-registered ones when runtime is installed
  • kirby_blueprints_loaded — list blueprint ids loaded at runtime
  • kirby_cache_clear — clear in-memory caches for this MCP session (StaticCache, config, composer, roots, tool index)
  • kirby_cli_version — run kirby version and return stdout, stderr and exit code
  • kirby_composer_audit — parse composer.json for scripts and quality tools

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

How to install the Kirby MCP Server

{
  "mcpServers": {
    "kirby-reference": {
      "command": "kirby-mcp",
      "args": [
        "--global"
      ]
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Example prompts to try

  • “Use Kirby MCP to Cursor.”
  • “Use Kirby MCP to Manual.”

Frequently asked questions

CLI-first MCP server for Composer-based Kirby CMS projects. It lets an IDE or agent inspect your Kirby project (blueprints, templates, plugins, docs) and interact Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.