GoBuildWP Setup Guide: First Safe WordPress MCP Connection

The GoBuildWP setup guide in wp-admin order

Everything in this first session happens on four GoBuildWP screens, and it helps to know their names before you start, because the menu groups them by the question each one answers. Settings holds the switch that exposes the site to agents at all. Connect a client produces the configuration you paste into your AI client. Diagnostics tests the connection from the server's side. Changes shows what an agent did afterwards. The Dashboard sits on top of all four and summarises them.

Start on Settings. The Agent access section has two controls: AI abilities, a toggle, and Safety profile, a drop-down. With AI abilities off there is no MCP endpoint and no ability exposed, whatever else is configured, and the Dashboard says agents are switched off. Turn it on, set Safety profile to Read Only and select Save settings. Doing this before you generate a configuration means the very first call your client makes already runs under the profile you intend to keep for the test.

Then open Connect a client. It is laid out as three numbered steps. Step 1, Choose your authentication method, offers OAuth, Application password and Access token; pick OAuth if your client supports a browser sign-in, because nothing secret is copied. Step 2, Connect your AI client, is a row of client tabs; choose yours and copy the snippet, command or form values it shows. Step 3, Check it worked, watches for the client's first authenticated request.

• Settings: AI abilities on, Safety profile set to Read Only, settings saved
• Connect a client, Step 1: an authentication method chosen deliberately, not by default
• Connect a client, Step 2: the snippet for your exact client, not a neighbour's
• Connect a client, Step 3: left open in a tab so you can reload it after the client starts

What a successful first connection looks like

Most clients read their server list only when they start, so restart the client after adding GoBuildWP, then ask it to list the site's abilities. Until that first request arrives, Step 3 says no client has connected yet. Reload the page once the client has made a call and it changes to report which clients authenticated and introduced themselves, by the name the client sends. That line is the server-side proof that the endpoint, the credential and the transport all worked, independent of anything the chat window says.

Next, the read itself. Ask for wppilot/list-content with a limit of one, or for wppilot/get-content on a page you created for the test. A good answer names the tool it called and returns an object ID you can find in wp-admin. A vague answer that describes your site without naming a tool usually means the model answered from its own knowledge, or from a web search, instead of calling the server; ask it again to use only this site's connection.

Finally, look at Changes for entries made during this test. A Read Only session should add none; on a site that already has history, older entries are expected and not a sign of trouble. Ordinary reads are not recorded (only a few sensitive reads, such as a raw database query, leave an audit row), so a new entry from this test session means something wrote, which is worth understanding before you go any further. The Dashboard's AI clients list should now show your client with a last-seen time, and its Changes, last 24 hours figure should not have risen during the test.

When the first read does not come back

Resist regenerating the credential. Open Diagnostics, choose how you connect in the How do you connect? list, and select Run diagnostics. It probes the MCP endpoint with and without credentials, checks that the Authorization header reaches PHP, that Application Passwords are accepted, that the OAuth sign-in challenge and metadata are reachable and that the server clock is accurate. If every probe passes, the picker underneath asks what you see in your AI client and narrows the advice to that symptom.

Three outcomes cover most first sessions. A client that connects but lists no GoBuildWP tools is usually pointing at the wrong endpoint, because the OAuth URL and the Application Password URL are different addresses, or has not been restarted since the entry was added. A 401 on the Application Password route usually means the password was revoked, the section is disabled, or a proxy is stripping the header. A read that is refused with a permission error means the connection works and the WordPress user lacks the capability the ability checks; the fix is the user, not the profile. The troubleshooting guide takes each of these further.

Widening access after the first read

Once a read is proven, add authority one step at a time and watch the result of each step on the site rather than in the chat. Switch the Safety profile to Production Safe, ask for a single edit to a draft you made for the purpose, and confirm three things: the draft changed in the editor, a row appeared on Changes naming the ability and your dedicated user, and that row offers an undo. Use it. A write you have already undone once is the cheapest insurance against the first real mistake.

Two decisions are worth making before an agent works on anything that matters. The Confirmation section of Settings decides who confirms destructive or critical calls: Agent flag, where the model sends confirm=true itself, or A person approves, where a person approves the exact call in the client or on a one-time wp-admin link. And the Abilities screen lets you switch off any ability the job will never need. Neither is required for the setup to work; both are easier to set now than after an agent has learned a habit.

Write down what you chose: the user the connection acts as, the profile, the confirmation mode and the client. If something surprises you in a month, those four facts are what anyone helping you will ask for first.

• A draft edited under Production Safe and checked in the editor
• The matching row on Changes, attributed to the dedicated user
• One undo performed and verified
• Confirmation mode chosen on purpose
• Abilities the workflow never uses switched off