Connect AI to GoBuildWP Cloud: Claude, ChatGPT, Cursor
Connect AI to GoBuildWP Cloud: step-by-step setup for Claude, ChatGPT, Claude Code, Cursor, VS Code, Codex and Windsurf, with test prompts and fixes.
This is the second half of a Cloud setup. Your WordPress sites are already connected to your Cloud account; now your AI app needs to reach Cloud. It needs one link, https://app.gobuildwp.com/mcp, and one sign-in with your Cloud email and password, after which it can see every site you allow. Nothing is installed on your computer for the chat apps, and nothing secret is copied anywhere unless you choose a personal token.
What you will do 5 steps
Open your AI app's connector or MCP settings
Paste the GoBuildWP Cloud link
Sign in and choose which sites the app may reach
Switch the connector on in a chat
Ask it to list your sites
Before you connect an app
You need a GoBuildWP Cloud account at https://app.gobuildwp.com with at least one site connected from wp-admin; the GoBuildWP Cloud guide covers that part. Then open Connect AI in Cloud. The page shows the link, the steps for the app you pick, and a status box that changes from Not connected yet to Connected the moment your app finishes signing in, then shows when it was last used and which tool it last ran.
Sign-in is the recommended route because the app never holds a password or a long-lived secret, and you can revoke it from Cloud in one click. A personal access token is the fallback for tools that cannot open a browser: scripts, CI jobs and a few editors. Give a token an expiry and only the sites it needs.
- A Cloud account with a confirmed email
- At least one site listed under Sites in Cloud
- The AI app you already use, signed in to your own account there
What the Allow screen asks
Whichever app you use, sign-in ends on the same page at your Cloud address, titled with the app's name and the words wants to use your WordPress sites. Choose all your sites, including ones you connect later, or tick only the ones this app should see. Tick Read only for this app when the app should look things up but never change anything, then click Allow and you are returned to the app.
If that page names an app you did not just start connecting, click Deny. Apps can register themselves, so neither a name nor matching timing proves identity. Review the client identity and requested access shown by the flow, and allow only the authorization you intended.
Pick your AI app
Every app below uses the same link, https://app.gobuildwp.com/mcp, and signs in with your GoBuildWP Cloud account. Jump to yours; the steps were checked against each vendor's own documentation on 2026-10-09.
- Claude claude.ai, Claude Desktop and mobile
- ChatGPT chatgpt.com
- Claude Code Terminal
- Cursor Editor
- VS Code GitHub Copilot in VS Code
- Codex Codex CLI, IDE extension and app
- Devin Desktop Formerly Windsurf (Cascade)
- Something else Antigravity, Gemini CLI, Zed, Kiro, JetBrains (Junie), Cline, LM Studio, Goose
Connect Claude
Before you start. Custom connectors work on every Claude plan; the free plan allows one. On Team and Enterprise an owner adds GoBuildWP first under Organization settings → Connectors, then each member connects it.
Open Claude's connector settings
On claude.ai or in the Claude Desktop app, open Customize, then Connectors. The button below takes you straight there.
Add GoBuildWP as a custom connector
Click + Add, then Add custom connector. Name it GoBuildWP, paste this link as the remote MCP server URL, and click Continue.
https://app.gobuildwp.com/mcpThe next screen: keep the defaults
- Claude detects that GoBuildWP uses sign-in. Click Continue.
- Authentication: Sign in when needed (or Sign in now).
- OAuth client: Use Claude's published identity (Recommended).
- Request headers: leave empty. Click Add.
Sign in and allow access
Click Connect next to GoBuildWP (Claude may open it for you straight away). A browser tab opens on your Cloud address.
What you'll see on your Cloud address
- If you're signed out: the GoBuildWP Cloud sign-in page. Sign in with your Cloud email and password.
- A page titled Claude wants to use your WordPress sites (the app may show its own name here).
- Which sites? Pick All my sites, including ones I connect later, or Only the sites I pick and tick them.
- Read only for this app: tick it if this app should only look things up. You can start read-only and reconnect later to allow changes.
- Click Allow. You're sent back to the app.
Only continue if you started this yourself a moment ago. If the page names an app you don't recognise, click Deny.
Turn GoBuildWP on in a chat
Start a new chat. Click + at the lower left of the message box, choose Connectors, and switch GoBuildWP on.
The first time Claude uses a GoBuildWP tool it asks your permission. Allow it once to check each call, or always for tools you trust.
A connector added on claude.ai also appears in Claude Desktop and the Claude mobile app.
Test it
Ask Claude one of the three test prompts, starting with “List my WordPress sites”.
Source: Claude Help Center: custom connectors using remote MCP.
Connect ChatGPT
Before you start. Adding your own MCP server depends on your ChatGPT plan and workspace policy; on Business and Enterprise an admin may have to allow custom MCP servers first. A GoBuildWP directory listing is planned; no availability date or plan eligibility is confirmed. Use the custom MCP setup described here and check your current account and workspace controls.
Open ChatGPT Plugins
Go to Plugins in ChatGPT. The button below opens it.
Add GoBuildWP as a custom MCP server
Select the + button, then Add custom MCP server, and fill in the form:
The form
- Name: GoBuildWP. The description is optional.
- Connection: public endpoint, with the link below as the server URL.
- Authentication: OAuth.
- Read the warning, select I understand and want to continue, then Create as a plugin.
https://app.gobuildwp.com/mcpChatGPT lists the tools it found (sites_list, run and the rest). Install the plugin.
Sign in and allow access
When you install the plugin, ChatGPT opens your Cloud address to sign in.
What you'll see on your Cloud address
- If you're signed out: the GoBuildWP Cloud sign-in page. Sign in with your Cloud email and password.
- A page titled ChatGPT wants to use your WordPress sites (the app may show its own name here).
- Which sites? Pick All my sites, including ones I connect later, or Only the sites I pick and tick them.
- Read only for this app: tick it if this app should only look things up. You can start read-only and reconnect later to allow changes.
- Click Allow. You're sent back to the app.
Only continue if you started this yourself a moment ago. If the page names an app you don't recognise, click Deny.
Use GoBuildWP in a chat
Start a new conversation, type @ in the message box and select GoBuildWP.
ChatGPT asks you to confirm before any tool that can change a site. Read what it is about to do, then confirm.
Test it
Ask ChatGPT one of the three test prompts, starting with “List my WordPress sites”.
Not confirmed in the vendor's docs: OpenAI's help center was unreachable when we checked, so which plans may add a custom MCP server is not confirmed. Older accounts may still show this under Settings → Apps with Developer mode. Sources: OpenAI: connect from ChatGPT; OpenAI: custom MCP servers.
Connect Claude Code
Add GoBuildWP with one command
Paste this into your terminal (any folder):
claude mcp add --transport http gobuildwp https://app.gobuildwp.com/mcpThis adds GoBuildWP for the current project only. Add --scope user after add to use it in every project. Check it any time with claude mcp list.
Sign in and allow access
Start claude, type /mcp, choose gobuildwp, then Authenticate. Your browser opens on your Cloud address.
What you'll see on your Cloud address
- If you're signed out: the GoBuildWP Cloud sign-in page. Sign in with your Cloud email and password.
- A page titled Claude Code wants to use your WordPress sites (the app may show its own name here).
- Which sites? Pick All my sites, including ones I connect later, or Only the sites I pick and tick them.
- Read only for this app: tick it if this app should only look things up. You can start read-only and reconnect later to allow changes.
- Click Allow. You're sent back to the app.
Only continue if you started this yourself a moment ago. If the page names an app you don't recognise, click Deny.
Check it in Claude Code
Back in the terminal, Claude Code confirms the sign-in. Run /mcp again: gobuildwp shows as connected with its tools.
There is nothing to switch on: just ask. Claude Code asks before it runs each GoBuildWP tool the first time; answer Yes, or Yes, and don't ask again for tools you trust.
Test it
Ask Claude Code one of the three test prompts, starting with “List my WordPress sites”.
Use a personal access token instead
Create a personal token on this page (Personal access tokens), set it as GOBUILDWP_TOKEN in your shell, then run:
claude mcp add --transport http gobuildwp https://app.gobuildwp.com/mcp --header "Authorization: Bearer $GOBUILDWP_TOKEN"Connect Cursor
Add GoBuildWP to Cursor
Click the button. Cursor opens and asks you to install gobuildwp; confirm it.
On the Connect AI page in GoBuildWP Cloud this step is a one-click Add to Cursor button.
Or paste this into ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):
{ "mcpServers": { "gobuildwp": { "url": "https://app.gobuildwp.com/mcp" } } }Sign in and allow access
Open Customize in Cursor's sidebar, where MCP servers are listed. Next to gobuildwp, start the sign-in (Cursor may start it for you). Your browser opens on your Cloud address.
What you'll see on your Cloud address
- If you're signed out: the GoBuildWP Cloud sign-in page. Sign in with your Cloud email and password.
- A page titled Cursor wants to use your WordPress sites (the app may show its own name here).
- Which sites? Pick All my sites, including ones I connect later, or Only the sites I pick and tick them.
- Read only for this app: tick it if this app should only look things up. You can start read-only and reconnect later to allow changes.
- Click Allow. You're sent back to the app.
Only continue if you started this yourself a moment ago. If the page names an app you don't recognise, click Deny.
Use it in chat
In Customize, check that gobuildwp is switched on and its tools are listed under Available Tools.
Open the chat (Ctrl+I, or Cmd+I on a Mac) and ask. Cursor uses GoBuildWP's tools when they fit, and by default asks for your approval before each one.
Older Cursor versions list MCP servers under Cursor Settings → Tools & MCP.
Test it
Ask Cursor one of the three test prompts, starting with “List my WordPress sites”.
Use a personal access token instead
Set GOBUILDWP_TOKEN in your environment and use this mcp.json instead:
{
"mcpServers": {
"gobuildwp": {
"url": "https://app.gobuildwp.com/mcp",
"headers": {
"Authorization": "Bearer ${env:GOBUILDWP_TOKEN}"
}
}
}
}Not confirmed in the vendor's docs: The label of the sign-in button next to a custom server is not in Cursor's docs. Sources: Cursor docs: Model Context Protocol; Cursor docs: MCP install links.
Connect VS Code
Before you start. Needs GitHub Copilot. On Copilot Business or Enterprise, your organisation must allow the MCP servers in Copilot policy.
Add GoBuildWP to VS Code
Open the Command Palette (Ctrl+Shift+P, or Cmd+Shift+P on a Mac), run MCP: Add Server, choose HTTP, paste the link and name it gobuildwp.
https://app.gobuildwp.com/mcpWhen VS Code asks where to save it, choose .mcp.json (this project) or Copilot Global (every project, in ~/.copilot/mcp-config.json). Written by hand, the entry looks like this:
{ "mcpServers": { "gobuildwp": { "type": "http", "url": "https://app.gobuildwp.com/mcp" } } }VS Code also reads .vscode/mcp.json, which uses a top-level servers key instead of mcpServers. Its documentation now lists that location as deprecated, so use it only if your VS Code does not offer .mcp.json.
Sign in and allow access
VS Code asks you to trust the server, then asks to sign in to your Cloud address. Allow both; your browser opens.
What you'll see on your Cloud address
- If you're signed out: the GoBuildWP Cloud sign-in page. Sign in with your Cloud email and password.
- A page titled VS Code wants to use your WordPress sites (the app may show its own name here).
- Which sites? Pick All my sites, including ones I connect later, or Only the sites I pick and tick them.
- Read only for this app: tick it if this app should only look things up. You can start read-only and reconnect later to allow changes.
- Click Allow. You're sent back to the app.
Only continue if you started this yourself a moment ago. If the page names an app you don't recognise, click Deny.
Turn it on in Copilot Chat
Open the Chat view (Ctrl+Alt+I, or Ctrl+Cmd+I on a Mac).
Click the Configure Tools button in the chat input and make sure gobuildwp is ticked.
Copilot asks before it runs each tool; click Allow.
Test it
Ask VS Code one of the three test prompts, starting with “List my WordPress sites”.
Use a personal access token instead
Put the token in your user-level ~/.copilot/mcp-config.json, never in a project's .mcp.json that may be committed:
{
"mcpServers": {
"gobuildwp": {
"type": "http",
"url": "https://app.gobuildwp.com/mcp",
"headers": {
"Authorization": "Bearer <your token>"
}
}
}
}Not confirmed in the vendor's docs: VS Code's docs don't show the wording of its sign-in prompt. Sources: VS Code docs: add and manage MCP servers; VS Code docs: MCP configuration reference; GitHub docs: MCP servers in Copilot CLI (mcp-config.json); GitHub docs: MCP allowlist for enterprises.
Connect Codex
Add GoBuildWP and sign in
Run both commands in a terminal. The first adds GoBuildWP to ~/.codex/config.toml; the second opens your browser to sign in.
codex mcp add gobuildwp --url https://app.gobuildwp.com/mcp codex mcp login gobuildwpSign in and allow access
codex mcp login gobuildwp opens your Cloud address in your browser.
What you'll see on your Cloud address
- If you're signed out: the GoBuildWP Cloud sign-in page. Sign in with your Cloud email and password.
- A page titled Codex wants to use your WordPress sites (the app may show its own name here).
- Which sites? Pick All my sites, including ones I connect later, or Only the sites I pick and tick them.
- Read only for this app: tick it if this app should only look things up. You can start read-only and reconnect later to allow changes.
- Click Allow. You're sent back to the app.
Only continue if you started this yourself a moment ago. If the page names an app you don't recognise, click Deny.
Use it in Codex
Start codex and type /mcp: gobuildwp is listed with its tools. Then just ask.
The CLI, the IDE extension and the Codex app share the same config, so this works in all three.
Test it
Ask Codex one of the three test prompts, starting with “List my WordPress sites”.
Use a personal access token instead
Set GOBUILDWP_TOKEN in your environment and add this to ~/.codex/config.toml:
[mcp_servers.gobuildwp]
url = "https://app.gobuildwp.com/mcp"
bearer_token_env_var = "GOBUILDWP_TOKEN"Source: OpenAI Codex docs: MCP.
Connect Devin Desktop
Add GoBuildWP to Cascade
In the Cascade panel, click the … (Actions) menu at the top right, then the Open MCP config file icon in the MCPs section. Add the gobuildwp entry under mcpServers and save:
{ "mcpServers": { "gobuildwp": { "serverUrl": "https://app.gobuildwp.com/mcp" } } }The file is %APPDATA%\devin\mcp_config.json on Windows and ~/.config/devin/mcp_config.json on macOS and Linux. Older Windsurf builds: ~/.codeium/windsurf/mcp_config.json.
Sign in and allow access
When Cascade loads the server it opens your browser on your Cloud address.
What you'll see on your Cloud address
- If you're signed out: the GoBuildWP Cloud sign-in page. Sign in with your Cloud email and password.
- A page titled Devin Desktop wants to use your WordPress sites (the app may show its own name here).
- Which sites? Pick All my sites, including ones I connect later, or Only the sites I pick and tick them.
- Read only for this app: tick it if this app should only look things up. You can start read-only and reconnect later to allow changes.
- Click Allow. You're sent back to the app.
Only continue if you started this yourself a moment ago. If the page names an app you don't recognise, click Deny.
Use it in Cascade
gobuildwp now shows in the MCPs section with its tool count. Make sure the toggle next to it is on, then ask Cascade in a new conversation.
On Enterprise, MCP must be turned on in settings; on Teams, an admin allowlist can block servers that aren't on it.
Test it
Ask Devin Desktop one of the three test prompts, starting with “List my WordPress sites”.
Use a personal access token instead
Set GOBUILDWP_TOKEN in your environment and use:
{
"mcpServers": {
"gobuildwp": {
"serverUrl": "https://app.gobuildwp.com/mcp",
"headers": {
"Authorization": "Bearer ${env:GOBUILDWP_TOKEN}"
}
}
}
}Not confirmed in the vendor's docs: The docs say OAuth is supported but don't show the sign-in steps. Source: Devin Desktop (formerly Windsurf) docs: Cascade MCP.
Other MCP apps
Any app that can add a remote MCP server over Streamable HTTP can use GoBuildWP Cloud. If it supports OAuth sign-in, the link is all it needs and the same Allow screen appears. If it can only send headers, create a personal access token in Cloud and send it as Authorization: Bearer followed by the token.
Antigravity
Agent panel → … → MCP Servers → Manage → View raw config (~/.gemini/config/mcp_config.json).
Add the server, then Customizations → Authenticate; sign in and paste the code back if asked.
{
"mcpServers": {
"gobuildwp": {
"serverUrl": "https://app.gobuildwp.com/mcp"
}
}
}Antigravity needs the key serverUrl, not url.
Gemini CLI
Run the command; Gemini CLI signs in on first use (or run /mcp auth gobuildwp).
gemini mcp add --transport http gobuildwp https://app.gobuildwp.com/mcpIn settings.json use httpUrl; url there means the older SSE transport.
Zed
Add to your Zed settings.json. Zed signs in with OAuth when no Authorization header is set.
{
"context_servers": {
"gobuildwp": {
"url": "https://app.gobuildwp.com/mcp"
}
}
}Kiro
Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in a project). Kiro signs in automatically.
{
"mcpServers": {
"gobuildwp": {
"url": "https://app.gobuildwp.com/mcp"
}
}
}JetBrains (Junie)
Add to ~/.junie/mcp/mcp.json (Windows: %USERPROFILE%\.junie\mcp\mcp.json), then click Authorize in the MCP panel.
{
"mcpServers": {
"gobuildwp": {
"url": "https://app.gobuildwp.com/mcp"
}
}
}Cline
MCP Servers → Remote Servers → Edit configuration, add the server. This setup uses a personal token from Cloud.
{
"mcpServers": {
"gobuildwp": {
"type": "streamableHttp",
"url": "https://app.gobuildwp.com/mcp",
"headers": {
"Authorization": "Bearer <your token>"
}
}
}
}LM Studio
Click Add to LM Studio and confirm in the app.
LM Studio signs in to GoBuildWP when it first uses the tools, or add a personal token as a header.
{
"mcpServers": {
"gobuildwp": {
"url": "https://app.gobuildwp.com/mcp",
"headers": {
"Authorization": "Bearer <your token>"
}
}
}
}Goose
Click Add to Goose and confirm in the app. Goose opens your browser to sign in.
Test the connection
Ask these in a new chat, with one of your own site names in place of [your site]. While the Connect AI page is open in Cloud, its status box changes to “Connected, last used just now by” your app as soon as the first call arrives, and names the tool that ran.
- “List my WordPress sites”. Reads the sites this Cloud connection may reach. A successful list verifies that gateway read; inspect one permitted site's tools and run an authorized read there to verify the site path.
- “Which plugins need updates on [your site]?”. Reads one site's plugins and their available updates. Changes nothing.
- “List the 5 most recent posts on [your site]”. Reads the site's latest posts. Changes nothing.
All three work on any site running GoBuildWP Free, with no other plugin, and none of them changes anything. With GoBuildWP Pro on a site you can also try “Back up [your site]”: it starts a backup with its backup plugin (UpdraftPlus, BackWPup or All-in-One WP Migration). Needs a connection that isn't read-only; the site may ask you to confirm first.
Troubleshooting
The sign-in keeps looping back, or the browser never returns to the app
- Sign in to your Cloud address in the same browser first, then start the connection again from the app.
- Allow pop-ups and third-party redirects for your Cloud address; strict tracker blocking can stop the return trip.
- If you closed the tab before clicking Allow, remove GoBuildWP from the app and add it again: the old attempt has expired.
- Confirm your Cloud email address. Until it is confirmed the Allow button stays disabled.
The app says "needs authentication", "Authorization required" or 401
- The app added GoBuildWP but never finished signing in. Click Connect (Claude, Cursor), Authenticate in /mcp (Claude Code), or run codex mcp login gobuildwp.
- If it worked before, inspect the actual error, expiry or revocation, endpoint and header handling. Re-authorize after identifying the failed authentication step; a 401 alone does not prove someone revoked the connection.
The app is connected but no GoBuildWP tools appear
- Switch the connector on for this chat: Claude's + menu → Connectors; ChatGPT: install the custom MCP plugin, then select it with @ in a new chat; Copilot's Configure Tools; Cursor's Tools & MCP switch.
- Start a new chat or restart the app. Most apps load the tool list once, when the conversation starts.
- Ask in Agent mode (Cursor, VS Code): plain Ask or Edit modes don't call tools.
The AI says the site is read-only, or a change was refused
- The site was connected to Cloud with Read Only access. That is the most Cloud may ever do there. To allow changes, reconnect the site from wp-admin (GoBuildWP → Connect → GoBuildWP Cloud) and choose Production Safe.
- Or this app's connection is read-only: you ticked Read only for this app when you allowed it. Revoke it under Connected apps and sign in again without that box ticked.
- The site's own safety profile can still refuse or ask for a confirmation. That is the site protecting itself, not an error.
"List my WordPress sites" returns nothing, or a site is missing
- Connect the site first: install GoBuildWP on it, then in wp-admin open GoBuildWP → Connect → GoBuildWP Cloud. It then appears on the Sites page.
- When you allowed the app you may have picked Only the sites I pick. Revoke it and sign in again to choose more sites.
- Sites marked Unreachable, Needs reconnect or Over plan limit on the Sites page can't be used until that is fixed.
A personal token stopped working
- Tokens can expire. Check its date under Your tokens; create a new one and replace it where you pasted the old one.
- A revoked token stops at once. Revoking a token cannot be undone.
- Send it exactly as Authorization: Bearer wppat_…, with no quotes or extra spaces.
It works at home but not on a work network
- Company proxies and firewalls can block your Cloud address. Ask IT to allow the scheme, host and port in your Cloud MCP URL, including streaming responses.
- Business and Enterprise AI plans often need an admin to allow custom connectors or MCP servers first (Claude Team/Enterprise owners, ChatGPT workspace admins, GitHub's MCP servers in Copilot policy).
Questions this guide answers
Which link do I paste into my AI app?
https://app.gobuildwp.com/mcp. It is the same for every app and every account; the sign-in decides whose sites the app sees.
The app is connected but says it cannot see my WordPress sites. What now?
Switch the GoBuildWP connector on in the chat you are using and start a new conversation, since most apps load their tool list when a conversation begins. In Cursor and VS Code, ask in Agent mode. If it still lists nothing, check that you picked at least one site on the Allow screen.
Can the AI change my sites after I connect it?
Only within what each site allowed when it connected to Cloud, and never on a connection you marked read-only. Each call still runs on the site under its safety profile and confirmations, and changes are recorded in the site's change ledger.
Review noteRequirements and credential methods follow the shipped GoBuildWP source (WordPress 6.9+, PHP 8.0+). Client menus, account plans and third-party behaviour can change; use the installed version and live schema. Our evidence standard.