<div class="wp-block-smartcloud-ai-kit-feature"></div>
Sign In

Agent Composer Overview

Building a WordPress site is a defined project. Operating its content continues for years.

Agent Composer lets agencies turn the content types, patterns, and editorial rules already built into a WordPress site into controlled workflows for ChatGPT, Codex, and other compatible agents. Clients can create complete, validated drafts without rebuilding layouts, breaking the theme, or receiving unrestricted WordPress access.

Build the site your way. Let clients create content safely without breaking the design.

Built for the work that starts after launch​

An agency may build the original site with a block theme, a custom theme, approved patterns, custom post types, or another established WordPress workflow. Composer does not replace that work.

Instead, the agency describes recurring content operations as Config Sets and Blueprints. A Blueprint can define the allowed content type, required sections, supported fields, taxonomies, metadata, and validation rules for a landing page, solution, case study, article, or another repeatable format.

The client's compatible AI agent can then use only the Composer abilities exposed for that workflow. The result is a structured WordPress draft that follows the existing content model and remains subject to human review.

The operating model​

Composer joins four kinds of information:

  1. A Config Set identifies one versioned configuration package and its lifecycle state.
  2. A Site Contract describes site-wide editorial, structural, and design rules.
  3. Blueprints define the allowed target, template, patterns, blocks, sequence, excerpt policy, and constraints for each page type.
  4. Theme and provider discovery confirms what the current WordPress installation can actually render or execute.

Only one validated Config Set is active on a site. Editing happens in a separate working copy; imported packages also remain inactive until an administrator reviews, validates, and activates them.

From agency build to controlled release​

Draft creation and production release are separate control points. Composer governs what the agent can create or modify in WordPress. A human approval process remains responsible for accepting the result. Production publishing can use the normal WordPress workflow or, in a static architecture, a separate manual or scheduled Static Publisher release.

Use the agent you already have​

Composer is the controlled WordPress execution layer, not a separate AI runtime. The user can work from ChatGPT, Codex, or another compatible agent and keep the reasoning, model access, and subscription in that environment.

Composer receives a structured operation, checks it against the active Config Set and Blueprint, validates the requested change, and applies only the allowed WordPress action. Compatibility depends on a supported MCP transport and client; Composer does not claim universal compatibility with every AI agent.

What an agent can do​

After an authenticated client connects through the WordPress MCP Adapter, Composer can expose abilities that:

  • load the current design context and selected page blueprint,
  • list approved patterns and registered blocks,
  • validate a proposed section plan without saving it,
  • create an agent-owned draft,
  • update only a draft assigned to the current agent,
  • inspect a draft and obtain a fresh preview,
  • search existing Media Library images and materialize valid Image blocks,
  • delegate a component operation to an installed provider that owns the corresponding WordPress Ability.

Composer does not expose content publishing, normal-content deletion, media upload, theme or plugin modification, or user administration. Preview is a real short-lived WordPress draft, and expired preview drafts are removed only after Composer verifies their private ownership markers.

The existing theme remains in control​

A contract can refer only to capabilities that exist on the current site. Composer therefore discovers templates, registered patterns, registered blocks, theme.json settings, and an optional theme manifest. Validation fails closed when a required template, pattern, block, or provider is missing.

This model supports two useful configurations:

  • Agent Canvas is an optional reference theme and starter environment for demonstrating Composer's complete contract model. It is not required and does not replace an agency's theme, patterns, or design process.
  • Any compatible third-party block theme can provide a partial capability set. An administrator creates a smaller contract using only the templates, patterns, blocks, and presets that discovery confirms.

Changing the theme never silently imports or activates a new Config Set.

Safety and accountability​

Every content write checks the full block tree, target post type, template, ownership, agent capability, and optimistic-concurrency token. Audit events are redacted and stored in a tamper-evident SHA-256 hash chain. Configuration changes use explicit Apply or Discard controls, and activation is bound to a fresh validation receipt for the exact site and checksum.

The dedicated smartcloud_agent role is the recommended execution identity. It has Composer's draft capability without receiving publishing, deletion, plugin-management, theme-management, media-upload, or unfiltered-HTML privileges.

Private WordPress can stay private​

For a local or firewall-protected WordPress environment, the optional Secure MCP Tunnel establishes an outbound connection to supported agent integrations. No inbound WordPress or MCP endpoint needs to be opened solely for the agent.

The transport does not bypass Composer's permissions. Draft-only rules, Blueprint validation, ownership checks, and other operation-level controls remain enforced inside WordPress. Direct MCP remains available when the client can already reach the authenticated Composer endpoint.

What Agent Composer does not do​

Composer does not:

  • design the original website;
  • replace the active theme or the agency's visual system;
  • provide its own general-purpose AI model or require separate WP Suite AI tokens;
  • grant an agent unrestricted WordPress administrator access;
  • treat draft creation as automatic production publishing;
  • require Agent Canvas, Static Publisher, or Static Site Guardian.