Our MCP plugins have grown up a bit. That is good news. It is also how things quietly become harder to explain. 😅
When there is one plugin, life is simple. When there is a core plugin, a stack of add-ons, a GitHub page, a website page, and a few setup steps in the right order, suddenly “just install it” stops being very helpful.
So this round of work was not really about polishing for the sake of polishing. It was about making the ecosystem easier to understand for normal people.
The problem was not the plugins
The plugins themselves were fine. The confusing part was everything around them.
- How many add-ons are there, actually?
- Which ones do you need?
- What should you install first?
- Which page has the current information?
- Why does one page sound newer than another?
That kind of friction is small, but it adds up fast. People do not want to solve a puzzle before they even get to the useful part.
What we changed
- We cleaned up the plugin pages on Devenia so they stop contradicting each other.
- We fixed stale counts, stale links, and stale release references.
- We rewrote the MCP Expose Abilities page in proper Gutenberg blocks so it will be easier to keep updated.
- We improved the GitHub README so the setup path is more obvious.
- We made the “start here” path much clearer: core first, then only the add-ons you actually need.
That may sound like housekeeping, but it changes the feeling of the whole ecosystem. Instead of “here is a pile of powerful stuff, good luck,” it starts to feel more like “here is the shortest path to getting something useful working.”
The real goal: less guessing
We want people to spend less time wondering which plugin does what, and more time actually using them.
If somebody lands on the page and can quickly figure out:
- what the core plugin does
- what is optional
- what order to install things in
- whether the ecosystem is maintained
then we have done our job properly.
Why this matters even if you are not technical
Because “user friendly” is not just about pretty buttons. It is also about whether something makes sense the first time you meet it.
Good tools can still feel unfriendly if the surrounding docs are messy, the pages drift out of date, or the setup path is harder than it needs to be.
That is the part we are trying to improve now.
What comes next
Probably more of this, honestly.
Not because we enjoy moving commas around on plugin pages, but because a friendly ecosystem is built from lots of small choices:
- clearer onboarding
- better install order
- fewer outdated details
- less “which of these do I need?” energy
The goal is simple: make the powerful stuff feel easier to approach.
If you want to see the result, start here: MCP Expose Abilities.
Still nerdy. Just less needlessly confusing. 🤖