Skip to main content
Glama

PressBridge Free

The WordPress MCP that still works when WordPress doesn't. Let Claude look inside your WordPress site safely: read-only, sandboxed, secrets hidden. Runs outside WordPress, so it works even when the site shows a critical error.

Website · Demo video · Get Pro · User guide · Security

you     On mysite, where is the footer phone number set? And show me the DB password.

claude  search "0744" in wp-content/themes  →  footer.php:41
        read_file wp-config.php             →  refused: blocked by deny rule 'wp-config*'

        The number is in wp-content/themes/mysite/footer.php, line 41.
        I can't read wp-config.php: PressBridge hides it so passwords never reach me.

PressBridge is an MCP server that gives Claude (Claude Code, Claude Desktop, any MCP client) controlled access to a WordPress site. The Free edition is read-only and made for one site: perfect for debugging, audits and "where is this text coming from?".

  • Read, list and search theme and plugin files

  • wp-config.php, .env, SQL dumps, keys and .git are invisible

  • Nothing outside the site folder, symlink tricks included

  • Read-only WP-CLI: versions, plugin and theme lists, checksums, cron, users

  • WooCommerce, read-only: products, stock, prices, coupons, shipping and taxes (set wc_user in the config; orders and customers only if you turn them on)

  • site_overview: version and pending updates in one call

  • check_site_health: is the site up right now? Loads key pages and boots WordPress

  • Includes the wp-care-report and wp-white-screen skills, also as a Claude Code plugin

Install (5 minutes, nothing exposed to the internet)

On the server:

sudo apt install python3-venv php-cli php-mysql
curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
sudo install wp-cli.phar /usr/local/bin/wp
python3 -m venv ~/pressbridge-venv
~/pressbridge-venv/bin/pip install pressbridge
mkdir -p ~/.pressbridge
cat > ~/.pressbridge/config.yaml <<EOF
data_dir: $HOME/.pressbridge/data
sites:
  mysite:
    root: /var/www/mysite/public_html
EOF
~/pressbridge-venv/bin/pressbridge check --config ~/.pressbridge/config.yaml

Run it as the user that owns the site files (or one that can read them).

On your computer, Claude Code:

claude mcp add pressbridge -- ssh you@server \
  /home/you/pressbridge-venv/bin/pressbridge serve --config /home/you/.pressbridge/config.yaml

Claude Desktop (claude_desktop_config.json, Settings → Developer → Edit Config):

{
  "mcpServers": {
    "pressbridge": {
      "command": "ssh",
      "args": ["-o", "BatchMode=yes", "you@server",
               "/home/you/pressbridge-venv/bin/pressbridge", "serve",
               "--config", "/home/you/.pressbridge/config.yaml"]
    }
  }
}

Claude Code plugin: skills and setup help

PressBridge is also a Claude Code plugin with the wp-white-screen skill (finds why a site shows "There has been a critical error" and gives the exact fix), the wp-care-report skill and a /pressbridge-setup command that walks you through the install:

/plugin marketplace add pressbridgesupport/pressbridge
/plugin install pressbridge@pressbridge

The plugin adds the skills; the MCP server itself still runs where the site files are, as above. With uv you can skip the virtualenv and run uvx pressbridge serve --config ~/.pressbridge/config.yaml.

Then ask Claude: "Give me a health overview of mysite" or "Where in the theme is the footer phone number set?"

The full user guide, with every command, config option and tool, is in GUIDE.md (features marked Pro aren't in this edition).

Related MCP server: mcp-wordpress

Want Claude to fix things too?

PressBridge Pro adds editing with automatic backups and one-call undo, a check after every change that rolls it back automatically if it broke the site, PHP syntax checks before saving, plugin/theme/core updates, unlimited sites, a remote HTTPS server with Docker and automatic certificates, the audit log, and skills for safe edits and safe updates.

→ https://pressbridgesupport.github.io/pressbridge

License

MIT. See LICENSE.

Available Tools

9 tools
check_site_healthB
Read-only

Load the site's key pages and boot WordPress now: is the site up, any fatal errors?

Inputs: site.

list_dirA
Read-only

List a folder inside a site. depth 1-4. Blocked files are hidden.

Inputs: path, site, depth.

list_sitesA
Read-only

List the WordPress sites you can work on, with what each one allows.

Inputs: no named parameters.

read_fileB
Read-only

Read a text file. offset is the first line (1-based), limit the number of lines.

Inputs: path (required), site, limit, offset.

site_overviewB
Read-only

One-call health snapshot: WordPress version, pending updates, plugins and themes.

Inputs: site.

statB
Read-only

Size, permissions and modified time of a file or folder.

Inputs: path (required), site.

wpC

Run an allowed WP-CLI command. args without 'wp', e.g. ["plugin", "list", "--update=available"].

Inputs: args (required), site.

wp_commandsC
Read-only

Show which WP-CLI commands this site allows.

Inputs: site.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools are clearly separable by resource and action: file operations (list_dir, read_file, search, stat), site discovery (list_sites, wp_commands), and execution (wp). The only mild overlap is site_overview versus check_site_health, both framed as 'health' checks, though one is a data snapshot and the other a live boot probe.

    Naming Consistency3/5

    Conventions are mixed: verb_noun (list_sites, list_dir, read_file, check_site_health), bare verbs/abbreviations (search, stat, wp), and noun phrases (wp_commands, site_overview). The wp/wp_commands pairing is internally coherent, but the set overall does not follow one predictable pattern.

    Tool Count5/5

    Nine tools is well within the sweet spot for a WordPress inspection bridge. Each tool covers a distinct capability layer (site enumeration, filesystem, WP-CLI, health) without filler.

    Completeness3/5

    Read/inspect coverage is solid and wp provides a broad escape hatch for deeper WordPress operations. However, the filesystem surface is read-only (list_dir, read_file, search, stat) with no write/edit/delete counterpart, which is a notable gap if agents are expected to modify files.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables full WordPress operator access through Claude Code, including content, media, plugin/theme management, direct theme-file editing, backups, cache purging, and raw REST API calls, all secured with revocable tokens and no SSH requirement.
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants and agents to communicate directly with a WordPress environment, executing PHP code and WP-CLI commands, inspecting and editing theme and plugin files in a sandbox, and managing posts, content, and Gutenberg blocks in real time.
      MIT