Git-native content governance for AI agents — 27 deterministic MCP tools over stdio and HTTP.
Nothing to run from here
PressBridge is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
85/100
trust score
1
downloads a day
local
runs on your machine
98
downloads in 30d
What it does
PressBridge lets Claude (Claude Code, Claude Desktop, any MCP client) look inside a WordPress site safely. It runs outside WordPress, so it still works when the site is broken.
Free edition (this package), read-only, one site:
- Read, list and search theme and plugin files
wp-config.php,.env, SQL dumps, keys and.gitare invisible to the model- Nothing outside the site folder, symlink tricks included
- Read-only WP-CLI: versions, plugins, themes, checksums, cron, users
- WooCommerce read-only: products, stock, prices, coupons, shipping, taxes
site_overviewandcheck_site_health
Install: PressBridge runs where the site files are. Install it on the server (pip install pressbridge), create ~/.pressbridge/config.yaml, then connect Claude over SSH:
claude mcp add pressbridge -- ssh you@server ~/pressbridge-venv/bin/pressbridge serve --config ~/.pressbridge/config.yaml
Full guide: https://github.com/pressbridgesupport/pressbridge
PressBridge Pro adds editing with automatic backups and one-call undo, automatic rollback if a change breaks the site, plugin/theme/core updates, unlimited sites, a remote HTTPS server with Docker, and a nightly security agent: https://pressbridgesupport.github.io/pressbridge
Quickstart
Install it the way its author documents:
1. # On the server (where the site files are):
2. python3 -m venv ~/pressbridge-venv && ~/pressbridge-venv/bin/pip install pressbridge
3. # Create ~/.pressbridge/config.yaml with your site's root folder (see the guide)
4. # On your computer, connect Claude over SSH:
5. claude mcp add pressbridge -- ssh you@server ~/pressbridge-venv/bin/pressbridge serve --config ~/.pressbridge/config.yaml
The full guide: https://github.com/pressbridgesupport/pressbridge#install-5-minutes-nothing-exposed-to-the-internet
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts PressBridge as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Install it the way its author documents:
1. # On the server (where the site files are):
2. python3 -m venv ~/pressbridge-venv && ~/pressbridge-venv/bin/pip install pressbridge
3. # Create ~/.pressbridge/config.yaml with your site's root folder (see the guide)
4. # On your computer, connect Claude over SSH:
5. claude mcp add pressbridge -- ssh you@server ~/pressbridge-venv/bin/pressbridge serve --config ~/.pressbridge/config.yaml
The full guide: https://github.com/pressbridgesupport/pressbridge#install-5-minutes-nothing-exposed-to-the-internet
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List the WordPress sites you can work on, with what each one allows.
Takes no parameters.
List a folder inside a site. depth 1-4. Blocked files are hidden.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | no | — |
| depth | integer | no | — |
| site | string | no | — |
Read a text file. offset is the first line (1-based), limit the number of lines.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | — |
| offset | integer | no | — |
| limit | integer | no | — |
| site | string | no | — |
Regex search across files (like grep). glob filters file names, e.g. '*.php'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pattern | string | yes | — |
| path | string | no | — |
| glob | string | no | — |
| max_results | integer | no | — |
| ignore_case | boolean | no | — |
| site | string | no | — |
Size, permissions and modified time of a file or folder.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | — |
| site | string | no | — |
Show which WP-CLI commands this site allows.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | — |
Run an allowed WP-CLI command. args without 'wp', e.g. ["plugin", "list", "--update=available"].
| Parameter | Type | Required | Notes |
|---|---|---|---|
| args | array | yes | — |
| site | string | no | — |
One-call health snapshot: WordPress version, pending updates, plugins and themes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | — |
Create or overwrite a file. The old version is backed up first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | — |
| content | string | yes | — |
| create_dirs | boolean | no | — |
| site | string | no | — |
Replace exact text in a file. old_text must match once unless replace_all is true.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | — |
| old_text | string | yes | — |
| new_text | string | yes | — |
| replace_all | boolean | no | — |
| site | string | no | — |
Move or rename a file or folder inside the same site.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | yes | — |
| destination | string | yes | — |
| site | string | no | — |
Move a file or folder to the trash outside the webroot (restorable).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | — |
| site | string | no | — |
List backups and trashed items, newest first. Filter by path prefix.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | no | — |
| limit | integer | no | — |
| site | string | no | — |
Put a backed-up or trashed file back. The current version is backed up first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| backup_id | string | yes | — |
| path | string | yes | — |
| site | string | no | — |
Recent PressBridge activity, newest first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
| site | string | no | — |
Security check now: compares the site with the last nightly baseline (new admins, PHP in uploads, changed core files, backdoor-like code, ...). Doesn't save a baseline or send alerts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | — |
The latest nightly security report, as sent to the alert channels.
Takes no parameters.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install PressBridge or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
BTrust score 85 / 100
Release 1.3.0 · scanned 5 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score91
Client score85
Findings5 threat · 5 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest7cba33c34db92191f4ad4d2f5ec75ce254fb70a5388e9f738b450690cb3a306c
Score vectorthreat 91 → client 85
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (18 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
9 of the 18 recovered tools are registered only when EDITION == "free" is false (src/pressbridge/server.py:178) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 9.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
9 tools are registered unconditionally · 9 more only when EDITION == "free" is false (src/pressbridge/server.py:178) — typically when a key or option is configured. All 18 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_sites | no tags | |
| list_dir | no tags | |
| read_file | sensitive-source | sensitive-source: keyword "read_file" |
| search | no tags | |
| stat | no tags | |
| wp_commands | no tags | |
| wp | state-write | state-write: declares readOnlyHint: false |
| site_overview | no tags | |
| check_site_health | no tags | |
| write_file conditional | file-writestate-write | file-write: keyword "write_file" in tool name; state-write: declares readOnlyHint: false |
| edit_file conditional | file-writestate-write | file-write: keyword "edit_file" in tool name; state-write: declares readOnlyHint: false |
| move conditional | state-write | state-write: declares readOnlyHint: false |
| trash conditional | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| list_backups conditional | no tags | |
| restore_backup conditional | state-write | state-write: declares readOnlyHint: false |
| audit_log conditional | no tags | |
| security_scan conditional | no tags | |
| watch_report conditional | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest7cba33c34db92191
Scanned2026-11-05
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.3.0. Pin a release below and the command asks for exactly that one.
1.3.0
5 Nov 2026
latestNo release note was published with this version.
1.1.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish PressBridge can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.