Plenty of tutorials show you how to connect Claude to a WordPress site. That's the easy version. The real question — the one an agency actually has to answer — is: how do you connect Claude to fifteen client sites without ever handing over the keys to the kingdom?
Here's the setup we use, and why every choice is a security choice first.
The three ways to connect Claude to WordPress
- WordPress.com Connector (read-only). OAuth, zero setup, great for analytics and audits. Read-only means it can look but never touch — perfect for a first, safe pass on a client site.
- Official WordPress MCP adapter (read-write). For self-hosted sites on WP 6.7+. Claude can actually execute — create posts, update pages — over the Model Context Protocol. Powerful, and exactly why it needs guardrails.
- Managed multi-site MCP. For running many client sites from one place: a dashboard enables the MCP server per site and hands you scoped tokens.
The 4th column nobody writes about: an agency running many sites
Every guide stops at "here's how to connect one." When you manage a fleet, the rules change:
- Never expose superadmin credentials. Ever. Each site gets its own scoped access, and no tool ever sees a master password.
- Application Passwords, scoped per site. WordPress Application Passwords let you grant a narrow, revocable credential per connection — so a token for Client A can never touch Client B, and you can kill it in one click.
- Least privilege by role. The connection gets exactly the capabilities it needs and nothing more. An editor token can't install plugins.
- Staging first. Read-write MCP work happens on staging, gets reviewed, then promotes to production — never straight to a live client site.
- Expiring tokens + an audit trail. Access has a shelf life, and every change is traceable.
Why this is the whole point
This security posture isn't overhead — it's the product. When we tell a Hampton Roads business we can bring AI into their site, "we can do it without ever putting your site at risk" is the part that earns trust. It's also the part that keeps us compliant: scoped data access, no credential leakage, a clear record of who changed what — the same discipline behind our custom builds.
AI in WordPress is here. Doing it safely, across a whole book of local clients, is the actual skill — and it's what we do first, here in the 757.
Running WordPress and want AI in it without the risk? Reach out — we'll walk you through exactly how we'd wire it up.
Related: why WordPress 7.0's AI connectors are only the foundation — the workflow layer they're missing.