WordPress ChatGPT MCP Connector Demo: Verified Tool Calls

What was actually tested on WPBridge Studio?

Direct answer: on October 10, 2026, an authenticated WordPress connector used through ChatGPT identified the correct WPBridge Studio site, read the connected WordPress user, discovered installed REST routes and read the published WordPress product page. This demonstration page was then created through WordPress REST, read back, and published with an additional saved-status check.

Test scope: the site is owned and administered by WPBridge Studio. The calls used the owner’s authorized Website Admin connector. This is not a customer case study, a simulated screenshot, an independent penetration test, or proof of a live Claude/Gemini client trial.

Reproduce the first three checks without editing your website

1. Connect your own authorized WordPress site using the hosted installation guide or direct on-site instructions. Use the correct MCP endpoint for the path selected.
2. Start with read-only access. In a compatible ChatGPT client, ask the connected tool to list the available sites and return the intended URL or site ID.
3. Call the site’s status endpoint. Verify the returned URL and available WordPress REST namespaces, not merely a green connected indicator.
4. Read /wp/v2/users/me and one known published page. Compare the returned WordPress user and page ID with the installation you authorized.
5. Stop if a URL, site identity, permission result, or returned content does not match the intended site. Do not proceed to publishing until the mismatch is resolved.

Example read-only request: “Use WPBridge Studio to identify the connected WordPress site, report site_status, read /wp/v2/users/me and verify the title and status of one known page. Give the actual tool results. Do not publish, update or delete anything.”

How the draft-save and publish test differs from a mockup

A content mutation is confirmed only after WordPress returns a record and a later authenticated read shows the expected saved state. A convincing chat message or preview of proposed HTML is insufficient. For this page, the owner-authorized workflow created the draft, read its WordPress record, requested publication, and read it back again.

For a first test on another site, use a disposable draft in a staging environment. Do not use a real checkout page, membership setting or user list to test writes. Preserve existing scripts, forms and layout when editing complex pages.

The WordPress REST API is the data source for this demonstration. For official platform documentation, read WordPress REST Pages and REST authentication.

Rechecked technical evidence: WordPress REST and tool access

Verification date: October 10, 2026. The Website Admin connection was inspected again from ChatGPT, separately from the original demonstration. These values describe the authenticated owner-controlled WPBridge Studio installation, not a benchmark of unrelated customer websites.

Important distinction: The 216 route patterns are the WordPress REST catalog detected on this site; they include core and third-party namespaces and are not 216 standalone ChatGPT tools. The available connection tools expose specific status, route-discovery, read and permitted write operations. Permissions remain enforced by WordPress and the connector.

Example ChatGPT prompts and what a successful result looks like

First prompt: confirm site identity without editing

Use WPBridge Studio to call list_sites and site_status.
Identify the intended site by its returned URL.
Do not create, update, publish, or delete anything.

Expected evidence: a returned site identifier and URL matching the WordPress site you selected. A connected badge alone is not enough.

Second prompt: prove that WordPress reads work

On the identified site, read /wp/v2/users/me
and a known published WordPress page.
Report the HTTP status and the returned page ID.
Do not make changes.

Expected evidence: authenticated REST responses from the intended site. A valid read does not establish that the same user may edit or publish.

Third prompt: test saving with explicit approval

Only after I approve writes on a staging site,
create a disposable WordPress draft.
Read the saved draft back using its returned ID.
Report both the save and read-back statuses.
Do not publish the draft.

Expected evidence: a created draft ID and a later WordPress response confirming draft status. This is a suggested customer test, not a report that the owner performed this exact staging test on another customer site.

See the detailed WordPress AI workflows, hosted connector setup and REST authorization troubleshooting.

What this demonstration does not prove

• It does not demonstrate an independently tested third-party Claude, Gemini or unaffiliated customer ChatGPT setup; those require their own account-level authorization checks.
• It does not show a WordPress theme, plugin settings panel, WooCommerce purchase flow or arbitrary PHP source code being edited. Such tasks need supported and authorized interfaces.
• It does not prove the live frontend matches the saved WordPress HTML. Browser rendering, caching and responsive appearance require their own checks.
• It does not verify the site’s Google ranking, index status, search performance or availability from every country.
• It does not guarantee WordPress actions that the target user, permission callbacks or installed REST routes do not allow.

Evaluate the WordPress ChatGPT connector for your website

The practical differences between an independent WordPress MCP connector and WordPress.com’s native ChatGPT integration include site hosting, tool availability, client eligibility, OAuth setup, access controls and pricing. WordPress.com publishes its own official connection guide; the appropriate solution depends on your website and intended tasks.

Review the WPBridge Studio WordPress ChatGPT MCP connector, the WordPress.com versus self-hosted comparison and connector buyer checklist. If you need a specific REST operation, verify it on staging before purchasing an entitlement.

Check the operations behind this demonstration

For the underlying list_sites, site_status, discover_routes, wordpress_read and wordpress_write behavior, see the WordPress MCP tool reference. Its documented examples are limited to actual REST routes and permission-aware workflows; they do not establish that every hosted, direct or unrelated client uses the same tool signatures.

WordPress MCP connector demo FAQs

Is the read-and-publish sequence a real WordPress operation?

Yes. The recorded results come from an authenticated WPBridge Studio connection to this WordPress installation, with the record checked again after each state change. They are not independently verified customer results.

Can I try a read-only WordPress connection without publishing anything?

Yes. Site status, WordPress identity checks and permitted page reads can be tested separately from editing operations. Keep writing disabled during initial verification.

Can the same connector manage more than one site?

The hosted service exposes a list of authorized sites for the customer’s workspace. The user should select and verify the intended site ID before requesting operations; actual rights remain site-specific.

Does WordPress MCP automatically improve SEO?

No. It supplies controlled tools for reading or updating content. Search performance depends on separate factors such as editorial usefulness, site indexability and page experience.