Claude and ChatGPT get full power on WordPress. You hold the switch.
Out of the box, AlphaBridge only reads. An administrator turns on write access with one switch. Every call runs with the rights of a WordPress user. With Pro, a way back is ready for pages and files.
How the dangerous parts are guarded.
Content tools are easy. Files, the database and deployment carry real risk. These three layers guard them.
Encrypted credentials
Deploy passwords are encrypted with libsodium (XSalsa20-Poly1305) before they touch the database. Any change to the stored value is detected. No tool returns them.
Same-server verification
Before a file is pushed, AlphaBridge checks the target with a probe file. It must be the server your site runs on. A redirected or spoofed host fails the check. SFTP host keys are pinned by SHA256 fingerprint.
Your switch, your permissions
Out of the box the plugin only reads. An administrator turns on write access with one switch. Then every tool is on, and with Pro also the abilities of other plugins. Switch off what you do not need. Every call runs with the WordPress rights of its user. It checks them for that very post, file or term. The database tools in Pro read with a single SELECT. They change rows only through structured writes. Each connection keeps its own access level.
Every layer, spelled out.
What the plugin does, layer by layer.
- OAuth 2.1 with PKCE. Claude connects via a login-protected consent screen on your own site — standard discovery, no token copying, no account with us.
- Hashed tokens, scoped and revocable. Tokens are stored only as hashes. They can be limited to read-only or content-only and given an expiry. You can rotate them in one click and revoke them at any time.
- Permission checks per tool and per object. Every call runs as a real WordPress user. It checks the capability for the specific post, file or term it touches, not just a global role.
- Layered secret protection. In the free plugin, options and transients are reachable only through a fixed allowlist of common site settings. The Pro option tools accept other names. They refuse security-relevant ones by blocklist. A blocklist only knows what it knows, so option writes stay an admin-level decision. Meta access is layered. Protected keys, is_protected_meta() keys and compound credential patterns (api_key, access_token, client_secret …) are refused. Generic meta passes WordPress's own per-key capability check. Reading protected "_" keys requires manage_options and an explicit request.
- SQL guard with a positive allowlist. Database tools (Pro) accept only allowed statement types. They block system schemas and dangerous functions. They close comment, CTE and PREPARE bypasses.
- Optional atomic deploy with rollback. With atomic:true (off by default), full-site deploys unpack to a staging folder, check every file and keep a backup. Then they swap by rename. A failed upload before the swap leaves the site as it was. A failed swap rolls back on its own.
- Guards everywhere. Path-traversal guards and SSRF-safe URL fetching with re-validated redirects. A fixed abuse rate limit. And a main switch that keeps the site read only until an administrator switches on write access.
- An audit log. The plugin keeps the latest 200 tool calls, each with its user and result. The settings page shows the newest ones with time, tool and status.
The core is open source.
The free plugin's complete source is public on GitHub and on WordPress.org. It includes the main switch, the permission checks and the log. Pro and Agency build on this core. Their own parts, such as the SQL guard and Site Deploy, are not public.
Built for people who answer for other people's sites.
Client sites need a record of the AI's work. AlphaBridge shows it in the log.
Per-client connections
Give each client its own token: read-only, content-only or full access, with an optional expiry. Rotate or revoke it without touching anything else.
A clear log
The settings page lists the latest tool calls with time and status, allowed or refused. The plugin keeps the latest 200 per site.
Blast-radius control
Nothing writes until an administrator switches on write access. Single tools and groups can be switched off. Search and replace in Pro previews changes by default. Deploys reach only the server your site runs on.
Questions about safety.
Can Claude do more than my WordPress account allows?
No. Every call runs with the rights of the connected WordPress user. What that user may not do, the AI cannot do.
What can the AI do while write access is off?
It only reads: content, media, terms, comments, settings and the structure of the site. Tools that write are refused. So are readers of code, files, the database, logs or credentials.
Can I see what the AI did?
Yes. The plugin keeps the latest 200 tool calls, each with its user and result. The settings page shows the newest ones.
Can I take back a change?
With Pro, yes, for edits to pages and files. Pro keeps an undo point for these edits, by default for 7 days.
One switch, full power. And with Pro, a way back.
Get Pro for $49 a year or $9 a month. Or try it free for 7 days, with no card. The log and the main switch come with every edition, the free plugin included.