SmartCloud Agent Composer
| 开发者 | smartcloud |
|---|---|
| 更新时间 | 2026年8月14日 20:44 |
| 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.
更新日志:
- Compatibility: Allow governed draft creation on SQLite-backed WordPress installations with an atomic, expiring idempotency lock.
- Taxonomies: Add a governed search, optional creation, draft assignment, and read-back workflow for Site Contract-approved public terms.
- Administration: Discover attached taxonomies and configure search, assignment, creation, limits, assignment mode, and hierarchical parent policy in the guided Site Contract editor.
- Safety: Keep term creation confirmation-gated and idempotent, restrict relationships to Composer-owned assigned drafts with optimistic concurrency, and expose no term edit or deletion operation.
- Relations: Make field contracts identify the required relation lookup, write, and verification workflow.
- MCP: Add concrete result schemas and stronger descriptions, including the editable-content alias, so clients use
search-relation-targetsfor post IDs. - Discovery: Count and paginate
list-content-draftsonly after Composer policy and WordPress capability filtering.
- Multisite: Store shared Hub ownership per site and recognize network-activated owners.
- Hub admin: Load the WebCrypto vendor before the shared admin bundle.
- Dependency: Rebuilt the bundled WP Suite Hub and Amplify vendor runtime with exact supported SmartCloud Amplify UI 6.15.5/3.6.5/6.15.5 versions.
- Compatibility: Restored ownership-safe WP Suite Theme CSS fragment updates on WordPress-managed Custom CSS storage.
- Initial public release.
- Fixed guided rule-list editing so spaces and new lines remain available while typing, and added pointer feedback to enabled switches.