MCP plugin update
What We Fixed in Our Free MCP Plugins (February 2026)
A transparent summary of what broke, what triggered fixes, and what we shipped across MCP Expose Abilities and add-ons in February 2026.
What triggered the February cleanup
We made a full cleanup pass across the MCP plugin ecosystem on February 19, 2026 and February 20, 2026.
The work was triggered by real user reports, missing public coverage, confusing release metadata, and documentation that no longer matched the plugin ecosystem.
The cleanup answered three questions
- What broke for plugin users?
- Which releases and docs were fixed?
- Where should users start now?
The work had three practical goals
The cleanup was not a cosmetic release note. It 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. We removed hard plugin header dependency checks from add-ons and kept runtime checks instead.
Make the ecosystem visible
Toolset coverage was missing in several public places, so we created and published mcp-abilities-toolset and added Toolset references to docs and plugin pages.
Fix confusing release signals
The GitHub release badge on mcp-expose-abilities showed release: invalid. We corrected release metadata and badge behavior.
The main problem was trust in the release surface
When activation messages, release badges, repository metadata, and documentation disagree, users cannot tell whether the plugin set is current or safe to install.
The cleanup focused on reducing that ambiguity without hiding the trigger. The public issue, repositories, release tags, and plugin pages remain visible so users can verify the state themselves.
What changed
- Activation blocker removed from affected add-ons.
- Versions bumped, commits pushed, and affected add-on releases published.
- Toolset add-on created, released, and linked from public documentation.
- mcp-expose-abilities release metadata corrected with v3.0.17.
- Release badge URL changed to a semver-sorted Shields URL.
What users should know now
The fixes were shipped so ZIP users and repository visitors see 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 v3.0.17 was published to remove confusion.
- Documentation consistency: README counts and links were updated so public docs better reflect current plugin state.
The most important outcome is simpler verification: current pages, releases, badges, and docs should point users in the same direction.
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
- MCP Expose Abilities on Devenia
- github.com/bjornfix/mcp-expose-abilities
- github.com/bjornfix/mcp-abilities-toolset
What was clarified
- Add-on dependency checks
- Toolset availability
- Release and badge metadata
How to read this update
This is a public 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 GitHub issue, release tag, repository, plugin page, and Toolset repository for primary evidence.
If you reported bugs or confusing behavior: thank you. These fixes were driven by real usage reports, and they made the plugins better for everyone.
Frequently asked questions
What triggered the February 2026 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 was 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 GitHub repository, and the mcp-abilities-toolset repository linked from this article.
Where to go next
If you use the free MCP plugins, start from the current plugin page or repository rather than old ZIPs, stale badges, or copied dependency notes.
- Open the Devenia plugin page.
- Check the current GitHub release.
- Use the Toolset add-on when you need the broader ability set.
- Report any remaining activation or documentation mismatch with the exact plugin, version, and message.
Real usage reports are useful. They make the public release surface clearer for everyone.