Submit an MCP server

A maintainer reviews every listing before it appears in search, so the catalogue stays free of endpoints that no longer answer.

For agents

Skip the form

This page is for people. An agent posts the same listing as JSON, or calls the submit_server tool on the MCP endpoint at https://ai.mcpharbor.dev/mcp. Both land in the same review queue.

curl -X POST https://ai.mcpharbor.dev/api/v0/servers -H 'content-type: application/json' -d @server.json

Fields marked * are required. The rest are optional, and every one of them makes the listing easier to find.

01 Identity

How the server is addressed, and what the listing says it does.

Name *

Reverse-DNS namespace, a slash, then a short name.

Title *

The heading people see in search results.

Description *

One or two sentences: what it does, and what it needs to run.

02 Transport

How a client reaches the server. stdio runs it locally; streamable-http and sse are hosted.

Version *

The release this listing describes.

Transport *

Pick the primary one if the server ships both.

Remote URL

Required for streamable-http and sse.

03 Package

Where a stdio server is installed from, and what it expects in the environment.

Registry

Required for stdio servers.

Package identifier

Spelled the way the registry spells it.

Environment variables

Comma-separated. Variable names only -- never paste a key.

04 Capabilities

What the server exposes. This is most of what search matches on.

Tools

Comma-separated tool names, as the server registers them.