We made a full cleanup pass across the MCP plugin ecosystem on February 19, 2026 and February 20, 2026. This post explains what triggered the work and exactly what we changed.
What Triggered This
- A user report in GitHub issue #2 showed add-ons failing activation with:
Requires: abilities-api, even when Abilities API was installed. - Toolset coverage was missing in several public places (repo docs, Devenia plugin page, repo About metadata).
- The GitHub release badge on mcp-expose-abilities showed
release: invalid, which was confusing.
What We Fixed
- Activation blocker removed: We removed hard plugin header dependency checks (
Requires Plugins: abilities-api) from add-ons and kept runtime dependency checks instead. This avoids false negatives from folder/slug mismatches. - Release sync: We bumped versions, pushed commits, and published releases across affected add-ons so ZIP users get the fix immediately.
- Toolset added everywhere: We created and published mcp-abilities-toolset, released
v1.0.1, and added Toolset references to docs and plugin pages. - mcp-expose-abilities release metadata fixed: We published v3.0.17 and removed an old draft release to avoid confusion.
- Badge fix: The release badge now uses a semver-sorted Shields URL, which resolves the previous
release: invaliddisplay. - Docs consistency: We updated counts and links in README content so public docs better reflect current plugin state.
Where to Start
- Main plugin page: MCP Expose Abilities on Devenia
- Main repository: github.com/bjornfix/mcp-expose-abilities
- Toolset add-on: github.com/bjornfix/mcp-abilities-toolset
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.