How to list your MCP server and get it discovered

To list your MCP server, publish it to the official MCP Registry with a server.json file and the mcp-publisher tool. Then add it to Smithery, Glama, mcp.so and PulseMCP. If your server is remote, also submit it to Claude's connector directory and the ChatGPT Plugin Directory.

Each directory has its own users, and the official registry feeds others, such as GitHub's MCP Registry. Once you are listed, your server name and tool descriptions determine whether an AI agent picks your server. Listed everywhere? Get your MCP server used, not just listed.

Where can you list an MCP server?#

See how many MCP servers there are today, and why the counts differ.

How to publish your MCP server to the official registry#

From namespace to live listing in five steps.

1. Pick your namespace. Use io.github.<your-username>/<server-name> if you sign in with GitHub, or your own domain in reverse order, such as com.example/server, if you prove it with DNS.
2. Write server.json. Add the name, a description of up to 100 characters, a version, and either a package or a remote URL.
3. Publish the package or host the server. Push the package to npm, PyPI, NuGet or a container registry (OCI). For a remote server, host it on HTTPS.
4. Log in. Run mcp-publisher login github (or the DNS option for a domain).
5. Publish. Run mcp-publisher publish. Your server shows up in the registry API within minutes.

{
  "name": "io.github.example/weather",
  "description": "Get forecasts and weather alerts for any US city",
  "version": "1.0.0",
  "packages": [{ "registryType": "npm", "identifier": "@example/weather-mcp", "version": "1.0.0" }]
}

How to list your MCP server on Smithery, Glama, mcp.so and PulseMCP#

Smithery#

1. Sign in with GitHub.
2. Add your server from its repo or remote URL.
3. Fill the name, description and tools, then publish.

Glama#

1. Make sure your repo is public on GitHub.
2. Submit the repo URL, or check if Glama has already indexed it.
3. Claim the listing to edit the details.

mcp.so#

1. Open the submit page.
2. Paste the repo or server URL and a short description.

PulseMCP#

1. Open the submit form.
2. Add the repo or server URL and a short description. PulseMCP also reads the official registry.

How to get your MCP server into Claude and ChatGPT#

Claude's connector directory lists remote MCP servers that pass Anthropic's review. You submit from your Claude organization settings with a name, tagline, description, categories, auth details and test credentials. Read how to submit a Claude connector.

ChatGPT lists MCP servers as plugins. You upload a plugin ZIP on the OpenAI Platform, fix the automated checks and submit for review. Read how to submit an app to ChatGPT.

How to get your MCP server discovered#

What helps agents pick your server.

• A clear server name. Say what it does in the name, like "weather" or "invoices", not a brand word only.
• Tool names with domain and action. Use names like calendar.create_event so the model knows each tool's job.
• Descriptions that start "Use this when...". Say when to use the tool and when not to.
• A README with examples. Show real prompts and real outputs.
• Track where you rank. Check your position in each directory's search and how often agents pick you.
• The right categories and tags. Pick the categories and tags people filter by in each directory, so your server shows up in browse lists too.

Listed everywhere? Get your MCP server used. gaintage tracks your rank in each registry, your share of results against competitors and the prompts that surface your server. Find competitors fast: search the MCP server registry by name or tag.

How do I host my own MCP server?#

You can run it locally over stdio, or host it as a remote server over HTTPS. A remote server can be listed in Claude and ChatGPT. A local server is installed from a package such as npm or PyPI.

Where can I deploy an MCP server?#

Any host that runs a web server works, such as Cloudflare Workers, Vercel, AWS, Google Cloud Run or Fly.io.

MCP server listing checklist#

1. Namespace chosen and verified.
2. server.json valid, with a description under 100 characters.
3. Package published or remote URL live on HTTPS.
4. Published to the official MCP Registry.
5. Listed on Smithery, Glama, mcp.so and PulseMCP.
6. Tool names use domain and action; descriptions start with "Use this when...".
7. README with 3 or more real prompt examples.
8. Remote? Submitted to Claude and ChatGPT.