modelcontextprotocol / modelcontextprotocol/ext-apps
💡 Idea: Growth strategy for MCP extension ecosystem
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 387
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 6
Description
Love the MCP extensions work! Quick thought on ecosystem growth:
For an MCP extensions registry like this, developer discovery is the #1 challenge. We ran growth for AFFiNE from 0 to 33k stars and found these channels work best:
- GitHub README SEO — Repos with titles matching search terms (e.g., "mcp server examples", "mcp integration template") get 200-500 organic views/month
- MCP community posts — Share on dev.to, Hashnode with MCP tags
- Newsletter features — Get listed in MCP-related newsletters
Happy to elaborate on any of these. We documented the full open source growth playbook here: https://github.com/Gingiris/gingiris-opensource
Would love to hear what growth channels you are exploring!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or implementation entry point is identified. Start by reviewing the issue and the linked open-source growth playbook, then check the repository’s existing README and MCP ecosystem materials. Done would require a concrete, maintainer-approved growth task with defined channels and success criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- content, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100