MCP maintenance

Make the public plugin surface easier to trust.

This summary explains what broke, what triggered the fixes, and what shipped across MCP Expose Abilities and its add-ons.
Abstract plugin maintenance with connected modules and checkmarks

What triggered the cleanup

Three questions guided the work.

A full maintenance pass covered the MCP plugin ecosystem in February 2026.

Real user reports, missing public coverage, confusing release metadata, and documentation that no longer matched the ecosystem triggered the work.

The maintenance work answered three questions

User impact

What broke for plugin users?

Release and docs

Which releases and docs were fixed?

Next step

Where should users start now?

The practical goals

Fix the activation path, make the ecosystem visible, and correct release signals.

The maintenance work removed activation confusion, made public plugin coverage easier to understand, and corrected release signals.

Remove activation friction

Add-ons were failing activation with Requires: abilities-api even when Abilities API was installed. The fix removed hard plugin-header dependency checks from add-ons while keeping runtime checks.

Make the ecosystem visible

Toolset coverage was missing from public surfaces. The cleanup published mcp-abilities-toolset and added Toolset references to docs and plugin pages.

Fix confusing release signals

The mcp-expose-abilities GitHub release badge showed release: invalid. Release metadata and badge behavior were corrected.

What changed

The release surface now has a cleaner set of signals.

When activation messages, release badges, repository metadata, and documentation disagree, users cannot tell whether the plugin set is current or safe to install.

The maintenance work reduced that ambiguity while keeping the trigger visible so users can verify the state.

Shipped changes

Activation

Activation blockers were removed from affected add-ons.

Release sync

Versions were bumped, commits were pushed, and affected add-on releases were published.

Toolset coverage

The Toolset add-on was created, released, and linked from public documentation.

Release metadata

Main release metadata was corrected to remove confusion.

Release badge

The release badge URL was changed to a semver-sorted Shields URL.

What users should know

Current zip files, releases, badges, and docs should point to the same state.

Current releases now give ZIP users and repository visitors a more consistent plugin ecosystem.

Activation

Hard header dependency checks were removed from add-ons to avoid false negatives from folder or slug mismatches.

Release sync

Versions were bumped, commits were pushed, and releases were published across affected add-ons.

Toolset coverage

Toolset references were added to repository docs, Devenia plugin pages, and repository metadata.

Release metadata

An old draft release was removed and the current release was published to remove confusion.

Documentation consistency

readme counts and links were updated so public docs better reflect current plugin state.

The important outcome is simpler verification: current pages, releases, badges, and docs should point users in the same direction.

The evidence

The fixes came from real usage.

A user report in GitHub issue #2 showed add-ons failing activation even when the required base plugin was installed.

Start here

Use the Devenia MCP Expose Abilities page and the public repositories for mcp-expose-abilities and mcp-abilities-toolset.

What was clarified

Add-on dependency checks, Toolset availability, and release and badge metadata.

How to read this update

Treat this as a maintenance summary, not a marketing claim.

The useful measure is whether the release surfaces now agree.

Activation behavior is less fragile.
ZIP users have current releases.
The Toolset add-on has a public repository and release.
The main release badge no longer reports an invalid release.
Docs and plugin pages point to the same ecosystem pieces.
Check the linked issue, release tag, repositories, and plugin pages for primary evidence.

These changes came from real usage reports and make the plugins easier to verify.

Frequently asked questions

What changed and where to start.

What triggered the cleanup?

A GitHub issue reported add-ons failing activation with Requires: abilities-api even when Abilities API was installed. Missing Toolset coverage and confusing release metadata were also cleaned up.

What changed in the add-ons?

Hard plugin-header dependency checks were removed from add-ons, runtime dependency checks were kept, versions were bumped, and affected add-on releases were published.

Where should users start now?

Start with the Devenia MCP Expose Abilities plugin page, the main repository, and the mcp-abilities-toolset repository linked from this article.

Where to go next

Start from current pages and repositories.

If you use the free MCP plugins, start from the current plugin page or repository rather than old zip files, stale badges, or copied dependency notes.

Open the current Devenia plugin page.
Check the current repository release.
Use the Toolset add-on when you need the broader ability set.
Report a mismatch with the exact plugin, version, and message.

Report any remaining activation or documentation mismatch with the exact plugin, version, and message.