<?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>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>
