List sites
See the configured WordPress sites and default site for your workspace.
Direct WordPress mode runs on your site and connects a personal ChatGPT app without a Node server. A hosted customer workspace uses the separate Studio service and its Stripe plans. Hosted purchases do not yet activate paid direct-mode licensing.
Each customer workspace has its own MCP endpoint and OAuth resource URL. Tokens issued for one workspace cannot authorize another workspace. Your configured site list is returned without its application passwords. You connect your own authorized sites in the dashboard. Your signed-in account determines which sites an AI client can access.
The encrypted authorization store preserves clients and refresh-token families across service restarts on the supported persistent storage setup. Access can still be revoked by a customer or operator. A permanent entitlement does not mean an authentication token can never expire.
See the configured WordPress sites and default site for your workspace.
Read authenticated site identity and available REST namespaces.
Inspect supported endpoints and their parameter schemas before using them.
Read installed REST endpoints with the connected user’s WordPress permissions.
Create, update, publish or delete only when write access is enabled and the native endpoint permits it.
View the allowance and requests consumed for your account. All connected workspace sites share that account allowance.
Both the workspace and the WordPress companion can restrict writing. A read-only workspace does not advertise a write tool. The companion independently blocks non-read operations while its read-only setting is active. You must deliberately enable both sides for changes.
Native WordPress REST permission callbacks run for the underlying operation. A subscriber does not gain publishing rights by asking ChatGPT, and a REST controller that denies access remains authoritative. This approach supports clear role selection, but it is not a replacement for backups or review of important changes.
Stripe-hosted Checkout handles the payment interface. The application grants access after processing a verified paid webhook, rather than relying on the success page. Unpaid delayed-payment sessions do not unlock access. Refund or dispute notifications deactivate the affected purchase entitlement.
Daily counting is enforced on the server. OAuth login, connection discovery and MCP tool listing do not consume the daily allowance. An authenticated tool invocation does, including a request that reaches the tool layer and then fails. This rule makes usage visible and predictable.
Third-party ChatGPT availability and usage limits still apply. Plugin-specific tasks require a working WordPress REST endpoint. Hosted customers use the authenticated Studio dashboard to connect and verify sites they are authorized to manage. Site verification is required; Studio does not provide a site builder inside ChatGPT. Some unusual integrations may still require support.
For more detailed configuration and lifecycle behavior, read the security page and setup documentation.
In brief: WPBridge Studio provides WordPress site discovery, authenticated status checks, REST endpoint inspection and permission-controlled content operations. Available operations are determined by the connected site, installed REST routes and the WordPress user.
| Feature | Practical use | Verification |
|---|---|---|
| Site listing | Select an authorized site in a multi-site workspace | Compare the returned site URL and site ID with the intended WordPress property |
| Site status | Identify the connected WordPress installation and REST namespaces | Check the returned site and user identifiers |
| REST route discovery | Determine whether a plugin exposes an API operation | Check the namespace, method and accepted parameters before calling it |
| Content reads | Review existing posts, pages or permitted drafts | Compare real IDs and saved statuses with the WordPress records |
| Content writes | Create or update authorized resources | Use a staging draft and read back the result; never assume the write succeeded |
Hosted Studio workspaces can include multiple verified sites. Select the correct site before each operation; the site’s own REST permissions still apply. See multi-site workflows.
No. WordPress hosting and AI client access remain separate. The hosted plan controls the Studio account’s tool-call allowance, not ChatGPT’s limits.
No. Supported plugin-specific actions require suitable REST endpoints. Use the compatibility checks before assuming access to a feature.
A practical test is more useful than an unqualified feature list. We tested site identity, REST discovery, authenticated reads, draft creation and publication on this authorized installation. The verified WordPress ChatGPT MCP connector demonstration gives the recorded results and distinguishes owner-site evidence from other AI client or customer environments.