One security surface, four useful views
The integration groups the documented Wordfence operations around the decisions an operator actually needs to make.
Status and scans
Read overall firewall, scan, issue, and block status; inspect scan progress; and start a new scan when a fresh check is needed.
Traffic and findings
Review recent live-traffic events and list scan issues so a security question has current activity and findings behind it.
IP controls
List blocked IPs and their reasons, block an IP temporarily or permanently, remove a block, or add an IP to the allowlist.
Login lockouts
List IPs locked out after failed logins and remove a lockout when that narrower recovery action is appropriate.
A controlled operating sequence
The sequence belongs to the operator; the integration supplies the individual Wordfence operations and their structured results.
01
Establish access
Confirm the existing Wordfence plugin is present and the authenticated MCP connection can reach the WordPress site.
02
Inspect first
Read status, scan progress, traffic, issues, blocks, and lockouts before choosing a response.
03
Apply the narrow action
Start a scan, change an IP control, allowlist an address, or unlock a login only when the evidence supports that specific change.
04
Check the result
Read the affected status or list again so the next decision reflects the updated WordPress state.
What must already be in place
This integration works with the security system already installed on the WordPress site.
Required
Wordfence pluginThe existing Wordfence plugin supplies the security status, scan state, traffic, findings, blocks, lockouts, and allowlisting controls exposed through this focused authenticated surface.
Prepare to inspect and act with context
Review the official Wordfence documentation to confirm the plugin’s setup and security features. Then connect the authenticated MCP surface when you need to inspect the current state and make a specific WordPress security change.