Directories and Social Media
Expand your reach beyond the registry. Submit to popular directories and share with the developer community.
Beyond the Registry
Publishing to the MCP Community Registry is your foundation. Directories and social channels expand your reach to developers who discover servers in other ways.
Multi-channel strategy:
- Registry - Official discovery (publish first)
- Directories - Community-curated lists with high visibility
- Social - Direct engagement with your target audience
Each channel reaches different developers. Maximize discoverability by being present across all of them.
MCP Directories
Community-driven directories aggregate MCP servers in searchable, categorized lists. High traffic, low barrier to entry.
awesome-mcp-servers (78k+ stars)
The most popular MCP server directory on GitHub. Extremely high visibility in the developer community.
How to submit:
- Fork punkpeye/awesome-mcp-servers
- Add your server to the appropriate category in README.md:
- [Your Server Name](https://your-slug.mctx.ai) - Brief description of what it does - Keep alphabetical order within the category
- Submit a pull request
Tips for approval:
- Write a clear, concise description (one sentence)
- Pick the most relevant category (don't force multiple)
- Follow the existing format exactly
- Use your vanity link (
your-slug.mctx.ai) not a GitHub repo link
PRs are typically reviewed within a few days. Once merged, you gain exposure to 78k+ GitHub users following the repo.
MCP Community Marketplace
A community-driven marketplace for discovering MCP servers. Modern UI, searchable by tags and categories.
How to submit:
- Visit mcp.so
- Click Submit (usually in the header or footer)
- Create a GitHub issue with:
- Server name
- Description
- Your vanity link (
your-slug.mctx.ai) - Tags/categories
- Wait for review and inclusion
Submission tips:
- Use the same description as your registry listing (consistency)
- Add tags that match your server's capabilities
- Link to your mctx.ai vanity URL for one-click subscribe
Social Channels
Directories are passive discovery. Social channels let you actively engage with developers who need what you're building.
Twitter/X
The developer community is highly active on Twitter. Announce your server, share use cases, and engage with users.
Announcement template:
Just launched [Server Name] on @mctxai 🚀
[One sentence describing what it does]
✓ Free MCP hosting
✓ One-click subscribe
✓ OAuth built-in
Try it: https://your-slug.mctx.ai
#MCP #AI #LLMOngoing engagement:
- Share interesting use cases or examples
- Quote tweet users who mention MCP
- Reply to questions in the #MCP hashtag
- Show what you're building (behind-the-scenes)
Hashtags to use:
#MCP- Core MCP community#AI,#LLM- Broader AI audience#ClaudeCode,#Cursor- Client-specific- Topic-specific tags for your server's domain (e.g.,
#DevTools,#Finance,#DataScience)
Discord
AI and MCP-focused Discord servers are where developers ask questions, share projects, and discover tools.
Recommended servers:
- MCP Discord - Official MCP community
- AI tool communities (Cursor, Claude, Cline, etc.)
- Topic-specific servers related to your domain
How to share:
- Join the server and observe for a day or two
- Read the rules (many have specific channels for sharing)
- Post in the appropriate channel (usually #showcase or #share)
- Describe the problem your server solves
- Include your vanity link
Do:
- Be helpful in other threads before promoting
- Answer questions about your server
- Share genuine value, not just self-promotion
Don't:
- Spam multiple channels
- Repost the same message frequently
- Only show up to promote
Relevant subreddits reach developers interested in AI, MCP, and specific domains.
Recommended subreddits:
- r/MachineLearning - Broad AI audience
- r/LocalLLaMA - Self-hosted AI tools
- r/ClaudeAI - Claude-specific community
- Topic-specific subreddits for your server's domain
How to share:
- Read the subreddit rules carefully
- Check if self-promotion is allowed (some require mod approval)
- Post with a descriptive title focused on the value
- Explain the problem and how your server solves it
- Include your vanity link
Example post structure:
Title: Built an MCP server for [specific use case]
Body:
I built [Server Name] to solve [specific problem].
[Brief description of what it does and why it's useful]
You can try it at https://your-slug.mctx.ai
Happy to answer questions or hear feedback!Follow subreddit norms:
- Some prefer Show & Tell posts in megathreads
- Others want detailed technical write-ups
- Engage with comments and answer questions
GitHub README
If your server's source code is public on GitHub, add installation instructions to your README.
Quick Start section example:
## Quick Start
Subscribe at [your-slug.mctx.ai](https://your-slug.mctx.ai), then add to your MCP client:
**Claude Code:**
```bash
claude mcp add your-slug -- npx mcp-remote https://your-slug.mctx.ai/v1.0.0
```
**Cursor:**
```json
{
"mcpServers": {
"your-slug": {
"url": "https://your-slug.mctx.ai/v1.0.0"
}
}
}
```Link to your mctx.ai vanity page for pricing, docs, and subscribe flow.
Developer Blogs and Content
Write about your server to attract developers searching for solutions.
Content ideas:
- Problem + Solution - "How I built an MCP server for [use case]"
- Technical Deep Dive - Architecture, design decisions, trade-offs
- Use Case Walkthroughs - Real examples of your server solving problems
- Integration Guides - How to use your server with specific tools
Where to publish:
- Dev.to - Large developer audience, good SEO
- Medium - Broader audience, paywalled content option
- Your own blog - Full control, builds your brand
SEO tips:
- Use keywords developers search for (e.g., "MCP server for X", "how to build Y")
- Link to your vanity page (
your-slug.mctx.ai) in the article - Share on Twitter, Reddit, and Discord after publishing
Writing Effective Descriptions
Your server description appears in directories, social posts, and your info page. Make it count.
Do:
- Lead with the benefit - "Get real-time weather data for any city"
- Be specific about capabilities - Don't say "data server", say "SEC filings search"
- Keep it under 100 characters for directory listings
- Use active language - "Query", "Analyze", "Convert", "Monitor"
Don't:
- Use generic phrases - "A powerful tool for...", "The best way to..."
- List features without context - Features alone don't communicate value
- Oversell with hype language - Let the capabilities speak for themselves
Examples:
| Good | Bad |
|---|---|
| "Query SEC filings with natural language" | "A server for financial data" |
| "Real-time flight status for any airline" | "Flight information tool" |
| "Convert documents to markdown with OCR" | "Document processing server" |
| "GitHub issue analytics and trends" | "GitHub integration server" |
Timing and Coordination
Launch with momentum by coordinating across channels:
Day 1 (Launch Day):
- Publish to MCP Community Registry
- Tweet your announcement
- Post to Discord servers
- Submit to awesome-mcp-servers
Week 1:
- Submit to MCP.so
- Post to Reddit (follow subreddit rules about timing)
- Publish blog post or demo video
- Update GitHub README
Ongoing:
- Share use cases and examples on Twitter
- Answer questions in Discord/Reddit
- Engage with users who mention your server
- Publish updates when shipping new versions
Track What Works
Monitor where your subscribers come from:
- Check your dashboard for subscriber growth
- Note when spikes occur after promotions
- Double down on channels that drive results
- Experiment with different messaging
You don't need to be everywhere. Focus on 2-3 channels where your target developers hang out.
Next Steps
- Your Vanity Link - Use your mctx.ai link everywhere
- Publish to Registry - Start with official discovery
- Versioning - Keep your server updated
See something wrong? Report it or suggest an improvement — your feedback helps make these docs better.