WordPress MCP servers in 2026: plugin or outside WordPress?

If you want Claude (or another AI assistant) to work on WordPress sites, you need an MCP server. There are now a dozen, and they split into two families that behave very differently on a bad day.

Disclosure first: I build one of them, PressBridge. I'll try to be fair, and I'll say where the others are the better pick.

Family 1: servers that go through WordPress (plugins and the REST API)

The official WordPress MCP Adapter turns "abilities" registered in WordPress into MCP tools. It is the long-term standard for WordPress itself, and the right base if you build your own plugin tools.

Cowboy MCP is a free plugin with a very wide tool set (content, media, WooCommerce, page builders, SEO plugins), an undo journal and database checkpoints before updates. If your work is mostly content and store management on healthy sites, it is hard to beat for the price: free.

InstaWP's MCP and WordPress.com's connector are good when your sites already live there.

Strengths of this family:

• Works on shared hosting, no SSH needed
• Deep access to WordPress data (posts, products, settings)
• One click to install

The trade-off: they need WordPress to be running. When a plugin update causes "There has been a critical error", the MCP connection is down too, exactly when you'd want an assistant to look at the logs. And a plugin serving the AI runs with the same access as WordPress itself, database password included.

Family 2: servers that run outside WordPress

These connect to the site's files and WP-CLI from the server, not from inside WordPress. PressBridge is one; plain SSH access for Claude Code is the do-it-yourself version.

Strengths:

• Still works when WordPress doesn't boot, so the AI can fix a white screen
• Secrets like wp-config.php can be blocked at the file level, outside PHP
• One server can manage many client sites, with different rights per site

The trade-off: you need SSH or Docker on the server. Shared hosting without SSH is out.

Plain SSH vs a guarded server

Giving Claude Code an SSH login is the fastest setup and the riskiest one on client sites: any shell command, any file, including secrets. A guarded server gives the AI fixed tools instead. In PressBridge that means:

• Read, search and edit files with an automatic backup and one-call undo
• PHP syntax check before saving
• WP-CLI from an allow-list (no eval, no db drop)
• An audit log of every call
• Since 1.2: after every change the site is loaded again, and the change is rolled back automatically if it broke the site
• Since 1.3: WooCommerce products, prices, stock and coupons through WP-CLI (orders and customers only if you turn them on)

Which one should you pick?

They also combine well: a plugin for content work, an outside server for maintenance and emergencies.

PressBridge has a free read-only edition (pip install pressbridge) and paid editions with editing, updates and a nightly security watch; the Agent plan has a 14-day free trial.

What are you using on client sites today? I'm curious which trade-offs matter most to you.

Written with help from Claude.