<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: pressbridgesupport</title>
    <description>The latest articles on DEV Community by pressbridgesupport (@pressbridgesupport).</description>
    <link>https://dev.to/pressbridgesupport</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4214641%2F67ebd0e2-9bf3-43ed-9cca-8882506c9203.png</url>
      <title>DEV Community: pressbridgesupport</title>
      <link>https://dev.to/pressbridgesupport</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/pressbridgesupport"/>
    <language>en</language>
    <item>
      <title>WordPress MCP servers in 2026: plugin or outside WordPress?</title>
      <dc:creator>pressbridgesupport</dc:creator>
      <pubDate>Thu, 05 Nov 2026 19:39:27 +0000</pubDate>
      <link>https://dev.to/pressbridgesupport/wordpress-mcp-servers-in-2026-plugin-or-outside-wordpress-1b0o</link>
      <guid>https://dev.to/pressbridgesupport/wordpress-mcp-servers-in-2026-plugin-or-outside-wordpress-1b0o</guid>
      <description>&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;Disclosure first: I build one of them, &lt;a href="https://pressbridgesupport.github.io/pressbridge" rel="noopener noreferrer"&gt;PressBridge&lt;/a&gt;. I'll try to be fair, and I'll say where the others are the better pick.&lt;/p&gt;

&lt;h2&gt;
  
  
  Family 1: servers that go through WordPress (plugins and the REST API)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;The official &lt;a href="https://github.com/WordPress/mcp-adapter" rel="noopener noreferrer"&gt;WordPress MCP Adapter&lt;/a&gt;&lt;/strong&gt; 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.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://wordpress.org/plugins/?p=287818" rel="noopener noreferrer"&gt;Cowboy MCP&lt;/a&gt;&lt;/strong&gt; 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.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://instawp.com/wordpress-mcp/" rel="noopener noreferrer"&gt;InstaWP's MCP&lt;/a&gt;&lt;/strong&gt; and &lt;strong&gt;WordPress.com's&lt;/strong&gt; connector are good when your sites already live there.&lt;/p&gt;

&lt;p&gt;Strengths of this family:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Works on shared hosting, no SSH needed&lt;/li&gt;
&lt;li&gt;Deep access to WordPress data (posts, products, settings)&lt;/li&gt;
&lt;li&gt;One click to install&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Family 2: servers that run outside WordPress
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;Strengths:&lt;/p&gt;

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

&lt;p&gt;The trade-off: you need SSH or Docker on the server. Shared hosting without SSH is out.&lt;/p&gt;

&lt;h2&gt;
  
  
  Plain SSH vs a guarded server
&lt;/h2&gt;

&lt;p&gt;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:&lt;/p&gt;

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

&lt;h2&gt;
  
  
  Which one should you pick?
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Your situation&lt;/th&gt;
&lt;th&gt;Good fit&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Content, WooCommerce, page builders on healthy sites, shared hosting&lt;/td&gt;
&lt;td&gt;A plugin (Cowboy MCP, MCP Adapter)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Building your own WordPress tools for AI&lt;/td&gt;
&lt;td&gt;MCP Adapter&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Sites on InstaWP or WordPress.com&lt;/td&gt;
&lt;td&gt;Their own connectors&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Agency fixing and updating many client sites on your own servers, including broken ones&lt;/td&gt;
&lt;td&gt;A server outside WordPress (PressBridge, or careful SSH)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;They also combine well: a plugin for content work, an outside server for maintenance and emergencies.&lt;/p&gt;

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

&lt;p&gt;What are you using on client sites today? I'm curious which trade-offs matter most to you.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Written with help from Claude.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>ai</category>
      <category>mcp</category>
      <category>webdev</category>
    </item>
    <item>
      <title>How to let Claude fix a WordPress white screen (without giving it the server)</title>
      <dc:creator>pressbridgesupport</dc:creator>
      <pubDate>Thu, 05 Nov 2026 08:17:47 +0000</pubDate>
      <link>https://dev.to/pressbridgesupport/how-to-let-claude-fix-a-wordpress-white-screen-without-giving-it-the-server-51go</link>
      <guid>https://dev.to/pressbridgesupport/how-to-let-claude-fix-a-wordpress-white-screen-without-giving-it-the-server-51go</guid>
      <description>&lt;p&gt;"There has been a critical error on this website." Every agency knows the message, and it always shows up at the worst time: right after a plugin update, a theme tweak, or a "small" change in &lt;code&gt;functions.php&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;AI assistants like Claude are now good at reading a PHP stack trace and finding the line that broke. The hard part is giving the AI access to a broken site &lt;strong&gt;without&lt;/strong&gt; giving it the keys to the server.&lt;/p&gt;

