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

Connect Directly to the Composer MCP Server

Composer registers WordPress Abilities and a dedicated MCP server. The separate WordPress MCP Adapter supplies the MCP transport that compatible clients use to discover and invoke those abilities.

The Composer endpoint is:

<wordpress-url>/wp-json/mcp/smartcloud-agent-composer

Prerequisites​

  • WordPress 6.9 or newer and PHP 8.1 or newer.
  • SmartCloud Agent Composer installed and active.
  • One validated and active Config Set with at least one Blueprint.
  • The official WordPress MCP Adapter installed and active.
  • A dedicated WordPress user with the smartcloud_agent role.
  • HTTPS for any remote HTTP connection.

WordPress includes the Abilities API in core from 6.9. Follow the MCP Adapter's current release instructions rather than downloading an arbitrary development branch. Its primary package installation is composer require wordpress/mcp-adapter; its official repository also documents a traditional plugin release path.

Create the execution identity​

Create a dedicated WordPress account such as <agent-user> and assign the smartcloud_agent role. Do not reuse an administrator account.

The role permits Composer draft execution but does not grant publishing, normal-content deletion, plugin or theme management, user management, media upload, or unfiltered HTML. Keep credentials outside Config Set JSON, logs, screenshots, prompts, and source control.

For HTTP clients that support WordPress Application Passwords, create an application password for this dedicated account and store it in the client's secret store. Never paste it into a public MCP configuration example.

Verify the server before connecting a client​

Open SmartCloud -> Agent Composer -> Overview as an administrator and confirm:

  • the expected active Config Set,
  • the endpoint path,
  • draft-only execution readiness,
  • current theme and provider readiness.

Then inspect the server with a compatible MCP inspector or client. The WordPress MCP Adapter repository documents both HTTP and local WP-CLI/stdio transports. A generic HTTP client configuration should contain:

Server URL: <wordpress-url>/wp-json/mcp/smartcloud-agent-composer
Username: <agent-user>
Password/token: <stored-application-password>

The exact authentication fields depend on the client. Do not expose the endpoint anonymously or put long-lived credentials in command history.

Expected governed workflow​

The client should perform these steps in order:

  1. Load the Blueprint for the requested page_type.
  2. Load the active design context.
  3. List approved patterns and required placeholders.
  4. Read approved reference content or search existing media only when needed.
  5. Assemble and validate the proposed sections without saving.
  6. Create an agent-owned draft with a unique idempotency key.
  7. Load the preview and report validation results and URLs for human review.

A safe first request is:

Using page type <page-type>, load the active blueprint and design context, list
approved patterns, validate a minimal content plan, create an agent-owned draft,
and return its preview. Do not publish, delete normal content, upload media, or
change WordPress configuration.

Confirm in WordPress that the result is a Draft and that no published content changed.

Updating a draft​

Composer requires the current modified_gmt and revision token for updates. A client must read the draft immediately before changing it and submit those values unchanged. If another editor saved the draft first, Composer returns a conflict; reload and review instead of retrying with stale tokens.

Troubleshooting​

  • Endpoint missing: confirm the MCP Adapter and Composer are active, then reload WordPress after clearing stale PHP processes.
  • Unauthorized or forbidden: authenticate as the dedicated user and confirm the smartcloud_agent role; do not solve this by granting Administrator.
  • No active configuration: validate and explicitly activate one Config Set.
  • Blueprint not found: use the exact stable page_type configured in the active set.
  • Pattern or block missing: rescan the site, confirm registration, and update a cloned working Config Set.
  • Provider not ready: inspect Theme & providers and the provider plugin's own configuration.
  • Conflict: reload the draft and use its current concurrency tokens.
  • Preview invalid: read the validation report; do not publish or bypass the failed constraint.

The direct MCP path sends requests between the configured client and WordPress. Composer itself does not require an OpenAI account, Connector tunnel, or WP Suite subscription for this workflow.