Kirby MCP
Give your coding agent access to your Kirby project and the knowledge to work with it. Kirby MCP connects your agent to project structure, live content, runtime debugging, and a bundled Kirby knowledge base.
Power your agent
การติดตั้งจากผู้เผยแพร่ ไม่ใช่เอนด์พอยต์ของ PlugMCP
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
Give your coding agent access to your Kirby project and the knowledge to work with it. Kirby MCP connects your agent to project structure, live content, runtime debugging, and a bundled Kirby knowledge base.
CLI-first MCP server for composer-based Kirby CMS projects — inspect blueprints/templates/plugins, interact with a real Kirby runtime, and use a bundled Kirby knowledge base.
For Composer-based Kirby projects. Kirby 6 · PHP 8.3+ · Composer
Capabilities · Knowledge base · Quickstart · Connect your agent · Usage · Tools and resources · Documentation
Your agent discovers the tools and resources through MCP. You can ask in plain language; you do not need to memorize tool names. Browse the tool and resource lists below to see the full range.
Expose your own project or plugin commands as custom MCP tools, with descriptions, validated inputs and explicit CLI allowlisting. The same Kirby command can also serve Janitor; no separate job system is added.
Kirby MCP ships with a curated knowledge base, not just access to your site. Your agent can search and read the bundled documents locally, without a network request:
The guides connect explanations to the relevant MCP tools and resources, so your agent can move from learning a Kirby concept to inspecting and working with your actual project. For example, the page-picker guide explains stored references, shows an update payload, and points to the tools for reading and verifying the content.
Use kirby_search to find a topic, or read documents through kirby://kb and kirby://kb/{path}. Official documentation and plugin-directory searches provide online lookups when you need to go further. You can also browse the bundled Markdown yourself.
From your Kirby project root:
composer require --dev bnomei/kirby-mcp:"^6.0"
vendor/bin/kirby-mcp install
Then connect your agent. Your MCP client starts the server; no separate running terminal is needed.
[!IMPORTANT] The verified Kirby CMS baseline is 6.0.0-beta.1. Kirby MCP's stable version does not make the CMS beta production-ready. Install Kirby separately and explicitly opt into its beta, for example with
composer require getkirby/cms:"6.0.0-beta.1" --with-all-dependencieson a test copy before installing MCP. For Kirby 5, usebnomei/kirby-mcp:"^1.15"instead.
The installer adds project-local runtime commands, a small Kirby plugin adapter, and .kirby-mcp/mcp.json. The MCP library stays in vendor/. Maintenance explains updates and removal.
Connecting a hosted site? Follow the remote installation tutorial for production installation, HTTPS, OAuth, and a restricted Kirby account. Advanced authentication options remain in the HTTP reference. Want reference access without a project? See global reference mode.
Step-by-step guides cover registration, authorization, a read-only connection check, and troubleshooting:
Client availability and authentication support vary; the tutorials link to official requirements and distinguish documented setup from live-tested compatibility. For a local project, the short configurations below are enough to get started.
Run these commands from the Kirby project root. They save an absolute executable path and project root so the client can find both when launched elsewhere.
claude mcp add kirby -- "$PWD/vendor/bin/kirby-mcp" "--project=$PWD"
codex mcp add kirby -- "$PWD/vendor/bin/kirby-mcp" "--project=$PWD"
Codex saves MCP registrations at user scope. Use a distinct server name instead of kirby for each project.
For Cursor, add this to .cursor/mcp.json, replacing both paths:
{
"mcpServers": {
"kirby": {
"command": "/absolute/path/to/project/vendor/bin/kirby-mcp",
"args": ["--project=/absolute/path/to/project"]
}
}
}
For other clients, configure the same command and arguments as a stdio MCP server. Reload your client if it does not discover the server immediately.
Try one of these prompts in your connected agent:
Use Kirby MCP to give me a tour of this project's blueprints, templates, and plugins.
Use Kirby MCP to plan a contact form using this project's conventions.
Read the about page with Kirby MCP and help me update its title.
Search the Kirby knowledge base for collection filtering. Check the official docs online if needed.
Asking for a plan is a useful way to inspect the project before making changes. Your agent can also read resources such as kirby://glossary/collection directly.
Skills give your agent task-specific guidance: project tours, page scaffolding, Panel blueprints, content migrations, routing, plugins, forms, translations, security, and more. See the skills catalog.
Copy them into your agent's skills directory. For Claude Code:
mkdir -p ~/.claude/skills
rsync -a vendor/bnomei/kirby-mcp/skills/ ~/.claude/skills/
For Codex, use ~/.codex/skills/ instead. Restart the agent after copying; repeat the copy after package updates to refresh the skills.
Add a dump where you need to inspect a value:
mcp_dump($page->title()->value())->label('Page title');
Ask your agent to render the page with kirby_render_page, then read the captured values with kirby_dump_log_tail using the returned traceId. Dumps are written to .kirby-mcp/dumps.jsonl; secret masking is on by default, but inspect output before sharing it.
For deeper inspection, query execution is enabled with confirmation. PHP eval is disabled until you enable it.
Ask your agent to check or generate IDE helpers, or run:
vendor/bin/kirby-mcp ide:status
vendor/bin/kirby-mcp ide:generate --write
Generated helpers live in .kirby-mcp/. Without --write, generation is a dry run.
See recent MCP activity at the top center of the Kirby Panel:

