Skip to content
Back to search

bricks-mcp-open

The most comprehensive open-source MCP server for Bricks Builder — 105 tools for pages, templates, styles, SEO, content, and more.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/developer2013--bricks-mcp-open/badge.svg)](/listings/developer2013--bricks-mcp-open)

HTML

<a href="/listings/developer2013--bricks-mcp-open"><img src="/api/listings/developer2013--bricks-mcp-open/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1. Install the WordPress Plugin

The `plugin/` folder in this repo contains the **Bricks API Bridge** WordPress plugin. Choose one of these install methods:

**Option A: ZIP Upload (easiest)** 1. Download **[bricks-api-bridge.zip](https://github.com/developer2013/bricks-mcp-open/releases/latest/download/bricks-api-bridge.zip)** from the latest release 2. Go to WordPress Admin → Plugins → Add New → Upload Plugin 3. Upload the ZIP and click "Install Now" 4. Click "Activate"

**Option B: Manual Upload via FTP/SSH** 1. Clone this repo or download it 2. Copy the `plugin/` folder to your WordPress installation:

   cp -r plugin/ /path/to/wordpress/wp-content/plugins/bricks-api-bridge/

3. Go to WordPress Admin → Plugins → Activate "Bricks API Bridge"

**Option C: WP-CLI**

# From the repo root. Builds from git, not from your working copy,
# so uncommitted files can't end up in the archive.
./scripts/build-plugin-zip.sh
wp plugin install bricks-api-bridge.zip --activate

After activation, the plugin registers REST API endpoints under `/wp-json/bricks-bridge/v1/`. No configuration needed — it works out of the box with WordPress Application Passwords.

2. Create an Application Password

In WordPress Admin → Users → Your Profile → Application Passwords: - Enter a name (e.g., "MCP Server") - Click "Add New Application Password" - Copy the generated password

3. Install the MCP Server

git clone https://github.com/developer2013/bricks-mcp-open.git
cd bricks-mcp-open
npm install   # or: bun install

4. Configure Credentials

Copy `.env.example` to `.env` and fill in your details:

cp .env.example .env
WORDPRESS_URL=https://your-site.com
WORDPRESS_USER=your-username
WORDPRESS_APP_PASSWORD=xxxx xxxx xxxx xxxx xxxx xxxx

5. Add to Your AI Assistant

**Claude Code** — add to `~/.claude/.mcp.json`:

{
  "mcpServers": {
    "bricks": {
      "command": "node",
      "args": ["/path/to/bricks-mcp-open/index.js"]
    }
  }
}

Or with Bun (faster startup):

{
  "mcpServers": {
    "bricks": {
      "command": "bun",
      "args": ["/path/to/bricks-mcp-open/index.js"]
    }
  }
}

**Claude Code iOS / Android App** — open Settings → MCP Servers → Add Server:

1. **Name:** `bricks` 2. **Command:** `node` (or `bun`) 3. **Arguments:** `/path/to/bricks-mcp-open/index.js` 4. **Environment Variables:** - `WORDPRESS_URL` = `https://your-site.com` - `WORDPRESS_USER` = `your-username` - `WORDPRESS_APP_PASSWORD` = `xxxx xxxx xxxx xxxx xxxx xxxx`

**Cursor / Windsurf** — add the same config to `.cursor/mcp.json` in your project.

**[Hermes Agent](https://github.com/NousResearch/hermes-agent)** (Nous Research) — add to `config.yaml`:

mcp_servers:
  bricks:
    command: node
    args: ["/path/to/bricks-mcp-open/index.js"]
    env:
      WORDPRESS_URL: https://your-site.com
      WORDPRESS_USER: your-username
      WORDPRESS_APP_PASSWORD: "xxxx xxxx xxxx xxxx xxxx xxxx"

Hermes has native MCP client support since v0.2.0 — all 105 tools appear in its tool list automatically. Works with any model (Hermes 3, Llama, OpenRouter, etc.).

> **Windows: TLS / "fetch failed" errors** > On Windows, Node.js ships its own bundled CA list and ignores the Windows certificate store. If your WordPress host sits behind a corporate proxy, TLS inspection, or a CA that's only trusted by Windows, every request fails with a certificate / `fetch failed` error. Tell Node to use the OS trust store by adding `--use-system-ca` **before** the script path in `args` (requires **Node.js ≥ 22.15**): > ```json > { > "mcpServers": { > "bricks": { > "command": "node", > "args": ["--use-system-ca", "C:\\path\\to\\bricks-mcp-open\\index.js"] > } > } > } > ```

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 432 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # bricks-mcp
  2. ```text
  3. ▟███████████████████████████████████████████▙
  4. █ ____ ____ ___ ____ _ ______ █
  5. █ | __ )| _ \|_ _/ ___| |/ / ___| BRICKS █
  6. █ | _ \| |_) || | | | ' /\___ \ █
  7. █ | |_) | _ < | | |___| . \ ___) | MCP █
  8. █ |____/|_| \_\___\____|_|\_\____/ █
  9. ▜▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▛
  10. 105 tools · 17 modules · MIT licensed
  11. ```
  12. > Printed on startup. In a real terminal the box animates in brick-by-brick (set `BRICKS_BANNER=anim|static|off`).
  13. **The most comprehensive open-source MCP server for [Bricks Builder](https://bricksbuilder.io/).**
  14. 100+ tools to manage pages, templates, styles, SEO, content, and more — directly from Claude Code, Cursor, Windsurf, or any MCP-compatible AI assistant.
  15. ![Tools](https://img.shields.io/badge/tools-105-blue)
  16. ![License](https://img.shields.io/badge/license-MIT-green)
  17. ![Bricks](https://img.shields.io/badge/Bricks_Builder-2.0%2B-orange)
  18. ![MCP](https://img.shields.io/badge/MCP-1.8-purple)
  19. ![Runtime](https://img.shields.io/badge/Node_%7C_Bun-green)
  20. ---
  21. ## Architecture
  22. ```
  23. Claude Code / Cursor / AI Assistant
  24. ↕ MCP Protocol (stdio)
  25. bricks-mcp (Node.js)
  26. ↕ REST API (Basic Auth)
  27. bricks-api-bridge (WordPress Plugin)
  28. ↕ PHP
  29. WordPress + Bricks Builder
  30. ```
  31. The MCP server communicates with your WordPress site through the included REST API plugin. Your AI assistant gets full control over Bricks Builder — reading pages, updating elements, managing styles, and building sections.
  32. ---
  33. ## Quick Start (5 Minutes)
  34. ### 1. Install the WordPress Plugin
  35. The `plugin/` folder in this repo contains the **Bricks API Bridge** WordPress plugin. Choose one of these install methods:
  36. **Option A: ZIP Upload (easiest)**
  37. 1. Download **[bricks-api-bridge.zip](https://github.com/developer2013/bricks-mcp-open/releases/latest/download/bricks-api-bridge.zip)** from the latest release
  38. 2. Go to WordPress Admin → Plugins → Add New → Upload Plugin
  39. 3. Upload the ZIP and click "Install Now"
  40. 4. Click "Activate"
  41. **Option B: Manual Upload via FTP/SSH**
  42. 1. Clone this repo or download it
  43. 2. Copy the `plugin/` folder to your WordPress installation:
  44. ```bash
  45. cp -r plugin/ /path/to/wordpress/wp-content/plugins/bricks-api-bridge/
  46. ```
  47. 3. Go to WordPress Admin → Plugins → Activate "Bricks API Bridge"
  48. **Option C: WP-CLI**
  49. ```bash
  50. # From the repo root. Builds from git, not from your working copy,
  51. # so uncommitted files can't end up in the archive.
  52. ./scripts/build-plugin-zip.sh
  53. wp plugin install bricks-api-bridge.zip --activate
  54. ```
  55. After activation, the plugin registers REST API endpoints under `/wp-json/bricks-bridge/v1/`. No configuration needed — it works out of the box with WordPress Application Passwords.
  56. ### 2. Create an Application Password
  57. In WordPress Admin → Users → Your Profile → Application Passwords:
  58. - Enter a name (e.g., "MCP Server")
  59. - Click "Add New Application Password"
  60. - Copy the generated password
  61. ### 3. Install the MCP Server
  62. ```bash
  63. git clone https://github.com/developer2013/bricks-mcp-open.git
  64. cd bricks-mcp-open
  65. npm install # or: bun install
  66. ```
  67. ### 4. Configure Credentials
  68. Copy `.env.example` to `.env` and fill in your details:
  69. ```bash
  70. cp .env.example .env
  71. ```
  72. ```env
  73. WORDPRESS_URL=https://your-site.com
  74. WORDPRESS_USER=your-username
  75. WORDPRESS_APP_PASSWORD=xxxx xxxx xxxx xxxx xxxx xxxx
  76. ```
  77. ### 5. Add to Your AI Assistant
  78. **Claude Code** — add to `~/.claude/.mcp.json`:
  79. ```json
  80. {
  81. "mcpServers": {
  82. "bricks": {
  83. "command": "node",
  84. "args": ["/path/to/bricks-mcp-open/index.js"]
  85. }
  86. }
  87. }
  88. ```
  89. Or with Bun (faster startup):
  90. ```json
  91. {
  92. "mcpServers": {
  93. "bricks": {
  94. "command": "bun",
  95. "args": ["/path/to/bricks-mcp-open/index.js"]
  96. }
  97. }
  98. }
  99. ```
  100. **Claude Code iOS / Android App** — open Settings → MCP Servers → Add Server:
  101. 1. **Name:** `bricks`
  102. 2. **Command:** `node` (or `bun`)
  103. 3. **Arguments:** `/path/to/bricks-mcp-open/index.js`
  104. 4. **Environment Variables:**
  105. - `WORDPRESS_URL` = `https://your-site.com`
  106. - `WORDPRESS_USER` = `your-username`
  107. - `WORDPRESS_APP_PASSWORD` = `xxxx xxxx xxxx xxxx xxxx xxxx`
  108. **Cursor / Windsurf** — add the same config to `.cursor/mcp.json` in your project.
  109. **[Hermes Agent](https://github.com/NousResearch/hermes-agent)** (Nous Research) — add to `config.yaml`:
  110. ```yaml
  111. mcp_servers:
  112. bricks:
  113. command: node
  114. args: ["/path/to/bricks-mcp-open/index.js"]
  115. env:
  116. WORDPRESS_URL: https://your-site.com
  117. WORDPRESS_USER: your-username
  118. WORDPRESS_APP_PASSWORD: "xxxx xxxx xxxx xxxx xxxx xxxx"
  119. ```
  120. Hermes has native MCP client support since v0.2.0 — all 105 tools appear in its tool list automatically. Works with any model (Hermes 3, Llama, OpenRouter, etc.).
  121. > **Windows: TLS / "fetch failed" errors**
  122. > On Windows, Node.js ships its own bundled CA list and ignores the Windows certificate store. If your WordPress host sits behind a corporate proxy, TLS inspection, or a CA that's only trusted by Windows, every request fails with a certificate / `fetch failed` error. Tell Node to use the OS trust store by adding `--use-system-ca` **before** the script path in `args` (requires **Node.js ≥ 22.15**):
  123. > ```json
  124. > {
  125. > "mcpServers": {
  126. > "bricks": {
  127. > "command": "node",
  128. > "args": ["--use-system-ca", "C:\\path\\to\\bricks-mcp-open\\index.js"]
  129. > }
  130. > }
  131. > }
  132. > ```
  133. > Alternatively set it via the environment instead of `args`: `"env": { "NODE_OPTIONS": "--use-system-ca" }`. On older Node versions, upgrade to ≥ 22.15 (or use `NODE_EXTRA_CA_CERTS` pointing to your CA bundle as a fallback).
  134. ---
  135. ### Manage Your WordPress Site from Your Phone
  136. Deploy the MCP server as a **self-hosted MCP environment** on Railway (or any Docker host), then connect it to the Claude Code mobile app. No Mac running in the background needed — the server runs 24/7 in the cloud.
  137. **How it works:**
  138. ```
  139. iPhone / Android (Claude Code App)
  140. ↕ Claude Self-Hosted MCP
  141. Railway / Docker (MCP Server — always on)
  142. ↕ REST API
  143. WordPress + Bricks Builder
  144. ```
  145. **Setup:**
  146. 1. Deploy the MCP server to Railway using the included `agent-service/Dockerfile`
  147. 2. In [Claude Console](https://console.anthropic.com) → MCP → Create Self-Hosted Environment
  148. 3. Generate an environment key and add it to your Railway deployment
  149. 4. The Claude Code mobile app automatically connects to your self-hosted environment
  150. **What you can do from your phone — no laptop needed:**
  151. ```
  152. You: "List all my pages and their SEO scores"
  153. You: "Create a new landing page for my dental practice"
  154. You: "Update the hero headline on page 42 to 'Welcome to Our Practice'"
  155. You: "Run an SEO audit and fix all missing meta descriptions"
  156. You: "Add a testimonials section using the testimonials-slider preset"
  157. You: "Create a snapshot called 'before-redesign', then change the palette"
  158. ```
  159. | Action | Example Prompt |
  160. |--------|---------------|
  161. | Build pages | *"Create a hero section with dark gradient background"* |
  162. | Edit content | *"Change the button text on page 42 to 'Book Now'"* |
  163. | SEO management | *"Set meta description and OG image for all pages"* |
  164. | Style updates | *"Update the primary color to #2563EB across the palette"* |
  165. | Backup & restore | *"Create a snapshot called 'before-redesign'"* |
  166. | QA checks | *"Check all links on page 42 for broken URLs"* |
  167. | Template management | *"Clone the header template and modify the navigation"* |
  168. The server runs 24/7 on Railway — your phone is just the control surface. All 105 tools are available anywhere, anytime.
  169. ### 6. Test the Connection
  170. Ask your AI assistant:
  171. > "Use the bricks_connection_test tool to verify my WordPress connection."
  172. ---
  173. ## Tool Categories (100+ Tools)
  174. | Category | Tools | Description |
  175. |----------|-------|-------------|
  176. | **Pages** | 9 | List, get, update, patch, append, build, clone, search pages |
  177. | **Scripts & Assets** | 5 | Per-page CSS/JS management, GSAP flag control |
  178. | **SEO (Page)** | 6 | Page-level SEO meta, schema markup, audit |
  179. | **Templates** | 8 | Full template CRUD, clone, import, search |
  180. | **Backup & Snapshots** | 7 | Named snapshots, multi-slot backups, restore |
  181. | **Global Classes** | 7 | CSS class CRUD, bulk create, usage analysis |
  182. | **BEM Components** | 3 | Generate, apply, and validate BEM class sets |
  183. | **Style System** | 10 | Color palette, fonts, CSS variables, breakpoints |
  184. | **Theme Styles** | 2 | Global theme style read/write |
  185. | **Presets** | 4 | Section presets: list, instantiate, save, delete |
  186. | **SEO (Advanced)** | 13 | Auto-fix, bulk update, sitemap, redirects, link check |
  187. | **WordPress Content** | 8 | Posts, categories, tags CRUD |
  188. | **Menus** | 5 | Navigation menu management |
  189. | **Site Management** | 9 | Settings, page creation, validation, cache, stats |
  190. | **Media** | 3 | Upload, list, edit media files |
  191. | **Multi-Site** | 3 | Switch between WordPress sites at runtime |
  192. | **Utilities** | 4 | Connection test, HTML→Bricks converter, Elementor→Bricks migration, batch ops |
  193. ---
  194. ## Migrating from Elementor?
  195. Switching from Elementor (Pro) to Bricks? `bricks_elementor_to_bricks` gives you a head start:
  196. 1. In WordPress, open the Elementor editor → **⌄ (menu) → Export Template** (or **Templates → Saved Templates → Export**). You get a `.json` file.
  197. 2. Run the tool with that file:
  198. ```
  199. bricks_elementor_to_bricks file_path="/path/to/elementor-export.json"
  200. ```
  201. 3. You get a ready-to-review **Bricks element array** plus a coverage report.
  202. 4. Review it, then push with `bricks_update_page` (take a snapshot first) or `bricks_import_page`.
  203. **How it works:** a purely structural translation — no headless browser, no rendering, no write to your site. Common widgets (heading, text, button, image, icon, divider, spacer) and the section/column/container structure map straight to **native, editable Bricks elements**. Widgets without a native equivalent (e.g. Pro sliders, forms, loops) become clearly-labelled placeholder blocks carrying a preview of their original content — so nothing is lost silently and you always see *where* and *what* to rebuild by hand. `line-height` is converted to a correct unitless ratio so you never inherit Elementor's px values as Bricks multipliers.
  204. ---
  205. ## Keeping your CSS editable in Bricks
  206. The whole point of Bricks is a visual builder — so CSS the assistant writes should stay **editable in Bricks**, not vanish into a place you can't reach. This plugin can inject per-page CSS into a private bundle (`_bab_page_assets`, output at `wp_head` priority **9997 — before** element CSS) via `bricks_update_page_assets`. That bundle is **not shown anywhere in the Bricks builder** and silently overrides what the builder displays — great for infrastructure CSS (`@font-face`, `:root{--vars}`, `@keyframes`, critical above-the-fold), but the wrong home for the layout/responsive/visual CSS you'll want to tweak by hand later. (This is exactly the r/BricksBuilder feedback: *"plugin-managed page CSS that a human can't edit defeats the purpose of using Bricks."*)
  207. **Where editable CSS belongs (priority order):**
  208. 1. **Native element settings** — padding, typography, colors, etc. (fully visual controls)
  209. 2. **Element `_cssCustom`** — per-element custom CSS, editable on the element's CSS tab
  210. 3. **Page `customCss`** — `bricks_update_page_settings` → Bricks *Page Settings → Custom CSS*
  211. 4. **Global classes** — editable in the Class Manager (build them with **native settings**, not `_cssCustom`, which is not compiled into page CSS via the API path)
  212. ### The editability guard
  213. To stop editable CSS from leaking into the invisible bundle, the guard classifies the `css` field of `bricks_update_page_assets` and acts in three modes:
  214. | Mode | Behaviour |
  215. |------|-----------|
  216. | `off` *(default)* | No-op — fully backwards-compatible |
  217. | `warn` | Write proceeds, the REST response carries a `warnings[]` field naming the editable rules |
  218. | `block` | Editable CSS is rejected (HTTP 422) and **nothing is written** |
  219. **Enable it** by adding one line to your `wp-config.php` (above `/* That's all, stop editing! */`):
  220. ```php
  221. // Bricks API Bridge — warn (or 'block') when editable CSS is sent to the private page-assets bundle
  222. define( 'BAB_GUARD_EDITABLE_CSS', 'warn' );
  223. ```
  224. (Or, without editing files: `wp option update bab_guard_editable_css warn`.) On the MCP side, the `bricks_update_page_assets` tool warns by default; set the env var `BRICKS_MCP_BLOCK_EDITABLE_CSS=1` to hard-block there too. Infrastructure CSS always passes — use the `css_critical` / `css_deferred` fields for it.
  225. ---
  226. ## Multi-Site Support
  227. Manage multiple WordPress sites from a single MCP server. Copy `sites.json.example` to `sites.json`:
  228. ```json
  229. {
  230. "default": "production",
  231. "sites": {
  232. "production": {
  233. "label": "Live Site",
  234. "url": "https://your-site.com",
  235. "username": "admin",
  236. "password": "xxxx xxxx xxxx xxxx xxxx xxxx"
  237. },
  238. "staging": {
  239. "label": "Staging",
  240. "url": "https://staging.your-site.com",
  241. "username": "admin",
  242. "password": "xxxx xxxx xxxx xxxx xxxx xxxx"
  243. }
  244. }
  245. }
  246. ```
  247. Switch sites at runtime:
  248. > "Switch to the staging site."
  249. **Custom `sites.json` location.** If you collect your MCP servers in one folder and keep site configs elsewhere, set `BRICKS_SITES_PATH` to point at the file — absolute, relative (to the working directory), or `~`-prefixed all work:
  250. ```
  251. BRICKS_SITES_PATH=~/mcp-config/bricks-sites.json
  252. ```
  253. When set, a missing file fails loudly at startup (instead of silently falling back to the `WORDPRESS_*` env vars), so a typo in the path can't connect you to the wrong site. No need to symlink `sites.json` into the server folder.
  254. ---
  255. ## Usage Examples
  256. ### Build a page section
  257. > "Create a hero section on page 42 with a full-width background, centered heading 'Welcome', a subtitle, and a CTA button."
  258. ### Manage styles
  259. > "Update the color palette — set the primary color to #2563EB and secondary to #7C3AED."
  260. ### SEO optimization
  261. > "Run an SEO audit on all published pages and auto-fix missing meta descriptions."
  262. ### Backup before changes
  263. > "Create a snapshot of page 42 named 'before-redesign', then update the hero section."
  264. ---
  265. ## Plugin Features
  266. The included WordPress plugin (`bricks-api-bridge`) provides:
  267. - **REST API endpoints** for all Bricks Builder data
  268. - **Security hardening** — rate limiting, user enumeration protection, security headers
  269. - **Responsive inference** — automatic mobile/tablet breakpoint generation
  270. - **Element validation** — catches invalid IDs, broken parent-child links
  271. - **Auto-fix** — corrects common CSS issues (overflow, grid, container width)
  272. - **Backup system** — multi-slot backups + named snapshots
  273. - **Design token import/export** — JSON, ACSS, Tailwind formats
  274. ---
  275. ## Feature Comparison
  276. | Feature | bricks-mcp | Novamira | cristianuibar/bricks-mcp | sabiertas/bricks-mcp-server |
  277. |---------|-----------|----------|--------------------------|----------------------------|
  278. | **Focus** | **Bricks Builder** | Generic WordPress | Bricks Builder | Bricks Builder |
  279. | **Tools** | **105** | 22 (12 core + 10 Gutenberg) | 11 | 10 |
  280. | **Approach** | REST API (structured endpoints) | PHP execution + filesystem | REST API | REST API |
  281. | **Agent Service** | Autonomous 5-phase pipeline | - | - | - |
  282. | **Mobile Control** | Telegram bot (iPhone/Android) | - | - | - |
  283. | **Multi-Site** | Runtime switching | - | - | Environment vars |
  284. | **BEM Support** | Generate + Apply + Validate | - | - | - |
  285. | **SEO Tools** | 19 (meta + audit + redirects) | - | - | - |
  286. | **Backup System** | Snapshots + Multi-slot | - | - | - |
  287. | **Section Presets** | 25 ready-to-use | - | - | - |
  288. | **Security Hardening** | Rate limit + Headers | - | - | - |
  289. | **Responsive Inference** | Auto breakpoints | - | - | - |
  290. | **WordPress Content** | Posts + Categories + Tags + Menus | Via PHP execution | - | - |
  291. | **Batch Operations** | Up to 20 per request | - | - | - |
  292. | **Design Tokens** | Import/Export (JSON, ACSS) | - | - | - |
  293. | **Auto-Fix** | Overflow, grid, container | - | - | - |
  294. | **Gutenberg Support** | - | Block Editor Queue | - | - |
  295. | **PHP Execution** | - | Direct PHP eval | - | - |
  296. | **License** | MIT | AGPL-3.0 | GPL-2.0 | MIT |
  297. ---
  298. ## Requirements
  299. - **Node.js** >= 18 or **Bun** >= 1.0 *(Windows behind a proxy/custom CA: use Node ≥ 22.15 with `--use-system-ca` — see [Windows TLS note](#5-add-to-your-ai-assistant))*
  300. - **WordPress** >= 6.0
  301. - **Bricks Builder** >= 2.0
  302. - **PHP** >= 8.0
  303. ---
  304. ## Agent Service (Autonomous Page Builder)
  305. The `agent-service/` directory contains an autonomous agent that builds entire WordPress pages from industry briefs — using Claude + the MCP server in a 5-phase pipeline:
  306. ```
  307. Industry Brief → Historian → Design → Code → Update → QA → Fix Loop
  308. ```
  309. - **Build from your iPhone or Android** — Use the Telegram bot or the [Claude Code mobile app](https://claude.ai/download) as your control center: trigger builds, QA, fixes, and screenshots from anywhere
  310. - **CLI Mode** — Single builds or overnight batch processing
  311. - **Budget Control** — Per-phase cost caps, total cost tracking
  312. - **Docker Ready** — Deploys to Railway, Fly.io, or any container host
  313. See [`agent-service/README.md`](agent-service/README.md) for setup instructions.
  314. ---
  315. ## Premium
  316. Looking for more? The premium edition includes **260+ tools** with:
  317. - **AI Build Pipeline** — Build entire pages from a URL in one command
  318. - **Learning System** — Remembers CSS fixes and improves over time
  319. - **Math Library** — 33 modules for design tokens, color harmony, spring physics
  320. - **Visual QA** — Puppeteer screenshots, pixel comparison, accessibility audits
  321. - **Design Intelligence** — Brand archetypes, competitive benchmarking, typography suggestions
  322. - **WooCommerce, ACF, Gravity Forms** integrations
  323. - **Bio-inspired animations** — Levy stagger, density-intensity, quorum sensing
  324. [Reach out for premium access](mailto:me@carstensachse.de)
  325. ---
  326. ## Contributing
  327. See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
  328. ## License
  329. MIT License. See [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.