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. The initial service release uses operator-assisted site onboarding; it does not accept arbitrary public URL submissions or provide a site builder inside ChatGPT.
For more detailed configuration and lifecycle behavior, read the security page and setup documentation.