---
title: "List your SaaS in the Official MCP Registry"
description: "Publish a live remote MCP server to the Official MCP Registry so agents and directories that query it can discover your product. Install the publisher CLI, authenticate, submit the server entry, then confirm the listing resolves to your endpoint. The real cost is having a working remote server; the submission itself is quick."
url: "https://seo-mcp.io/t/list-your-saas-in-the-official-mcp-registry"
---

# List your SaaS in the Official MCP Registry

Publish a live remote MCP server to the Official MCP Registry so agents and directories that query it can discover your product. Install the publisher CLI, authenticate, submit the server entry, then confirm the listing resolves to your endpoint. The real cost is having a working remote server; the submission itself is quick.

## Prerequisites

- A publicly reachable remote MCP server endpoint
- Homebrew installed on macOS or Linux
- An account for the Official MCP Registry (GitHub authentication is typical)

## Steps

1. **Confirm the remote MCP server responds** — Send an MCP initialize request to your public endpoint and check that it answers with a JSON-RPC result containing serverInfo.
   Check: The curl request returns HTTP 200 and a JSON body with a result.serverInfo object.
2. **Install the publisher CLI** — Install mcp-publisher with Homebrew as described in the tweet.
   Check: `mcp-publisher --help` exits with status 0 and prints the available subcommands.
3. **Authenticate the CLI** *(general best practice)* — General best practice: sign the CLI in to the registry account (typically GitHub-based) before any publish attempt, so the submission is attributed to your organisation.
   Check: The CLI reports a signed-in account or writes a credentials file, and no authentication error is returned.
4. **Publish the server entry** *(general best practice)* — General best practice: run the publish flow from the repository that holds the server manifest, with the name, short description, repository URL and the public remote endpoint filled in.
   Check: The CLI prints a success message naming the published server, with no validation errors.
5. **Check the public listing** *(general best practice)* — Open the registry page for your server and confirm the description, repository link and endpoint are correct and that search on the registry finds it by name.
   Check: The registry page for your server returns HTTP 200, shows your remote endpoint, and the site name is returned in registry search results.

## Source

@tarasshyn on 2026-10-18: https://x.com/tarasshyn/status/2111078201090777406

Canonical: https://seo-mcp.io/t/list-your-saas-in-the-official-mcp-registry