Getting Started

WP Agent Bridge is designed around a simple principle: routine use should stay simple, while advanced development and operational tools remain available when needed.

1. Install and activate

Install the WP Agent Bridge plugin in WordPress and activate it. The plugin creates a dedicated administration area.

2. Choose Basit or Gelişmiş mode

Basit mode focuses on onboarding, Cloud Account, plan status and product readiness. Gelişmiş mode exposes approvals, usage, release readiness, account/fleet, plan catalog and Cloud diagnostics.

3. Connect ChatGPT / MCP

Use Quick Connect to create a connection. The generated MCP endpoint is associated with a revocable connection token. Hosting credentials are not required by Quick Connect.

4. Optional Cloud Account

Cloud Account uses passwordless email verification. Enter your email, request the code, then enter the numeric OTP in WordPress. After successful verification, the site is automatically enrolled into the account's default fleet.

5. OAuth authorization

For OAuth-capable MCP clients, WP Agent Bridge uses the existing Cloud Account identity. A user authenticates with email OTP, reviews the requesting client and scopes, then explicitly approves or denies access. OAuth activation is completed only after the authorization server and resource-server validation are enabled.

6. Safety model

Read-only tools can be executed directly when authorized. Higher-impact operations use explicit safety controls such as dry-run, plan/state hashes, SHA checks, confirmations, snapshots and rollback where supported.

7. Usage synchronization

When Cloud Account is linked, privacy-safe aggregate usage can synchronize automatically. It includes daily counts and normalized route counters only.

8. Plans

The Free plan is active. Pro and Agency structures may be visible for product planning, but paid checkout remains disabled until a payment provider is explicitly activated.

9. Troubleshooting

Check the Product Readiness, Cloud diagnostics and package health screens first. If contacting support, never include OTPs, passwords, access tokens, refresh tokens or service-role keys.

Current package line: 2.31.x. Documentation will evolve with OAuth public release and billing activation.