Choose MCP access and understand its limits
POM AI exposes a defined website authoring catalog. WordPress permissions, OAuth scopes, enabled write groups and input validation all apply. An administrator connection has access only to the supported operations in that catalog.
What an agent can change
Depending on its permissions and enabled write groups, an agent can edit pages, posts, navigation, public custom content, taxonomies, supported custom fields, POM layouts and templates, CSS, forms, listings and the WooCommerce catalog. Read the destination's live contracts before editing. Some operations require a current revision from a read or preview.
POM AI does not expose user administration: agents cannot list accounts, create or delete users, change passwords, grant roles or permissions, or edit account authentication settings. Identifying the user who authorized a connection does not grant user-management operations.
Agents cannot create, upload or modify JavaScript or PHP source, install plugins or themes, execute shell commands, or run arbitrary SQL. Opening all write groups does not enable those operations. Generic plugin-option dumps and protected application metadata are unavailable.
HTML, CSS and existing scripts
HTML is filtered using the installation's WordPress KSES post-content rules, including for administrators with unfiltered_html and multisite super administrators. Script elements, inline event handlers and executable embedded content are excluded. Supported encoded HTML builder fields and block attributes are filtered too. Read the saved content back because unsupported markup can be removed.
Shortcode parameters and structured attributes cannot contain executable URL schemes or event-handler fragments. Use the theme's existing interactions and script selections for behavior.
CSS belongs in POM Theme's managed CSS controls. Keep edits concise and reuse existing rules. PHP, script execution and HTML breakouts are refused in CSS.
An agent can assign scripts that already exist in POM Theme's catalog to pages, posts and supported custom content, or to archive, single and feed templates. It selects existing identifiers and native feature tokens; it cannot supply a new script URL, path or source. See the template and script guide.
Custom-field operations require an explicit permitted key. They do not expose all metadata. Use the dedicated content, SEO, media, template and script tools for those features rather than editing their internal metadata.
Configure access
- Open Settings → POM AI → AI Tools and enable POM AI MCP, then open MCP server and enable the connection method your agent supports. Use HTTPS.
- Choose the existing WordPress user whose permissions match the work. Configure a service user when using API key authentication for writes.
- Open only the required write groups: Allow content writes, Allow option writes, Allow POM Theme writes or Allow WooCommerce writes. They are closed by default. Script assignments on content require both content and POM Theme writes.
- Authorize the necessary OAuth scopes. A listed tool can still refuse execution because a scope, capability or write group is missing.
- Preview a small change, inspect the result, apply it within the intended scope and verify the saved page or setting. Use JSON
trueandfalsefor boolean arguments, not quoted strings.
See getting started, client connections and multisite pages for the relevant connection route.
Credentials and verification
Keep keys and tokens in the client's protected connection configuration, outside prompts, pages and authoring plans. OAuth uses PKCE and site-bound grants; API keys and destination OAuth tokens are stored hashed on the site. Account connections keep the separately authorized destination credentials encrypted on the account service.
Remote image uploads accept raster images, reject private destinations and redirects, limit download size and pin the validated destination address. They require the WordPress cURL transport. A supported raster image payload is an alternative when remote downloading is unavailable.
Inspect Recent MCP logs in the settings panel and verify the affected content. Logs help identify operations; they do not replace checking the saved result or maintaining backups. Closing write groups or revoking access stops later operations and does not undo completed changes.
Stop or revoke access
Close the relevant write group to stop further changes. Use Reset OAuth or Revoke API key when the site connection should lose access. Account users can revoke an agent or disconnect a website from My Account → POM AI Management → AI site connections. Review affected content and restore a backup when necessary.