SmartCloud Agent Composer
| 开发者 | smartcloud |
|---|---|
| 更新时间 | 2026年8月4日 22:27 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | MIT |
| 版权网址: | 版权信息 |
详情介绍:
/wp-json/mcp/smartcloud-agent-composer. A compatible authenticated MCP client can connect directly; an OpenAI Connector tunnel is optional and is not bundled.
Core operation runs inside WordPress without requiring a WP Suite account, subscription, hosted service, provider plugin, or proprietary theme. Optional integrations are disclosed under External Services.
Key features
- Draft-only agent execution with separate WordPress authorship and Composer ownership.
- Explicitly validated and activated Config Sets; imports and edits never activate automatically.
- Optimistic concurrency for configuration and draft changes.
- Gutenberg block-tree, pattern, template, post-type, language, excerpt, field, and relation validation.
- Document and structured-record Blueprints, including registered REST-visible fields approved by the Site Contract.
- Human-readable, ordered relation editing constrained by allowed target types, statuses, and cardinality.
- Existing-image assignment and optional bounded raster ingestion from approved HTTPS hosts.
- Short-lived preview drafts with ownership-checked cleanup.
- Redacted, tamper-evident audit events in an append-only SHA-256 hash chain.
- Checksum-protected Config Set lifecycle and active-theme/provider discovery.
安装:
- Install the plugin ZIP through Plugins -> Add New -> Upload Plugin and activate it.
- Open SmartCloud -> Agent Composer and review runtime, theme, and provider status.
- Create or import an inactive Config Set, review its Site Contract and Blueprints, then validate and explicitly activate it.
- Install and activate the separate WordPress MCP Adapter if an MCP client will use Composer.
- Create a dedicated WordPress user with the
smartcloud_agentrole and configure the client to authenticate as that user.
屏幕截图:
常见问题:
Can Composer publish or delete site content?
No. Agent-facing operations create and update drafts only. Normal content cannot be published or deleted through Composer. Only expired, Composer-owned temporary previews are removed automatically.
How does an agent connect?
Install the WordPress MCP Adapter, use a dedicated authenticated WordPress user, and connect a compatible MCP client to /wp-json/mcp/smartcloud-agent-composer. An optional Connector tunnel can expose the same endpoint without changing Composer's WordPress authorization boundary.
How does media handling work?
Composer can search readable Media Library images and assign an existing image as the featured image of a Composer-owned draft. If an administrator explicitly enables remote ingestion and allowlists an exact HTTPS host in the active Site Contract, Composer can download one bounded raster image, validate it, store it locally, and assign it to that draft. It cannot browse arbitrary hosts, follow redirects, edit existing media, or delete Media Library items.
How can configuration be preserved before uninstalling?
Open SmartCloud -> Agent Composer -> Audit & portability and export all configuration. The checksum-protected JSON contains Config Sets but excludes credentials and site-specific audit history. Restored sets remain inactive until reviewed, validated, and activated.
更新日志:
- Added governed draft creation and updates, registered structured-field writes, relation search and ordering, existing featured-image assignment, and optional allowlisted remote raster ingestion.
- Added versioned Config Sets, theme/provider discovery, validation receipts, optimistic concurrency, audit chaining, previews, portability, and explicit lifecycle controls.
- Added Universal Gutenberg, SmartCloud Recommended, and Detected Theme Starter starting contracts.
- Packaging: Renamed the bundled shared runtime directory to
smartcloud-wpsuite. - Migration: Made
smartcloud-wpsuitethe canonical admin, option, and REST namespace while retaining legacy aliases for rolling upgrades. - Initial public release.