&lt;p&gt;Here is the setup I use, and why the place where your AI tool runs matters more than which model you pick.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why a plugin can't fix a white screen
&lt;/h2&gt;

&lt;p&gt;Most WordPress AI connectors (MCP servers) are plugins. They run inside WordPress, which is great for creating posts or managing WooCommerce products.&lt;/p&gt;

&lt;p&gt;But when WordPress dies with a fatal error, every plugin dies with it, including the one your AI uses to talk to the site. The connector is down exactly when you need it.&lt;/p&gt;

&lt;p&gt;To repair a site that won't boot, the AI has to work &lt;strong&gt;from outside WordPress&lt;/strong&gt;: on the files, and through WP-CLI.&lt;/p&gt;

&lt;h2&gt;
  
  
  The safe way: files + WP-CLI, with guardrails
&lt;/h2&gt;

&lt;p&gt;Giving Claude plain SSH works, but it is a bad idea on client sites. One misunderstood instruction and it can run &lt;code&gt;rm -rf&lt;/code&gt;, read &lt;code&gt;wp-config.php&lt;/code&gt; (your database password ends up in a chat log), or "fix" things you never asked it to touch.&lt;/p&gt;

&lt;p&gt;What you want instead is a small set of fixed tools:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Read and search&lt;/strong&gt; theme and plugin files, never secrets (&lt;code&gt;wp-config.php&lt;/code&gt;, &lt;code&gt;.env&lt;/code&gt;, SQL dumps, keys)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Edit with a backup&lt;/strong&gt; of every file, and one-call undo&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A PHP syntax check&lt;/strong&gt; before anything is saved&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;WP-CLI from an allow-list&lt;/strong&gt; (&lt;code&gt;plugin deactivate&lt;/code&gt; yes, &lt;code&gt;eval&lt;/code&gt; and &lt;code&gt;db drop&lt;/code&gt; no)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An audit log&lt;/strong&gt; of every call&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I built &lt;a href="https://pressbridgesupport.github.io/pressbridge" rel="noopener noreferrer"&gt;PressBridge&lt;/a&gt; for this: a self-hosted MCP server that runs next to your sites and gives Claude exactly those tools, nothing else.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fixing a white screen, step by step
&lt;/h2&gt;

&lt;p&gt;With the site connected, this is the whole conversation:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;You:&lt;/strong&gt; acme shows "There has been a critical error". Find out why and fix it.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;In a typical session, Claude then:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Runs &lt;code&gt;check_site_health&lt;/code&gt;: the home page answers HTTP 500, and WP-CLI can't load WordPress. The fatal error points to a file in one plugin, say &lt;code&gt;wp-content/plugins/some-plugin/includes/class-x.php&lt;/code&gt;, line 212.&lt;/li&gt;
&lt;li&gt;Reads that file and the plugin version (&lt;code&gt;wp plugin list&lt;/code&gt;), and sees the plugin was updated an hour ago.&lt;/li&gt;
&lt;li&gt;Deactivates the plugin (&lt;code&gt;wp plugin deactivate some-plugin --skip-plugins&lt;/code&gt;, on the Pro edition). The site is back.&lt;/li&gt;
&lt;li&gt;Tells you what broke, which version, and suggests rolling back or waiting for a fix.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Claude never sees a password, and every step is in the audit log.&lt;/p&gt;

&lt;h2&gt;
  
  
  The part I care about most: it can't make things worse
&lt;/h2&gt;

&lt;p&gt;The scariest moment with an AI on a live site is the fix that breaks something else.&lt;/p&gt;

&lt;p&gt;Since version 1.2, PressBridge checks the site &lt;strong&gt;after every change&lt;/strong&gt; Claude makes. It loads your key pages and boots WordPress through WP-CLI. If the site worked before the change and is broken after it, the change is undone on the spot (file restored, plugin deactivated, previous theme back) and Claude is told what failed.&lt;/p&gt;

&lt;p&gt;I tested this on real WordPress with MariaDB: a change that passes &lt;code&gt;php -l&lt;/code&gt; but crashes at runtime is rolled back automatically, and the site comes back on its own.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;The free edition is read-only and enough to diagnose a white screen:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pip &lt;span class="nb"&gt;install &lt;/span&gt;pressbridge
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Setup takes about ten minutes on a server you already run: &lt;a href="https://github.com/pressbridgesupport/pressbridge#install-5-minutes-nothing-exposed-to-the-internet" rel="noopener noreferrer"&gt;install guide&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The paid editions add editing with backups, the automatic rollback, plugin and theme updates, and a nightly security watch. The Agent plan has a 14-day free trial.&lt;/p&gt;

