Plugin release
Wordfence support in MCP Abilities has a clearer path.
What this release note clarifies
Keep the product path, focus, and security context distinct.
Wordfence focus
The release is about Wordfence-related MCP ability support, not a broad Devenia download directory.
Specific product path
The primary action points to MCP Expose Abilities, the Devenia-owned page that best matches the reader job for this update.
Secondary context
Wordfence remains supporting security context, separate from the Devenia product path.
Using Wordfence through MCP? Leave a comment with the specific action boundary or security check you want documented next.
The product path
Start with MCP Expose Abilities for the maintained Devenia context.
This release note keeps the Wordfence update compact. It gives readers one clear Devenia-owned product path for understanding how MCP abilities are exposed. Wordfence remains supporting security context.
Use MCP Expose Abilities for the maintained Devenia product context. Keep security-plugin context separate when you need to understand the Wordfence side of the update.