MCP Server & AI Policy Enforcement Changelog

v . 1 . 2 . 2
New

Added a “My AI Access” member view so any logged-in user can see the tools available to their role, with an admin/member view switcher for administrators.
Added a Settings link to the plugin’s row on the Plugins page.

Improvement

NHI Registry is now role-based: grant abilities to each WordPress role, with live capability-conflict detection. A request receives the abilities its user’s role(s) are granted across all enabled NHIs.
Rebuilt NHI create/edit as full-screen pages (guided create wizard ending in a connection step); removed the cramped modal editor.
Existing NHIs are migrated automatically and keep working; review each one to scope its abilities per role.
Support and deactivation-feedback emails now include the customer’s email address in the subject line.

v . 1 . 2 . 1
New

Added a floating Contact Support button, available throughout the admin app.
Added a Setup Guide link in the toolbar for quick access to the connection guide.

Improvement

Redesigned the deactivation feedback prompt with a clearer, on-brand layout, guided reason selection, and the option to get help instead of deactivating.

v . 1 . 2 . 0
New

Added NHI Registry: a new admin screen to view and manage all non-human identity (AI client) registrations, including OAuth client details and token status.
Added per-ability toggle to enable or disable individual abilities from being exposed as MCP tools.

Improvement

v . 1 . 1 . 1
New

v . 1 . 1 . 0
New

Added a remote MCP server endpoint that exposes registered abilities as MCP tools.
Added a self-hosted OAuth 2.1 authorization server with Dynamic Client Registration, PKCE, and discovery metadata so ChatGPT and Claude can connect.

v . 1 . 0 . 0
New

Initial release: read-only viewer for abilities registered through the WordPress Abilities API.

Secure MCP Server for WordPress
Release Notes