Connect WordPress to GoBuildWP Cloud and Your AI Apps

Connect WordPress to GoBuildWP Cloud: what each screen asks

Before you start, switch AI abilities on under GoBuildWP, Settings. Cloud tests the connection before it finishes, so a site with abilities off refuses to begin and tells you to turn them on first.

The GoBuildWP Cloud panel sits on the Connect screen. Select Connect to GoBuildWP Cloud and a browser tab opens on app.gobuildwp.com, where you sign in and choose the access level for this site. You are then sent back to wp-admin for a confirmation that spells out the whole grant in one sentence: this site, your Cloud account (its email shown masked), the access level, and the WordPress user the connection will act as. Select Confirm, or Cancel to leave the site untouched.

Behind the confirmation, the browser only ever carries a one-time code. The site itself creates an access token for Cloud and hands it over server to server, then Cloud calls the site back to check the connection works. The panel then reads This site is connected to GoBuildWP Cloud, with the account and a Site ID, and the site appears under Sites in your Cloud account with a heartbeat and a last-check time.

Choose the WordPress user deliberately, because the confirmation names whoever is signed in to wp-admin. Every call that arrives through Cloud runs as that user, with that user's capabilities, under the access level you picked.

• AI abilities switched on under Settings
• Signed in to wp-admin as the user Cloud should act as
• The confirmation sentence read before selecting Confirm
• The site listed under Sites in Cloud, with a recent last check

Cloud connection errors, by the message you see

Every failure in the connection flow leaves the site as it was, except where the message says a token was revoked, which is the site cleaning up after itself.

• GoBuildWP Cloud cannot be used from this site: the site is not on HTTPS. Cloud needs HTTPS outside a local development environment.
• The site cannot create the signing key GoBuildWP Cloud needs: PHP's sodium extension is missing. Ask the host to enable it.
• This site could not reach GoBuildWP Cloud: an outbound request from the server failed. Nothing changed; try again, and if it persists, check the host's outbound firewall.
• GoBuildWP Cloud could not finish connecting this site, so the access token was revoked: Cloud could not reach the site over the internet to check it. A site behind a login wall, an IP allowlist or a private network cannot be connected until Cloud can reach its MCP endpoint.
• This connection request expired or was started by another user: a request lasts about ten minutes and belongs to the admin who started it. Start again from the same account.
• This site is already connected to GoBuildWP Cloud: one site links to one Cloud account at a time. Disconnect first, then connect again.
• Connection cancelled: you, or the Cloud tab, cancelled before confirming. Nothing was changed.

What an AI app can call through one Cloud link

An app connected to Cloud does not see each site's abilities directly. It sees a small set of gateway tools: sites_list to find the sites it may reach, site_tools to read one site's tool list and schemas, run to call one tool on one site, changes and change_detail to read a site's change log, and undo to roll a recorded change back, which the site may ask to confirm. A typical request therefore runs sites_list, then site_tools, then run, and the agent names the site in each call.

With a Pro licence linked, bulk_run runs the same tool with the same arguments on many sites in the background, and bulk_status reports per-site results. It needs bulk permission on that app's connection, and it accepts a dry run, which is the way to start: read what would happen on every site before anything does. The Bulk actions screen in Cloud shows recent runs and starts new ones by hand.

If a site's tool list is empty in Cloud, open the site under Sites and use Check now; the gateway caches what each site reported at its last check.

Changing a site's access level later

The token Cloud holds is listed among the site's access tokens on the Connect screen, but its limits cannot be edited there, because Cloud relies on what was agreed when the site connected. To move a site from Read Only to Production Safe, or back, disconnect and connect again with the new level. Revoking the token from the list does the same as Disconnect: the link is dropped and Cloud is told.

Narrowing per app needs no reconnection. In Cloud, an app's connection can be limited to some sites and made read-only, and that applies at once. For a site most apps should only read but one should edit, connect the site as Production Safe and make every other app's connection read-only.

Looking after connected sites from the Cloud account

Once sites are connected, the Cloud account is also where you look after them as a group, without an AI app in between. Sites running GoBuildWP Free 1.18.0 or newer report their pending updates, their newest backup and their safety settings to Cloud on their own, and each screen below reads those reports. Without Pro you still see the update and backup lists; acting on many sites at once, policies and the SEO report need a Pro licence linked to the account.

• Updates: what each site needs, and with Pro, updating some, one site, one plugin everywhere or everything, after a confirm screen
• Backups: the newest UpdraftPlus, BackWPup, Duplicator or All-in-One WP Migration backup on each site, and with Pro, starting one
• Safety policies: one safety profile, approval mode and ability list pushed to many sites, as far as each site's owner allows
• Team and clients: admins and members who run the sites, and clients who see only theirs, read-only
• SEO report: Search Console for every site, read through each site's own Google Site Kit