How I Let Claude Fully Control My WordPress Site

What started as an experiment turned into a production tool I use every day, and eventually a commercial product.

The Problem

If you manage a WordPress site, you know the drill. You want to make a small change, update some copy, tweak a CSS class, add a menu item, and suddenly you’re context-switching between your AI assistant, a browser tab, an SFTP client, and the WordPress admin. You describe what you want to Claude, it gives you code, you copy it, paste it somewhere, and hope nothing breaks.

There’s a better way.

The Idea: Give Claude Direct Access

What if Claude didn’t just tell you what to do, but could do it itself?

That’s the idea behind PressBridge: a WordPress plugin that exposes your entire site through a token-authenticated REST API and a built-in MCP (Model Context Protocol) server. Claude connects to it directly, and can read and manage your site without you acting as the middleman.

Architecture

Here’s how the pieces fit together: Claude.ai connects to PressBridge via HTTPS with token authentication. The plugin exposes a REST API and MCP server at /wp-json/pressbridge/v1/, giving Claude structured access to posts, pages, media, users, options, theme files, database, plugins, and menus, all within WordPress.

How the API Works

PressBridge adds a REST API namespace at:

https://yoursite.com/wp-json/pressbridge/v1/

All requests require authentication via one of three methods:

Authorization: Bearer YOUR_TOKEN
X-PressBridge-Token: YOUR_TOKEN
?token=YOUR_TOKEN

Example: Read a theme file

GET /wp-json/pressbridge/v1/theme/file?path=style.css
Authorization: Bearer YOUR_TOKEN

Example: Create a post

POST /wp-json/pressbridge/v1/posts
Authorization: Bearer YOUR_TOKEN
Content-Type: application/json

{
  "title": "How AI is Changing WordPress",
  "content": "
Article content here...
",
  "status": "draft",
  "type": "post"
}

The MCP Server

The REST API is useful on its own, but the real power comes from the MCP (Model Context Protocol) server built into PressBridge. MCP is an open standard developed by Anthropic that lets AI models connect to external tools and data sources. Claude.ai supports MCP connectors natively. Instead of Claude constructing raw HTTP requests, it gets a structured set of 53 named tools it can call directly, read_theme_file, db_execute, create_post, list_plugins, and so on.

Connecting to Claude.ai

1. Install and activate PressBridge on your WordPress site
2. Go to Settings → PressBridge and copy your Connector URL (token is pre-included)
3. In Claude.ai go to Settings → Integrations → Add custom connector
4. Paste the URL and save

That’s it. Claude now has direct access to your WordPress site.

Real Prompts I Use Every Day

Here are actual prompts from my workflow, no exaggeration, these all work:

Content & SEO

Update the meta title and description for the homepage to target 
the keyword "AI WordPress automation". Keep it under 60 characters 
for the title and 155 for the description.

Add a new blog post draft titled "5 Ways AI Can Save Your 
WordPress Developer Hours Every Week".

Theme & CSS

The logo in the hero section is too large on mobile. Add a CSS 
rule that reduces it to 72px on screens under 768px wide.

Add a sticky "Back to Top" button that appears after the user 
scrolls 300px. Style it to match the site's orange brand color.

Database & Options

Check all published pages and tell me which ones are missing 
Rank Math SEO meta titles and descriptions.

Update the footer copyright year to 2026 across all relevant 
options and theme files.

System & Maintenance

Read the PHP error log and summarize any recurring errors 
from the last 24 hours.

Flush all caches, object cache, transients, and Varnish.

Security Design

Giving an AI direct write access to your WordPress site sounds terrifying. Here’s how PressBridge handles it:

• Token authentication, Every request requires a bearer token verified with PHP’s hash_equals() to prevent timing attacks.
• Options blacklist, WordPress secret keys, auth salts, and the PressBridge token itself are blacklisted from the options API.
• Path traversal prevention, All file paths are validated with PHP’s realpath() before any file operation.
• SQL guardrails, The database execute endpoint blocks DROP and TRUNCATE statements.
• SSRF protection, Media URL upload endpoints reject non-HTTP/HTTPS schemes.
• Tier-gated access, Pro features require a valid license. Free tier limits Claude to posts, pages, media, and basic options.

What It’s Like to Work This Way

Here’s a real example. I had a services page rendering from a PHP template (page-services.php) instead of the WordPress database. Any content change required editing PHP and potentially hitting a WAF restriction.

I asked Claude to:

1. Read the existing PHP template
2. Rewrite all the content as structured HTML
3. Write it into WordPress post_content via a database update
4. Simplify page.php to just call the_content()
5. Delete the now-unnecessary page-services.php

The entire migration took one conversation. The page looks identical on the frontend, but now all content lives in the database, meaning future changes are just natural language prompts.

What This Unlocks

Once your site’s content lives in the database and Claude has API access, a whole class of workflows becomes possible:

• Automated SEO audits, Ask Claude to review every page’s meta, heading structure, and keyword density
• Content pipelines, Generate, review, and publish blog posts through conversation
• Maintenance automation, Weekly cache flushes, error log reviews, plugin audits
• A/B testing copy, Update headlines and CTAs across multiple pages in one prompt
• Localization, Ask Claude to translate post content and write it back as a new draft

Limitations & Honest Caveats

Claude doesn’t have real-time context. It reads what you ask it to read. If you ask it to “fix the header” without specifying a file, it needs to read the file first.

It can make mistakes. Claude can write incorrect SQL or malformed HTML. Always keep backups and test changes on a staging environment for anything critical.

WAF rules on managed hosts (like WP Engine) can block writes to new PHP files. This is actually what pushed me to move all content to the database, the WAF made that the right architectural decision anyway.

Try It

PressBridge is available at strifetech.com/pressbridge. Free tier includes post/page management, media library, and basic options, enough to connect Claude and start exploring. Pro ($5/mo) unlocks theme files, database access, user management, and all 53 tools. Agency ($20/mo) covers unlimited sites.

Wrapping Up

The shift from “ask Claude, copy the answer, paste it somewhere” to “ask Claude, it does the thing” is not incremental, it’s a fundamentally different way of working. PressBridge is what made that possible for WordPress.

If you build something interesting with it, I’d love to hear about it.