POM AI MCP capability map
The site MCP manages the supported content and configuration of one WordPress site. The network MCP selects an existing site and routes its supported operations to that destination. Discover the destination before editing: its theme, plugins, enabled features and actor permissions determine which operations can run.
Site writes require a preview and approval from the original WordPress actor. Network super administrators can explicitly authorize temporary work sessions for selected supported operations on one destination; other writes retain exact approval. A prepared write job combines up to 100 explicit operations under one review, with each operation usable once. Compatible MCP clients show a confirmation form; the review link remains available. The assistant waits for approval and executes the original operations with the shared approval_id. Approval does not replace OAuth scopes, site identity, write gates, object permissions or required revisions. See Confirm writes.
Site capabilities
| Area | Supported work |
|---|---|
| Content | List, search, count, read, create, update, publish and delete posts, pages and supported public CPT items; edit slug, text, excerpt and status. Revisioned content authoring also supports hierarchy and order. |
| SEO | Read and update the supported Yoast and Rank Math title and description fields. |
| Taxonomies | Discover taxonomies; read, create, edit, delete and assign terms. Edit names, explicit slugs, descriptions and parent terms. With POM Theme, set thumbnail/background images and native term positions. Name-only and order-only batches support up to 50 revisioned terms. Omitted slugs stay unchanged. |
| Media | List, count and read attachments; upload raster images from a public URL or base64; edit title, caption, description and alt text; delete media and set or remove supported content thumbnails. Upload payloads have size and image-type limits. |
| Navigation | Read and create menus; create, update, delete and reorder items; assign registered menu locations. Read and assign front, posts and privacy pages. There is no whole-menu deletion tool. |
| Comments and metadata | List comments and pending comments, create, approve, spam, trash or delete individual comments. Read, update or delete supported post/term custom metadata. Private application storage is excluded. |
| Site settings | Read site information and approved options; edit the supported option allowlist. This does not provide unrestricted option access. |
| Theme settings | Discover live settings and contracts, read values, patch supported fields and apply supported setting batches. Configure settings such as branding, header and layout only where their live contracts allow it. |
| Theme content models | Configure CPTs, taxonomies and custom fields; create, update, delete and assign managed archive, single and feed HTML templates. Refresh discovery after structural changes. |
| Theme styling | Read/edit global CSS; list, create, update and delete managed stylesheets; inspect and regenerate generated CSS assets. Inspect and assign existing registered content scripts. Arbitrary JavaScript and PHP creation are excluded. |
| Search and listings | Discover listing contexts; save supported queries; configure facets for available contexts; rebuild the facet index and build listing markup. |
| Forms | Discover, read, create and save supported POM forms using the live form contract. |
| Authoring plans | Preview and create a bounded plan, prepare and approve one step at a time, inspect progress, discard the journal and adopt matching content/form results after interrupted creation. Discarding a journal does not undo its completed writes. |
| WooCommerce | Read products, variations, global attributes, attribute terms and coupons; create/update simple or variable products; create/update/delete variations; update up to 50 variations per batch; create global attributes and assign product attributes; create/update/delete coupons and clear up to 100 trashed coupons per operation; read aggregate catalog counts. There are no product-deletion, order-management or customer-management tools. |
| Cache | Inspect POM Cache availability and statistics; clear the current site’s supported HTML and progressive JSON cache when the integration is available. |
| Authoring guidance | Discover blocks, shortcodes, merge tags and schemas; validate supported content and template markup; retrieve the packaged site-authoring skill. |
Access and availability
WordPress content operations use wp:content:read or wp:content:write; theme operations use pom_theme:read or pom_theme:write; commerce operations use woocommerce:catalog:read or woocommerce:catalog:write. The corresponding base MCP scope is also required. Discover each tool’s exact scope list.
Site write controls separate content, options, POM Theme and WooCommerce. Cache clearing additionally requires its integration and the site-management capability. A listed tool can report unavailable when the corresponding theme feature or integration is absent. WooCommerce tools are registered only while WooCommerce is active.
Unpublished or password-protected content requires object-level permission. Commerce writes check the selected product, variation, parent product or coupon; generic post tools cannot modify commerce objects. New products default to draft. Publication requires the relevant publishing capability.
The standard transport and the native transport share the operation callbacks, schemas and approval workflow. Native transport on supported WordPress versions adds pom_get_site_context for the site UUID, connection identity and contract. The installed catalog with POM Theme and WooCommerce contains 145 shared site tools, plus that native context tool. Enabling network delegation adds the two work-session tools described below. Counts can change with the active integrations; discovery is authoritative.
Network capabilities
The main-site connection adds five tools:
| Tool | Purpose |
|---|---|
pom_network_get_context |
Identify the network, contract and enabled write groups. |
pom_network_list_sites |
List existing, eligible subsites in pages of up to 20 and report POM AI activation. |
pom_network_discover_site |
Read a chosen destination’s identity, actual tool schemas, scopes and write groups. |
pom_network_read_site |
Run a discovered read-only or validation tool on that destination. |
pom_network_execute_site |
Preview, request approval and execute a discovered write on that destination. |
The network requires the supported native transport, POM AI active on the main site and destination, a current main-site Unlimited network entitlement and an authorized super-administrator OAuth connection. It keeps the original destination-tool scopes and capabilities. Delegation does not require a separate child MCP credential; independent child access has its own authorization requirements. See Manage multisite websites.
Write controls separately cover the legacy page-authoring operation, broader content/forms/media/taxonomies, theme/content-model/search configuration, site options, WooCommerce and cache. The legacy page control alone allows pom_site_save_content for pages; newly exposed WordPress page aliases belong to broader content management. Broader groups start disabled.
Use the explicit blog_id for routing and the discovered destination UUID inside its tool arguments. Approval happens on the selected destination. The network cannot recursively invoke another network/account gateway and does not route the resource or prompt interfaces.
Complete site tool names
The following groups list the supported registered operations. Read includes validation and markup-building operations that do not persist changes. Write requires approval even when the stored change is a plan journal rather than public content. Preparing a write job creates a review only; its contained operations remain unapplied until approval and execution.
Content and SEO
Read: wp_get_posts, wp_get_post, wp_count_posts, wp_get_post_types, wp_get_pages, wp_get_page, wp_search, wp_get_seo_meta, pom_site_get_content.
Write: wp_create_post, wp_update_post, wp_delete_post, wp_create_page, wp_update_page, wp_delete_page, wp_update_seo_meta, pom_site_save_content.
Media
Read: wp_get_media, wp_get_media_item, wp_count_media.
Write: wp_upload_media_from_url, wp_upload_media, wp_set_featured_image, wp_update_media, wp_delete_media.
Taxonomies and terms
Read: wp_get_terms, wp_get_term, wp_get_categories, wp_get_tags, wp_get_taxonomies, wp_count_terms.
Write: wp_create_term, wp_update_term, wp_delete_term, wp_rename_terms, wp_reorder_terms, wp_add_post_terms.
Comments and custom metadata
Read: wp_get_term_meta, wp_get_comments, wp_get_pending_comments, wp_get_post_meta.
Write: wp_update_term_meta, wp_delete_term_meta, wp_create_comment, wp_delete_comment, wp_approve_comment, wp_spam_comment, wp_trash_comment, wp_update_post_meta, wp_delete_post_meta.
Site settings and navigation
Read: wp_get_site_info, wp_get_option, wp_get_menus, wp_get_menu_items, wp_get_menu_locations, wp_get_site_pages.
Write: wp_update_option, wp_create_menu_item, wp_update_menu_item, wp_delete_menu_item, wp_reorder_menu_items, wp_create_menu, wp_assign_menu_location, wp_set_site_pages.
Authoring discovery and validation
Read: pom_get_authoring_skill, pom_get_authoring_context, pom_get_available_shortcodes, pom_get_shortcode_schema, pom_validate_builder_content, pom_get_available_mergetags, pom_get_template_schema, pom_validate_template_markup, pom_get_available_blocks, pom_get_block_schema, pom_validate_block_content.
POM Theme settings, styles and templates
Read: pom_theme_get_status, pom_theme_list_settings_schema, pom_theme_get_settings_values, pom_theme_get_global_css, pom_theme_get_custom_css, pom_theme_get_generated_css, pom_theme_get_css_build_info, pom_theme_list_html_templates, pom_theme_get_html_template, pom_theme_get_template_assignments, pom_theme_get_script_catalog, pom_theme_get_content_scripts, pom_theme_get_settings_catalog, pom_theme_get_setting_contract.
Write: pom_theme_update_setting, pom_theme_update_settings_batch, pom_theme_update_global_css, pom_theme_upsert_custom_css, pom_theme_delete_custom_css, pom_theme_generate_assets, pom_theme_upsert_html_template, pom_theme_delete_html_template, pom_theme_assign_template, pom_theme_configure_content_model, pom_theme_assign_content_scripts, pom_theme_patch_settings.
Queries and faceted search
Read: pom_site_get_listing_catalog, pom_site_build_listing.
Write: pom_site_save_query, pom_site_save_facets, pom_site_reindex_facets.
Forms
Read: pom_site_find_forms, pom_site_get_form_contract, pom_site_get_form.
Write: pom_site_create_form, pom_site_save_form.
Network work sessions
Request: pom_site_request_work_session prepares a main-site web authorization for selected groups on one destination, lasting one, four or eight hours after approval. It applies no site changes.
Read: pom_site_get_work_session returns scope, status, expiry and operation receipts. Permitted writes use work_session_id and a unique operation_id; deletion tools and composite plans retain exact approval. These tools are available when network delegation is enabled and require the main-site network connection.
Combined write reviews
Read: pom_site_get_write_job.
Prepare review: pom_site_prepare_write_job previews explicit operations and requests one approval without applying them. Each operation retains its own scopes, capabilities and write groups.
Resumable authoring plans
Read: pom_site_preview_plan, pom_site_get_plan.
Write: pom_site_adopt_plan_form, pom_site_create_plan, pom_site_prepare_plan_step, pom_site_apply_plan_step, pom_site_adopt_plan_content, pom_site_discard_plan.
WooCommerce catalog and coupons
Read: wc_get_products, wc_get_product, wc_get_store_stats, wc_get_product_variations, wc_get_variation, wc_get_product_attributes, wc_get_attribute_terms, wc_get_coupons, wc_get_coupon, wc_get_coupon_count.
Write: wc_create_product, wc_update_product, wc_create_variation, wc_update_variation, wc_delete_variation, wc_batch_update_variations, wc_create_product_attribute, wc_set_product_attributes, wc_create_coupon, wc_update_coupon, wc_delete_coupon, wc_empty_coupon_trash.
POM Cache
Read: pom_cache_get_status.
Write: pom_cache_clear_site_cache.
Native site identity additionally uses pom_get_site_context.
Resources and prompts
Direct site connections expose resources for the site summary, builder guide, available shortcodes, layout/content-model/header/media guidance, theme modules, settings schema, archive/single/feed template guidance and merge tags. Individual shortcode schema resources depend on the active site catalog.
The eight prompt recipes are:
create_landing_page_with_pom_builder: Create a landing page using the POM classic builder workflow.update_pom_builder_page_preserving_structure: Update an existing POM classic builder page while preserving structure and merge tags.create_pom_content_model: Create CPTs, taxonomies, custom fields, POM templates, assignments and test content.change_pom_header_style: Change POM header layout, behavior and colors through theme settings.create_page_with_generated_media: Create a complete POM page, upload generated images to media and use them in the page layout.create_archive_template_pom: Create a POM archive template with validated merge tags.create_single_template_pom: Create a POM single template with validated merge tags.create_feed_template_pom: Create a POM feed item template with validated merge tags.
Prompt recipes supply instructions; they do not apply changes or bypass approvals. A recipe about generated media does not mean this MCP generates AI images itself.
Boundaries
Neither connection creates, deletes or provisions subsites; manages users, roles, credentials, licenses or billing; installs or updates plugins, themes or WordPress; performs backups or infrastructure work; or executes arbitrary PHP, JavaScript, shell commands or SQL. Theme settings and custom metadata follow their supported contracts rather than unrestricted storage access.
The POM AI administration screens for AI copy, long posts, translations, image generation/editing and credits are separate features. Their paid generation operations are not exposed by this site-management tool catalog.
Writes and batches are not database transactions. Inspect complete, deleted, errors and nested destination results, then read back the target. An interrupted or partially applied operation must be inspected before retrying. See Limits and Security.