How to Get Your MCP Server Discovered

You built an MCP server. It works. It solves a real problem. You published it to npm or GitHub.

Now nobody can find it.

This is the most common frustration we hear from MCP server authors. The ecosystem has over 1,400 projects and growing — standing out takes more than good code. Here’s what actually works.

1. Get Listed Everywhere

MCP server discovery is fragmented across multiple registries. You need to be in all of them. Here’s the checklist:

Registry	How to Submit
npm	Publish your package. Add mcp and mcp-server keywords to package.json.
GitHub	Add the mcp-server topic to your repo. This is how most directories find you.
AiList	Submit via the web form or tell your Ai agent: “list my project on AiList.”
Glama	Submit at glama.ai
mcp.so	Submit at mcp.so
MCPServers.org	Submit at mcpservers.org/submit
awesome-mcp-servers	Open a PR on the GitHub repo

Each listing is a backlink and a discovery channel. Don’t skip any of them — it takes 5 minutes each.

2. Write a README That Converts

Your README is your landing page. Most developers decide whether to install in under 30 seconds. Here’s what they need to see:

First 3 lines: What it does, in plain language. Not what it is — what it does for the developer.

— Bad: "An MCP server implementation for PostgreSQL database integration"
— Good: "Query your PostgreSQL database from Claude Code using natural language"

Install command: One line, copy-pasteable. The npx pattern is ideal:

npx your-mcp-server

Configuration example: Show the exact JSON for .mcp.json or claude_desktop_config.json. Developers want to paste and go.

{
  "mcpServers": {
    "your-server": {
      "command": "npx",
      "args": ["-y", "your-mcp-server"],
      "env": {
        "API_KEY": "your-key-here"
      }
    }
  }
}

Tools list: A table or bullet list of every tool the server exposes. Developers scan this to understand scope.

Screenshot or GIF: Show it working. One screenshot of your MCP server being used in Claude Code is worth a thousand words of documentation.

3. Use the Right GitHub Topics

GitHub topics are how automated importers (including AiList’s) discover your project. Add these to your repo:

• mcp-server — The essential one. This is the primary discovery tag.
• mcp — Broader protocol tag.
• model-context-protocol — Full protocol name.
• claude-code — If it works with Claude Code.
• Your domain: database, devtools, automation, etc.

GitHub allows up to 20 topics per repo. Use them.

4. Add an Embeddable Badge

If you’re listed on AiList, you can add a badge to your README that links back to your listing:

[![Listed on AiList](https://hifriendbot.com/ai-list/badge/your-slug.svg)](https://hifriendbot.com/ai-list/your-slug/)

This does two things: it gives your project social proof (“listed on a major directory”) and it creates a discovery loop where developers who find your repo can browse related projects.

5. Let Ai Agents Submit for You

Here’s a trick most people don’t know: AiList has an MCP server. That means you can tell your Ai coding agent:

“List my project on AiList”

The agent reads your repo, fills in the details (name, description, category, GitHub URL), and submits it automatically. No forms, no copy-pasting.

Install the AiList MCP server:

npx ailist-mcp

This works from Claude Code, Cursor, or any MCP-compatible client.

6. Make Your Server Easy to Try

The easier it is to test, the more people will install it. Some tips:

• Zero-config default: If possible, make it work without an API key for basic features.
• npx support: Users should be able to run npx your-server without a global install.
• Clear error messages: When setup fails, tell the user exactly what’s wrong and how to fix it.
• Free tier: If your server requires a key, offer a free tier. The friction of creating an account and paying kills adoption.

7. Package.json Keywords Matter

npm search and registry importers use package.json keywords. Make sure yours include:

"keywords": [
  "mcp",
  "mcp-server",
  "model-context-protocol",
  "claude",
  "claude-code",
  "your-specific-domain"
]

This is often overlooked but directly affects whether automated tools find and index your project.

The Bottom Line

Building the server is half the work. The other half is making it findable. List it everywhere, write a README that sells, use the right tags, and make it trivially easy to install.

The MCP ecosystem is still early enough that a well-positioned server can gain traction quickly. Don’t wait for developers to find you — put your project where they’re already looking.

Submit your project: AiList — Submit Your Ai Project