The indicator is off by default. To turn it on, set this in .kirby-mcp/mcp.json alongside your other settings:
{
"activity": { "enabled": true }
}
Run vendor/bin/kirby-mcp update to refresh the Panel assets, then reload the Panel. Kirby admins see the robot after a successful tool call or resource read. It fades from orange to grey and disappears after five minutes; hover, focus, or tap to see the elapsed time.
It shows recent activity, not whether an agent is connected or currently working. Activity details cover timing and shared-filesystem requirements.
Tools let your agent inspect or act; resources bring reference material and project data into its context. These are the project server's capabilities; global reference mode exposes only the research subset, and remote permissions can narrow access.
kirby_init, kirby_info, kirby_roots, kirby_composer_audit, kirby_cli_version.kirby_blueprints_index, kirby_blueprints_loaded, kirby_blueprint_read.kirby_templates_index, kirby_snippets_index, kirby_collections_index, kirby_controllers_index, kirby_models_index, kirby_plugins_index, kirby_routes_index.kirby_read_page_content, kirby_read_file_content, kirby_read_site_content, kirby_read_user_content.kirby_list_children, kirby_list_files, kirby_read_file, kirby_view_image.kirby_upload_file, kirby_move_page (preview first; pass confirm: true to execute).kirby_create_page, kirby_delete_page, kirby_change_page_slug, kirby_change_page_status.kirby_delete_file.kirby_find_pages, kirby_find_files.kirby_update_page_content, kirby_update_file_content, kirby_update_site_content, kirby_update_user_content.kirby_search, kirby_online, kirby_online_plugins, kirby_tool_suggest.kirby_render_page, kirby_dump_log_tail, kirby_query_dot, kirby_eval, kirby_run_cli_command.kirby_runtime_status, kirby_runtime_install, kirby_cache_clear, kirby_ide_helpers_status, kirby_generate_ide_helpers.Writes and execution follow the defaults and safety controls. See the tool reference for individual descriptions.
CLI tools and help resources accept canonical command names such as make:template, not filesystem paths or encoded aliases. OAuth upgrades require reauthorization for refresh tokens issued before grant-family tracking; see remote access.
Resources are read-only. Replace {…} with the item you want; the resource reference explains IDs and URI encoding.
kirby://kb, kirby://kb/{path}, kirby://glossary, kirby://glossary/{term}.kirby://fields/update-schema, kirby://field/{type}/update-schema, kirby://blueprints/update-schema, kirby://blueprint/{type}/update-schema.kirby://fields, kirby://field/{type}, kirby://sections, kirby://section/{type}.kirby://hooks, kirby://hook/{name}, kirby://extensions, kirby://extension/{name}.kirby://info, kirby://roots, kirby://composer, kirby://config/{option}, kirby://blueprint/{encodedId}.kirby://page/content/{encodedIdOrUuid}, kirby://file/content/{encodedIdOrUuid}, kirby://site/content, kirby://user/content/{encodedIdOrEmail}.kirby://file/read/{encodedIdOrUuid} returns text or a binary blob, not metadata.kirby://site/children, kirby://site/files, kirby://page/children/{encodedIdOrUuid}, kirby://page/files/{encodedIdOrUuid}. Follow each listing's nextUri for more results.kirby://commands, kirby://cli/command/{command}.kirby://tools, kirby://tool-examples.kirby://uuid/new, kirby://susie/{phase}/{step}.Browse pages and attachments, read original files, and view image previews using Kirby IDs or UUIDs. content remains metadata; read returns bytes. Uploads support local copies and single-use HTTP tickets; uploads and page moves require confirmation and native permissions.
See Native browsing, uploads and moves for pagination, blueprint constraints, examples, limits, and remote permissions.
You can start with the installed configuration. Change settings only for the capabilities you need.
Local MCP access is trusted access to your project. Confirmation guards MCP operations, not everything your coding agent can do through its other tools. Enabled PHP eval and generic CLI execution are not sandboxed. Keep .kirby-mcp/ outside your public document root or deny web access to it.
[!WARNING] Retrieved documents can contain prompt injection. Review proposed changes and do not assume an agent's output or a confirmation prompt makes an action safe.
For custom settings, use the configuration reference. Before exposing the server remotely, read the authentication and permission boundaries.
After upgrading the package, refresh the installed runtime files:
composer update bnomei/kirby-mcp
vendor/bin/kirby-mcp update
update overwrites the copied runtime commands and plugin adapter, but preserves your configuration. They normally live in site/commands/mcp/ and site/plugins/kirby-mcp/; custom Kirby roots are respected.
To uninstall, remove those two directories and the Composer dependency. Delete .kirby-mcp/ only if you also want to remove configuration, dumps, generated helpers, and remote authentication state. Remove the server entry from your MCP client and any HTTP routes you registered.
--project=/absolute/path/to/project.vendor/bin/kirby-mcp install and ask the agent to check kirby_runtime_status.cli.allow, cli.allowWrite, and cli.deny in the configuration reference.KIRBY_MCP_HOST or kirby.host.dumps.enabled, the dump file's permissions, and the render's traceId.Server diagnostics go to stderr. Include the client version and relevant error when reporting a problem; remove secrets first. See compatibility notes for the current CMS baseline and known upstream limitations.
For development and contributions, see Contributing and Testing. Release history lives in the Changelog; report vulnerabilities using the Security policy.
This MCP server is provided "as is" with no guarantee. Use it at your own risk and always test it yourself before using it in a production environment. If you find any issues, please create a new issue.
It is discouraged to use this MCP server in any project that promotes racism, sexism, homophobia, animal abuse, violence or any other form of hate speech.
CLI-first MCP server for composer-based Kirby CMS projects — inspect blueprints/templates/plugins, interact with a real Kirby runtime, and use a bundled Kirby knowledge base.
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Kirby ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-11 CLI-first MCP server for composer-based Kirby CMS projects — inspect blueprints/templates/plugins, interact with a real Kirby runtime, and use a bundled Kirby knowledge base.