Repository navigation
faq
An AI-assisted development toolkit for Magento 2 that implements the Model Context Protocol (MCP). It allows AI coding agents to inspect, query, and modify Magento installations.
Claude Code, Cursor, GitHub Copilot, JetBrains AI (PhpStorm), and Gemini CLI.
No. It's a standalone Composer library that connects to Magento from outside the module system. It initializes the ObjectManager directly without being registered as a module.
Magento 2.4.4 through 2.4.8 with PHP 8.1 through 8.4.
Bricklayer searches for app/etc/env.php starting from the current working directory. Ensure you're running commands from within or above your Magento root directory.
DDEV is auto-detected. After composer require --dev inchoo/magento-bricklayer, run ddev exec vendor/bin/bricklayer install. The generated .mcp.json will use ddev exec as the command wrapper.
Same as DDEV — Warden is auto-detected via the WARDEN_ENV_NAME environment variable.
Bricklayer uses progressive disclosure. Only 17 essential tools are listed in tools/list. Use search-tools to discover the full set of 84 tools by keyword.
Yes, with safety restrictions. Destructive tools, code generation, and code execution are blocked by default in production mode. Read-only introspection and query tools remain available.
code-runner is hard-blocked in production mode. This cannot be overridden even with explicit configuration in .bricklayer.json. This is a deliberate security measure.
Add it to your .bricklayer.json:
{
"tools": {
"product-delete": { "enabled": true }
}
}Note: This only works in developer mode for destructive tools.
No. The server detects file changes via mtime tracking and reloads automatically on the next tool call.
vendor/bin/bricklayer updateBuilt-in defaults are used. In developer mode, all tools are enabled. In production mode, destructive tools are disabled.
Run vendor/bin/bricklayer verify to diagnose. Common causes:
- Missing
app/etc/env.php - Failed ObjectManager initialization
- Magento in maintenance mode
Check your .bricklayer.json and deploy mode. In production, destructive tools require explicit "enabled": true.
Bricklayer auto-detects staleness via sentinel files. If it doesn't pick up changes, call the reinitialize tool manually.
Verify that .mcp.json exists in your project root and the MCP server command is correct:
vendor/bin/bricklayer verifyGetting Started
Architecture
Tools Reference
- Overview (84 Tools)
- Introspection
- Catalog
- Orders
- Customers
- Database
- Logs & Diagnostics
- GraphQL
- Development
Configuration
Guidelines & Skills
Code Generation
Diagnostics
Security