菜单
Use when reading or changing Bricks global settings (post types, CSS loading, maintenance mode, performance toggles). Covers the allow-list registry flow, partial-merge semantics, and what keys are excluded from MCP by design.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | bricks-settings |
| description | Use when reading or changing Bricks global settings (post types, CSS loading, maintenance mode, performance toggles). Covers the allow-list registry flow, partial-merge semantics, and what keys are excluded from MCP by design. |
Requires: Bricks 2.4+ with the Abilities API enabled
Run first when filesystem tools are available:
_BS_UPDATE_CHECK=""
for _CAND in "$HOME/.bricks/skills/bricks-skills/scripts/bricks-skills-update-check" "$PWD/scripts/bricks-skills-update-check" "$HOME/.claude/skills/bricks-skills/scripts/bricks-skills-update-check" "$HOME/.codex/skills/bricks-skills/scripts/bricks-skills-update-check"; do
[ -f "$_CAND" ] && _BS_UPDATE_CHECK="$_CAND" && break
done
[ -n "$_BS_UPDATE_CHECK" ] && sh "$_BS_UPDATE_CHECK" || true
If it prints BRICKS_SKILLS_UPDATE_AVAILABLE <old> <new> <tag>, load bricks-skills-update before continuing. If it prints BRICKS_SKILLS_JUST_UPDATED <old> <new>, mention the new version and continue.
Bricks global settings (the bricks_global_settings option: hundreds of keys backing the admin Settings pages) are exposed to MCP through an allow-list registry. You don't update_option the whole blob: you discover writable keys, then send partial writes that update the keys you send.
Three tools. Use them in order:
bricks/list-settings-schema: read-only discovery. Returns every key the MCP will accept, with type, category, description, and validation hints. Call this first if you don't already know which key to write.bricks/get-global-settings: read current values for keys in the registry. Never returns excluded credential values or code-execution toggles.bricks/set-global-settings: partial-merge write. Takes { settings: { key: value, ... } }. Other keys untouched.set-global-settings updates the keys you send and leaves everything else alone. This is the opposite of a typical update_option call: you don't need to round-trip the entire settings blob. Safe to batch multiple unrelated top-level keys in one call.
bricks/set-global-settings
settings:
postTypes: ["page","post","product","bricks_template"]
cssLoading: "file"
Result: postTypes and cssLoading updated; every other setting (maintenance mode, disable emojis, etc.) retained exactly as it was.
Dozens of keys across categories. Current examples from includes/abilities/settings.php:
postTypes, wp_to_bricks, bricks_to_wp, disableClassManager, disableVariablesManager, disableOpenGraph, disableSeo, elementAttsAsNeeded, customImageSizes, disableSkipLinks, smoothScroll, deleteBricksData, searchResultsQueryBricksData, themeStylesLoadingMethod, duplicateContent, enableQueryFilterspublicTemplates, myTemplatesAccess, myTemplatesWhitelist, remoteTemplates, saveFormSubmissionsbuilderAutosaveInterval, builderQueryMaxResults, builderLocale, abilitiesApicssLoading, disableBricksCascadeLayer, disableEmojis, disableJqueryMigratemaintenanceMode, maintenanceTemplate, bypassMaintenanceUserRoles, maintenanceExcludedPostspasswordProtectionEnabledCall list-settings-schema to see the current full list: it's auto-generated from the registry and stays in sync with Bricks updates.
These are blocked at the registry level (see Settings::EXCLUDED_SETTING_KEYS). Attempting set-global-settings with any of these returns bricks_setting_excluded. The literal list:
licenseKey: plus any key starting with license, apiKey, or apiSecretKeyinstagramAccessTokenmyTemplatesPasswordremoteTemplatesPasswordremoteTemplates[].passwordexecuteCodeEnabled: master toggle for the custom-PHP execution pathexecuteCodeCapabilities: role matrix controlling who can execute codecodeSignaturesLocked: prevents tampering with the signature-verification defensecodeExecutionMode: chooses between strict and permissive PHP sandboxinghtmlExecutionMode: same, for custom HTML blocksReason: every item here is a credential or privilege-escalation boundary. A tool that can read apiKeyGoogleMaps can leak a billable provider key; a tool that can flip executeCodeCapabilities or executeCodeEnabled can grant itself RCE. These values stay admin-UI-only even with MCP fully enabled. Signature regeneration is also admin-UI-only and is not controlled by an excluded settings key: it simply has no MCP ability (see the bricks-maintenance skill).
If a task requires one of these, surface the requirement to a human: don't try to route around the exclusion.
remoteTemplates can manage saved source URLs and optional names only. Passwords are preserved if already configured, but never returned or written. New MCP-written remote template URLs must be public http/https URLs: private, loopback, link-local, unsafe-port, credentialed, or non-resolving hosts are rejected because those URLs are later used for outbound template-library fetches.
Use bricks-list-credential-status when you only need to know whether a credential exists. It returns rows with configured, readable: false, and writable: false; it never returns the stored value or a masked fragment.
Good uses:
apiKeyGoogleMaps.configured before building a Google Maps experience.Do not ask for the raw value. If a required credential is missing, tell the user which setting to add in the Bricks admin UI.
set-global-settings { settings: { fooBarBaz: 1 } } where fooBarBaz isn't in the registry returns bricks_setting_unknown. This is defensive: silent acceptance of arbitrary keys would make the option bloat with junk an admin can't clean up.
If you think a setting SHOULD be writable but isn't in the registry, it probably moved to a dedicated ability:
bricks/set-breakpointsbricks/set-style-managerbricks/set-pseudo-classesbricks/list-builder-permissions, bricks/upsert-builder-capability, bricks/set-builder-role-accessThe registry is for keys that don't fit into one of those domains.
If a
bricks/*ability is not available as a direct tool: first check whether it is outside the fast path and call it throughmcp-adapter-execute-abilitywithability_name: "bricks/<name>". If the dispatcher also rejects it, callbricks-list-ability-statusto check whether a site admin disabled it under Bricks > AI.
bricks/list-settings-schema
-> scan output for "maintenance" category
-> find maintenanceMode, maintenanceTemplate, bypassMaintenanceUserRoles, maintenanceExcludedPosts
bricks/get-global-settings (optional: check current values)
bricks/set-global-settings
settings:
maintenanceMode: "maintenance"
maintenanceTemplate: 123
bypassMaintenanceUserRoles: "custom"
maintenanceExcludedPosts: ["45","88"]
One call, four keys, atomic update. Everything else about the site untouched.
bricks/get-global-settings -> mutating -> bricks/set-global-settings with the whole blob. It works, but it defeats partial-merge and races with admin UI saves.bricks_setting_excluded: the exclusion is permanent and deliberate.list-settings-schema output as cacheable across Bricks versions: new keys show up with updates.Use when writing custom-element controls or debugging control behavior: "what control type for a color?", "conditional control visibility", "dynamic data on a custom control". Covers the ~40 control types, the `required` syntax, CSS-binding via `css` key, dynamic-data support, and default-value gotchas.
Use before writing or editing Bricks element JSON, settings, controls, globals, page settings, or template settings. Gives the runtime lookup order plus bundled full resolved schemas so you can check exact control keys and value shapes instead of guessing.
Use after every write through the Bricks MCP: set-page-elements, update-element, update-element-conditions, update-element-interactions, batch-update-elements, set-template-conditions, set-global-variables, create-theme-style, etc. Defines the verify-after-write loop: read back the change, render the affected post, check for silent failures (empty render, unknown tags, unbalanced braces, query:null). Catches the "tool returned success but the page broke" class of bugs.
Use when the Bricks skills update check reports BRICKS_SKILLS_UPDATE_AVAILABLE, or when the user asks to update the Bricks skills pack.
Use at the start of every Bricks session. Orientation rules: call get-design-context before any design-system write, verify mutations with get-page-elements / list-revisions, and never force same-named globals to duplicate.
Use when creating or updating design tokens: global classes, variables, color palettes, theme styles, components. Enforces uniqueness, scale-generator usage, and conditions on theme styles. Prevents system fragmentation.