by Jordan Hlebarov 0 (0 reviews)

HLB Ability Registry for MCP

Name: HLB Ability Registry for MCP
Author: Jordan Hlebarov

An admin-curated ability registry for the WordPress Abilities API, with a per-ability on/off switch and optional multisite network control.

HLB Ability Registry for MCP ranks #57,584 among WordPress.org plugins with 0+ active installations, is #598 of 628 in the Multisite category, and was last updated Aug 21, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.1

v1.6.4 Current Version v1.6.4

Updated 1 month ago Last Update on 21 Aug, 2026

Refreshed 11 hours ago Last Refreshed on

#598 of 628 in Multisite

View on WordPress.org

Rank

#57,584

— No change

Active Installs

-100%

KW Avg Position

139.5

2.5 worse

Downloads

720

+12 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 30%

0+ 10+

25,917

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 7 more installs to reach 10+

Rank Changes

Current #57,584

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.6.4
Last Updated: Aug 21, 2026
Requires WP: 6.9+
Tested Up To: 7.1.1
PHP Version: 7.4 or higher
Author: Jordan Hlebarov

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

abilities-api AI mcp multisite rest-api

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,758

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

30K+ installs

#1,008

UpdraftPlus: WP Backup & Migration Plugin

3M+ installs

#15

WPCode - Insert Headers and Footers + Custom Code Snippets - WordPress Code Manager

3M+ installs

#19

All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights)

2M+ installs

#21

MonsterInsights - Google Analytics Dashboard for WordPress (Website Stats Made Easy)

MainWP Child - Securely Connects to the MainWP Dashboard to Manage Multiple Sites

700K+ installs

#86

BackWPup – WordPress Backup & Restore Plugin

400K+ installs

#134

LightStart - Maintenance Mode, Coming Soon and Landing Page Builder

400K+ installs

#136

View all Multisite plugins

Frequently Asked Questions

Common questions about HLB Ability Registry for MCP

No. Abilities register with WordPress core's Abilities API regardless, and are reachable via /wp-json/wp-abilities/v1/. The MCP Adapter is only needed if you want the dedicated MCP protocol endpoint. This plugin never downloads or installs the MCP Adapter automatically — it only detects whether it's present and links to its GitHub releases page if not.

Read-only abilities (listing/getting posts, media, comments, taxonomies, templates, site info) default on. Anything that writes or deletes data defaults off until a site administrator turns it on explicitly.

Yes — open it in WordPress Playground: https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/jdbg/hlb-ability-registry-mcp/main/blueprints/demo.json

Yes. Per-subsite settings are always intersected with the currently-available ability registry, so a stale or renamed id can never be registered. In network mode, every permission and capability check still runs inside the target subsite's own context via switch_to_blog(), so a non-member is denied exactly as if they'd called the API on that subsite directly.