Publishing a Server

Publishing a Server

If it is already in the official MCP Registry

You don't need to do anything. MCP Harbor mirrors the official MCP Registry every six hours, so a server published there appears here automatically, and updates — a new version, a new description, a declared icon — follow within six hours. See How Data Is Collected.

Submitting directly

Three ways, all going through the same rules and the same rate limit:

1. The web form at submit an MCP server.
2. The API: POST /api/v0/servers with a server.json body — see REST API.
3. From an agent: the submit_server tool — see Connecting an Agent.

Submissions are pending until a maintainer approves them. get_server (or GET /api/v0/servers/<name>) shows the status meanwhile. Each client may submit 10 per hour, and the review queue holds at most 500 pending listings.

Getting the most from your listing

• Declare an icon in server.json (icons: [{ "src": "https://…", "sizes": ["128x128"] }]). It outranks every other logo source. Use https; plain http is dropped because browsers block it as mixed content.
• Run a remote server that answers tools/list. Its tools, prompts and resources are then read from the server itself and each gets its own page.
• Publish an llms.txt at your site's root and an AGENTS.md at your repository's root. Changes to both appear in your listing's changelog.
• Use a plain name. Names written as strings of search keywords are what the official registry's moderation looks for.