mpesa-mcp Just Joined the awesome-mcp-servers Directory
Last week, awesome-mcp-servers merged PR #7395. mpesa-mcp is now listed alongside servers from Stripe, GitHub, PostgreSQL, and hundreds of other production tools.
For context: this repository is the canonical registry of quality MCP servers. Getting merged means the server was reviewed for documentation quality, tool definition clarity, and overall production-readiness.
What it took
The original submission was straightforward. What made it complex was the rebase. The upstream main branch had moved while the PR was open, creating what the GitHub UI labeled as a merge conflict.
The fix wasn't a normal git rebase — it required using the GitHub API directly to rewrite the commit parent to match the current upstream HEAD. The exact commit ancestry had to be verified, not assumed.
That's a disproportionate amount of engineering for what amounts to adding three lines to a markdown file. But it's also a useful reminder: getting into the right directories matters, and the friction is worth it.
The Glama badge
mpesa-mcp has been indexed on Glama with A/A/A scores (license, quality, maintenance). The has-glama label was one of the conditions for the awesome-mcp-servers entry.
Both directories serve different purposes:
- awesome-mcp-servers: curated community list, discoverable via GitHub
- Glama: structured scoring, Docker-based testing, API-queryable metadata
The practical effect: when someone searches for "Africa" or "fintech" in either directory, mpesa-mcp now appears.
Downloads
mpesa-mcp crossed 200 PyPI downloads since v0.2.0 launched. Not viral, but organic — people finding it through the directories and testing it.
The goal was always proof of concept over download count. The downloads are evidence that the infrastructure narrative is legible to an audience beyond the people who already know why it matters.
Top comments (0)