=== AbiliZen - AI Abilities Manager for WordPress MCP ===
Contributors: gowebsmarty
Tags: mcp,ai,claude,abilities,mcp-server
Requires at least: 6.9
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 1.0.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Connect Claude, ChatGPT & any MCP client to your WordPress & Fully control which WordPress Abilities are exposed to AI assistants, with comprehensive logging.

== Description ==

AbiliZen gives you a simple dashboard to control which WordPress Abilities are available to AI assistants.

WordPress 6.9 introduced the Abilities API, letting core and plugins register discrete, schema-described capabilities (an "ability" — read a post, create a page, get site info, and so on). The MCP Adapter exposes
those abilities to AI clients over the Model Context Protocol (MCP). AbiliZen sits on top of both:

* **Abilities tab** — every ability currently registered on the site is read live via `wp_get_abilities()` and shown in one dashboard, grouped by category, with a toggle to enable or disable each one. Nothing is
  hard-coded: whatever core or your other active plugins register shows up automatically.
* **AI Connection tab** — a step-by-step walkthrough for connecting an MCP client (Claude Desktop, Claude Code, Cursor, VS Code, or any other MCP-compatible assistant) to this site, including live status checks and
  ready-to-copy configuration snippets.
* **Logging tab** — every call an AI assistant makes to the MCP endpoint is recorded: who made it, which ability it targeted, and whether it succeeded.

= Authentication =

AbiliZen only supports [WordPress Application Passwords](https://make.wordpress.org/core/2020/11/05/application-passwords-integration-guide/) for authenticating MCP clients. There is no separate API key, token, or OAuth flow to configure or trust — an AI assistant connects as a real
WordPress user over HTTPS and is limited to exactly what that user's role and capabilities allow, the same as any other Application Password integration.

= Requirements =

* WordPress 6.9+ (ships the Abilities API in core)
* The [MCP Adapter](https://github.com/WordPress/mcp-adapter) plugin, active
* Application Passwords available on the site (on by default over HTTPS)

== Installation ==

1. Upload the `aizen` folder to `/wp-content/plugins/`, or install the zip via Plugins → Add New → Upload Plugin.
2. Activate AbiliZen.
3. Install and activate the [MCP Adapter](https://github.com/WordPress/mcp-adapter) plugin.
4. Go to **AbiliZen → AI Connection** and follow the setup steps.

== Frequently Asked Questions ==

= Does this plugin register its own abilities? =

No. AbiliZen don't define abilities of its own — it only reads whatever is already registered via `wp_get_abilities()` and lets you toggle each one.

= Does disabling an ability here only affect MCP? =

No. Disabling an ability unregisters it from the WordPress Abilities API registry entirely (`wp_unregister_ability()`), so it disappears from MCP,
the REST abilities endpoint, and any other code that queries the registry — exactly as if it had never been registered.

= Can AbiliZen make a private ability public over MCP? =

No. AbiliZen can only remove abilities that are already public; it cannot grant MCP visibility to an ability its own plugin did not opt in.

= Does this plugin work without the MCP Adapter plugin? =

You can manage abilities without it, but nothing will be reachable by an AI assistant until the MCP Adapter plugin is installed and active — it is what actually speaks the Model Context Protocol.

== Changelog ==

= 1.0.0 =
* Initial release.
