WP Agent Bridge
An MCP server embedded within the WordPress plugin architecture that enables Claude to operate on WordPress content securely via the standard MCP protocol. It provides safety mechanisms including token-based permission control, dry-run simulation, diff comparison, and snapshot rollback capabilities.
Timeline (last 90 days)
WP Agent Bridge is an MCP server running inside WordPress that allows Claude to operate WordPress content management functions without directly touching underlying server credentials such as SSH, FTP, or administrator passwords.
The onboarding process for WP Agent Bridge consists of three steps: installing the plugin, generating a token with a defined scope, and pasting two lines of configuration into Claude's MCP configuration file.
WP Agent Bridge uses scoped tokens to limit the range of content Claude can operate on, applying the principle of least privilege.
WP Agent Bridge performs a dry run before executing any write operation, presenting a precise before-and-after diff of the changes.
Actual changes in WP Agent Bridge are only committed after the user returns a one-time confirmation token, employing a human-in-the-loop design.
WP Agent Bridge records a snapshot of every write operation and verifies the result via loopback requests and logs to confirm whether the page is functioning normally after modification.
WP Agent Bridge supports rolling back to a previous state with a single call.
According to official documentation, WP Agent Bridge provides up to 70 abilities covering various WordPress operations, and all abilities are subject to the same set of guardrails (dry run, confirmation token, snapshot, and rollback).
The specific stability of WP Agent Bridge, the coverage scope of its 70 abilities, and the granularity of token permissions are primarily derived from official demonstrations and have not yet been verified in real-world scenarios.
All Facts (8)
WP Agent Bridge is an MCP server running inside WordPress that allows Claude to operate WordPress content management functions without directly touching underlying server credentials such as SSH, FTP, or administrator passwords.
50%UnverifiedThe onboarding process for WP Agent Bridge consists of three steps: installing the plugin, generating a token with a defined scope, and pasting two lines of configuration into Claude's MCP configuration file.
50%UnverifiedWP Agent Bridge uses scoped tokens to limit the range of content Claude can operate on, applying the principle of least privilege.
50%UnverifiedWP Agent Bridge performs a dry run before executing any write operation, presenting a precise before-and-after diff of the changes.
50%UnverifiedActual changes in WP Agent Bridge are only committed after the user returns a one-time confirmation token, employing a human-in-the-loop design.
50%UnverifiedWP Agent Bridge records a snapshot of every write operation and verifies the result via loopback requests and logs to confirm whether the page is functioning normally after modification.
50%UnverifiedWP Agent Bridge supports rolling back to a previous state with a single call.
50%UnverifiedAccording to official documentation, WP Agent Bridge provides up to 70 abilities covering various WordPress operations, and all abilities are subject to the same set of guardrails (dry run, confirmation token, snapshot, and rollback).
50%