&lt;p&gt;If you manage client sites and try it, I'd like to hear what breaks. Comments are open.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Written with help from Claude.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>ai</category>
      <category>claude</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Letting Claude maintain WordPress sites without giving it SSH access</title>
      <dc:creator>pressbridgesupport</dc:creator>
      <pubDate>Thu, 29 Oct 2026 07:48:37 +0000</pubDate>
      <link>https://dev.to/pressbridgesupport/letting-claude-maintain-wordpress-sites-without-giving-it-ssh-access-l6</link>
      <guid>https://dev.to/pressbridgesupport/letting-claude-maintain-wordpress-sites-without-giving-it-ssh-access-l6</guid>
      <description>&lt;p&gt;I look after WordPress sites for a living, and lately I've wanted Claude to take over the boring parts: find where a piece of text lives in a theme, fix it, check which plugins need updates, write the monthly care report for the client.&lt;/p&gt;

&lt;p&gt;The two obvious ways to do that both felt wrong:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Give the AI an SSH key.&lt;/strong&gt; It sees everything, including &lt;code&gt;wp-config.php&lt;/code&gt; and the database password, and one bad instruction can wipe a client's site.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Copy and paste files into a chat.&lt;/strong&gt; Safe, but slow, and the AI never sees the whole theme.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So I built something in between: &lt;strong&gt;PressBridge&lt;/strong&gt;, a self-hosted MCP server that sits between Claude and the WordPress site. Claude gets useful tools; the server decides what those tools are allowed to do.&lt;/p&gt;

&lt;h2&gt;
  
  
  The server enforces the rules, not the prompt
&lt;/h2&gt;

&lt;p&gt;A prompt like "never read wp-config.php" is a suggestion. A file that is invisible to the tool is a guarantee. That was the main design rule: every limit is checked by PressBridge before anything runs, so text hidden in a plugin readme or a web page can't talk Claude past it.&lt;/p&gt;

&lt;p&gt;In the free edition, Claude can:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;read, list and search theme and plugin files&lt;/li&gt;
&lt;li&gt;run read-only WP-CLI commands: versions, plugin and theme lists, core checksums, cron, users&lt;/li&gt;
&lt;li&gt;call &lt;code&gt;site_overview&lt;/code&gt; to get the WordPress version and pending updates in one call&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And it can't:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;see &lt;code&gt;wp-config.php&lt;/code&gt;, &lt;code&gt;.env&lt;/code&gt;, SQL dumps, keys or &lt;code&gt;.git&lt;/code&gt;, at any folder depth&lt;/li&gt;
&lt;li&gt;reach anything outside the site folder, symlink tricks included&lt;/li&gt;
&lt;li&gt;open a shell or run arbitrary commands&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It connects over SSH, so nothing is exposed to the internet.&lt;/p&gt;

&lt;h2&gt;
  
  
  A real session
&lt;/h2&gt;

&lt;p&gt;Here's a 70-second recording of a real session on a test site: health overview, creating and editing a file with an automatic backup, a one-call undo, a safe delete and the audit log.&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/3Am6OlLmZ6s" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;The free edition is MIT-licensed on GitHub, for one site, read-only: &lt;a href="https://github.com/pressbridgesupport/pressbridge" rel="noopener noreferrer"&gt;https://github.com/pressbridgesupport/pressbridge&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Install takes about five minutes on any Linux server where you have SSH: a Python venv, WP-CLI, and a small YAML file listing your site. Then add it to Claude Code or Claude Desktop and ask: &lt;em&gt;"Give me a health overview of mysite."&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  If you want Claude to fix things too
&lt;/h2&gt;

&lt;p&gt;I also sell a paid edition, which is how I'm hoping to keep working on this. It adds edits with automatic backups and one-call undo, a PHP syntax check before saving, allow-listed plugin, theme and core updates, unlimited sites, a Docker HTTPS server and a full audit log. There's also a monthly plan with a nightly security check that alerts you to new admin accounts, PHP files in uploads and changed core files. Details: &lt;a href="https://pressbridgesupport.github.io/pressbridge" rel="noopener noreferrer"&gt;https://pressbridgesupport.github.io/pressbridge&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;One honest limit: file backups don't cover database changes such as plugin updates, so keep your normal database backups running.&lt;/p&gt;

&lt;h2&gt;
  
  
  Feedback welcome
&lt;/h2&gt;

&lt;p&gt;I'd really like to hear from people who manage WordPress sites: what would you want blocked, or allowed, before you'd let an AI assistant anywhere near a client site?&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>ai</category>
      <category>mcp</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
