How do I list my MCP server on MCP Server Finder and other MCP directories?

[bhagyakanwar1]

Pre-submission Checklist

• I have checked that this question would not be more appropriate as an issue in a specific repository
• I have searched existing discussions and documentation for answers

Question Category

• Protocol Specification
• SDK Usage
• Server Implementation
• General Implementation
• Documentation
• Other

Your Question

Hi MCP community,

I am looking to list our company’s MCP server (Exasol MCP Server) both on some official/community MCP server directories.
Here’s the repository for reference: https://github.com/exasol/mcp-server

My questions are:
Where exactly should I submit my server for best visibility/discovery?

Is there a standard process or template to request listing? For MCP Server Finder, it opens an email to info@mcpserver.com
but doesn’t give details, what should my email contain? Should I provide metadata/config, or just a description and links?

Thanks for your help and advice!

[isheng-eqi]

Here is a comprehensive list of MCP server directories and how to submit to each one.

Major MCP directories

1. MCP Server Finder (mcpserverfinder.com)

The largest community-maintained directory.

How to submit:

• Email info@mcpserver.com with the following:
  • Server name
  • One-line description
  • GitHub repository URL
  • Category tags (e.g., database, productivity, developer-tools)
  • Logo URL (optional, PNG/SVG)

Recommended email template:

Subject: MCP Server Listing Request: Exasol MCP Server

Server Name: Exasol MCP Server
Description: MCP server for Exasol database — query execution, schema introspection, and database management
Repository: https://github.com/exasol/mcp-server
Category: database, analytics
Logo: https://raw.githubusercontent.com/exasol/mcp-server/main/logo.png

2. MCP Registry (modelcontextprotocol.io)

The official MCP registry. This is the most authoritative listing.

How to submit:

• Follow the process at: https://github.com/modelcontextprotocol/modelcontextprotocol
• Check the servers/ directory for the submission format
• Generally requires a PR to the registry
• Your server needs to meet quality standards (documentation, tests, active maintenance)

3. Smithery (smithery.ai)

A managed MCP hosting and discovery platform.

How to submit:

• Visit https://smithery.ai
• Connect your GitHub repository
• Their system auto-discovers your MCP server configuration
• Provides hosting, analytics, and a listing page

4. MCP.so (mcp.so)

A community-curated MCP server directory.

How to submit:

• Visit https://mcp.so
• Usually has a "Submit" button or GitHub-based submission
• Requires server name, description, repo link, and tags

5. PulseMCP (pulsemcp.com)

Another community directory with search and categorization.

How to submit:

• Check https://pulsemcp.com for submission guidelines
• Typically GitHub-based or form submission

6. GitHub Awesome Lists

Several "awesome-mcp" lists that get significant traffic:

• awesome-mcp-servers: https://github.com/punkpeye/awesome-mcp-servers

  • Submit via PR — add your server to the appropriate category section in README.md
  • Format: - [Server Name](repo-url) — Short description

• awesome-mcp: https://github.com/appcypher/awesome-mcp

  • Same PR-based submission

7. MCP Marketplace (Claude / Anthropic)

The in-product marketplace accessible from Claude Desktop.

How to submit:

• This is gated — Anthropic curates which servers appear
• Your server should be well-documented, reliable, and follow MCP best practices
• No formal public submission process yet (as of mid-2026)

Prioritized submission order

For maximum visibility with Exasol MCP Server, I recommend this order:

1. MCP Server Finder — email today, quickest turnaround
2. Awesome MCP lists — submit PRs, get indexed by search engines
3. Smithery — get hosted and discoverable
4. MCP.so / PulseMCP — broader community reach
5. Official MCP Registry — highest authority but longest process

Pro tips

• Ensure your README has clear installation instructions and a claude_desktop_config.json example
• Add an MCP badge to your README: [![MCP Server](https://img.shields.io/badge/MCP-Server-blue)](your-url)
• List your server in your GitHub repo's "About" section with relevant topics: mcp, mcp-server, exasol
• A working mcp.json example in your README significantly increases adoption

[SebTardif]

@bhagyakanwar1

Where exactly should I submit my server for best visibility/discovery?
Is there a standard process or template to request listing? For MCP Server Finder, it opens an email to info@mcpserver.com but doesn’t give details

For exasol/mcp-server (PyPI exasol-mcp-server), treat the Official MCP Registry as the source of truth. Several directories now ingest that listing instead of taking a one-off GitHub URL.

1. Official MCP Registry (do this first)

This is not a PR into modelcontextprotocol/servers anymore. Publish metadata to registry.modelcontextprotocol.io with server.json + mcp-publisher.

Docs:

• Quickstart
• Package types

For a GitHub org + PyPI package:

1. Pick a name like io.github.exasol/mcp-server (org Owner must publish).
2. Put a visible mcp-name: io.github.exasol/mcp-server line in the published PyPI README (same version you will declare).
3. Add a root server.json (registryType: pypi, identifier exasol-mcp-server, matching version, stdio transport + the real start args).
4. Keep description at 100 characters or fewer (validate returns 422 otherwise).
5. mcp-publisher validate, then mcp-publisher login github, then mcp-publisher publish.

Same version cannot be republished. Fix copy on the next package version. Verify:

curl -fsSL "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.exasol/mcp-server"

2. PulseMCP

pulsemcp.com/submit does not take a free-form GitHub URL for servers. They ingest the Official Registry (daily crawl, weekly process). After you are on the Registry, wait about a week or email hello@pulsemcp.com with the Registry name, GitHub URL, version, and the same short description.

3. Smithery

Smithery is a separate listing (and optional hosting). For a local/stdio Python server, publish an MCPB (or URL only if you actually host Streamable HTTP). CLI smithery mcp publish on a bundle has been flaky (400 No values to set); REST create + multipart release + PATCH "unlisted": false is the path that works. New listings often start unlisted until that PATCH.

4. Glama

One-time Add Server with the GitHub repo URL (GitHub OAuth). Optional repo-root glama.json with maintainers. No per-release publish token. The listing page can return HTTP 200 before search finds you; wait until https://glama.ai/api/mcp/v1/servers?query=exasol returns a hit.

5. MCP Server Finder email

info@mcpserver.com is still the Finder path. A useful body is:

Subject: MCP Server listing request: Exasol MCP Server

Server name: Exasol MCP Server
One-line description: MCP tools for Exasol metadata and read-only SQL.
Repository: https://github.com/exasol/mcp-server
PyPI: https://pypi.org/project/exasol-mcp-server/
Docs: https://exasol.github.io/mcp-server/main/index.html
Official Registry name: io.github.exasol/mcp-server   (once published)
Categories: database, analytics
Install: pip install exasol-mcp-server

Logo URL only if you have a stable raw image. You do not need to attach full MCP JSON.

6. mcp.so and awesome lists

• mcp.so: the site submit form is paid. The free path is a GitHub issue on chatmcp/mcpso titled Submit: Exasol MCP Server.
• punkpeye/awesome-mcp-servers: PR into the right category; disclose that you maintain the server. Read their CONTRIBUTING first.
• appcypher/awesome-mcp-servers is archived; skip it.

Order that actually compounds

1. Official Registry (server.json + PyPI marker + mcp-publisher)
2. Finder email (their question)
3. Smithery (if you want a Smithery page)
4. Glama Add Server
5. PulseMCP wait/email (after Registry)
6. mcp.so issue + awesome-list PR

Topics you already have (mcp-server, python3) are good. A README install block with a concrete client config example still helps more than extra directory badges.