Kirby MCP Server

Kirby MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. 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 with a real Kirby runtime. It ships with a local knowledge base of Kirby.

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

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What the assistant can call

Once Kirby MCP is connected, these are the calls the assistant has available:

• Cursor — Use kirby-reference for docs/KB research that is always available. Use kirby-project only when that specific Kirby project should be inspectable or
• Manual — Start the server (point it at a composer-based Kirby project):

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the kirby mcp mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Kirby MCP's toolset — Cursor, Manual — is a fair guide to whether it matches your workflow. It is maintained by bnomei; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.