Skip to content
Documentation

Your EMCP guide

Answers from our docs

YOUR CHAT, YOUR CHOICE

Before we chat

MSR Builds processes your question and up to four recent messages on our server to answer from the EMCP docs. AI is optional and needs your separate permission.

The chat is kept in this page's memory, not saved as a conversation in our database or browser storage. Our hosting and security services process connection information, such as your IP address, to prevent abuse.

Cloudflare Turnstile checks your browser and connection to prevent automated abuse when you send a question. No login is required.

Please leave out personal, sensitive or confidential information, passwords and API keys.

You can withdraw consent and clear this page's chat at any time. This cannot undo a request already sent or erase provider/security records.

Chat privacy, retention & your rights ↗ · Privacy contact

Starting chat consents to this processing. You can browse our docs without using the chat.

Active theme (any theme)

Before the theme-specific packs (Astra, Kadence, GeneratePress, Blocksy), EMCP Tools ships a builder-agnostic Themes layer that works with whatever theme a site is running. It is the base every named pack builds on: when the active theme is one of the supported ones, the matching pack adds a curated, verified settings allowlist on top; otherwise these generic tools still give an agent the theme context and Customizer access it needs.

How it works

Section titled “How it works”

Both tools take { operation, arguments }. Omit operation to get back the list of available operations for that tool.

emcp-tools/theme-read

Section titled “emcp-tools/theme-read”

Read-only, on by default. Operations:

  • get-theme-context: the active theme and its parent, the detected framework, whether it is a block theme (is_block_theme), declared supports, registered menu locations, and whether a child theme is active. Call this first so an agent knows what it is working with.
  • get-mods: read the theme’s Customizer theme_mod values.

emcp-tools/theme-write

Section titled “emcp-tools/theme-write”

Disabled by default. Registers behind the edit_files / switch_themes capabilities. Operations:

  • set-mods: write Customizer theme_mod values. Structural keys are refused.
  • create-child-theme: scaffold a style.css + functions.php child of the active parent and activate it, so an agent can then edit theme files via the Filesystem tools. Idempotent, requires confirm: true, and refuses to build a grandchild.

Example

Section titled “Example”

Read the active theme’s context before doing anything else:

theme-read({ operation: "get-theme-context" })

Create a child theme so theme files can be edited safely:

theme-write({ operation: "create-child-theme", arguments: { confirm: true } })

Safety

Section titled “Safety”

theme-read is read-only and on by default. theme-write ships off and, because create-child-theme writes a functions.php and activates the child (effectively code execution), it stays behind the disabled-by-default write gate and the edit_files / switch_themes capabilities. When you need it, switch on Theme Write under EMCP Tools → Tools → Themes (section Active Theme) and choose Save changes in the save bar.

See also

Section titled “See also”