Requirements and responsibilities
Name the team, server, hostname, owner and affected users for the Ghost application. Record the current version and the actual business flow that must survive the change. Confirm the current dashboard form, plan eligibility, and server capacity before committing a resource change. A one-click catalog listing is discovery, not permission or proof that the connected MCP profile can install it.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Ghost content and member exports · Ghost staff roles and invites · Ghost publishing and scheduling · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Prepare a non-sensitive test input and an acceptance record. Keep access to the app administrator and an independent observer where possible; omit secrets from AI prompts and client reports.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Ghost content and member exports · Ghost staff roles and invites · Ghost publishing and scheduling · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
For a Docker app, identify persistent volumes, bind mounts, external databases and app-level export requirements. A Docker backup briefly stops the app, and an in-place restore replaces current state. Agree a maintenance window and owner before any action that interrupts the service or overwrites data.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Ghost content and member exports · Ghost staff roles and invites · Ghost publishing and scheduling · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Illustrative situation
An editorial team runs Ghost with weekly posts and occasional newsletters. It needs to monitor staff rights, publishing and exports before an upgrade.
Choose the approach
A Ghost content export, member export and theme export are separate; a Docker backup covers additional runtime state.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Ghost content and member exports · Ghost staff roles and invites · Ghost publishing and scheduling · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Do not restore an older app snapshot without accounting for newer posts or members.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Ghost content and member exports · Ghost staff roles and invites · Ghost publishing and scheduling · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Review publication health
- Where
- Ghost Admin and public URL
- Permissions
- Authorized Ghost application administrator or delegated role with rights for this task; hosting access alone is insufficient.
- Inputs
- Recent posts, scheduled items, mail status
- Action
- Check public article, scheduled queue, staff access and any failed newsletter sends. Record app version and errors.
- Expected result
- A dated editorial baseline.
- Verify
- Open newest public post and a scheduled draft preview.
- If it fails
- If newsletter send failed, diagnose provider separately from page uptime.
Sources: Ghost content and member exports · Ghost staff roles and invites · Ghost publishing and scheduling
Step 2 of 5
Audit staff permissions
- Where
- Ghost staff settings
- Permissions
- Authorized Ghost application administrator or delegated role with rights for this task; hosting access alone is insufficient.
- Inputs
- Editor/author/admin roster
- Action
- Compare staff roles with current team and revoke departed accounts while preserving an administrator.
- Expected result
- A current staff roster.
- Verify
- Test a limited editor in a fresh session.
- If it fails
- If an editor has admin settings access unexpectedly, correct role before next release.
Sources: Ghost content and member exports · Ghost staff roles and invites · Ghost publishing and scheduling
Step 3 of 5
Inspect backup and exports
- Where
- Ghost Import/Export and xCloud Docker Backup
- Permissions
- Authorized xCloud team/site operator with the discovered write scope for this exact operation and owner approval for its target and interruption.
- Inputs
- Content JSON, member CSV, theme ZIP, snapshot
- Action
- Export current content and members where used; inspect completed app backup and persistent media/database scope.
- Expected result
- A recoverable editorial checkpoint.
- Verify
- Open exports and compare counts to Ghost Admin.
- If it fails
- If an export is incomplete, fix it before upgrade.
Sources: Back up and restore Docker apps · Docker backup operations and storage constraints · Ghost content and member exports
Step 4 of 5
Test an editorial change
- Where
- Ghost editor and public browser
- Permissions
- Authorized Ghost application administrator or delegated role with rights for this task; hosting access alone is insufficient.
- Inputs
- Harmless draft, image, schedule time
- Action
- Preview, publish and revise a small post; inspect URL, metadata and media signed out. Check scheduling timezone if used.
- Expected result
- Publishing works after maintenance.
- Verify
- Compare revision history and public result.
- If it fails
- If post or email fails, pause further releases and inspect app logs.
Sources: Ghost content and member exports · Ghost staff roles and invites · Ghost publishing and scheduling
Step 5 of 5
Record update and recovery rule
- Where
- Editorial runbook
- Permissions
- Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
- Inputs
- Update owner, backup ID, post/member delta
- Action
- Set a maintenance window and decide how newer content will be preserved before any snapshot restore. Assign one person to monitor publication and mail.
- Expected result
- A safe ongoing procedure.
- Verify
- Have another editor locate last good backup and export.
- If it fails
- If recent members are missing from snapshot, reconcile before restore.
Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · Ghost content and member exports
Maintenance
Review this task after app or template updates and at the cadence agreed with the owner. Record failures as dated observations rather than assuming host health proves service health.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Ghost content and member exports · Ghost staff roles and invites · Ghost publishing and scheduling · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Watch access changes, backup completion, free storage and external providers. Recheck integrations after credential, DNS, mail or source-data changes.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Ghost content and member exports · Ghost staff roles and invites · Ghost publishing and scheduling · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Recovery decisions
Before data recovery, identify incident time, completed backup, target and records created after the snapshot. Preserve current evidence and live data before replacement.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Ghost content and member exports · Ghost staff roles and invites · Ghost publishing and scheduling · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Use the documented dashboard or application recovery procedure with the authorized owner. Repeat the task-specific limited-user check; reconcile newer records before reopening writes.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Ghost content and member exports · Ghost staff roles and invites · Ghost publishing and scheduling · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
AI handoff
Connect an authorized xCloud MCP profile and discover its exact tools and team scope. The packaged REST wrapper is GET-only; use dashboard or app controls for undocumented writes.
Supported scope
- Confirm requirements and inspect resources mcp · read
Discover the connected profile and operation schema first; only teams granted to the connection are visible.
Checkpoint: Confirm exact team, server and site identity. Use dashboard_url returned by the resource; do not invent a dashboard link.
Operation identifiers and scopes to discover
teams.index, servers.show, sites.show
Scopes: read:servers, read:sites
xCloud MCP documentation and connection profiles · xCloud agent capability boundaries
Copyable agent brief
Manual checkpoints
- Approve exact site, target, cost and any write or maintenance window after inspecting the proposed plan.
- An authorized Ghost administrator must configure and test app users, content, integrations and business rules in the app.
- Native WordPress staging, backup schedule/settings, push/pull and all restores are dashboard-only; Docker restore is dashboard-only and replaces state.
- Reconcile data created after the chosen recovery point before any destructive restore.
Feature coverage
- editorial-ops decision, evidence and task action (covered): The procedure identifies the authorized task boundary and observable result. Review publication health Audit staff permissions Inspect backup and exports Test an editorial change
- backup, ongoing operation and recovery (covered): Recovery and maintenance are checked in the task procedure. Test an editorial change Record update and recovery rule