Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/neon-solutions/add-mcp/llms.txt

Use this file to discover all available pages before exploring further.

The add-mcp curated registry is a hand-curated list of first-party, officially maintained MCP servers from popular developer tools and SaaS services. When a user runs npx add-mcp find <keyword>, the results include entries from this registry. Contributing your server gets it in front of every developer using add-mcp to discover and install MCP servers.

​
What is the Curated Registry?

The registry is a single JSON file — registry.json — committed to the add-mcp GitHub repository. It is the source of truth for the add-mcp curated registry endpoint, served at: 
https://mcp.agent-tooling.dev/api/v1/servers
Every entry describes one MCP server: its canonical name, title, description, version, and either remote connection details (URL, optional auth headers) or npm package information for stdio servers.
The curated registry accepts first-party, officially maintained MCP servers only — i.e. servers published or endorsed by the tool or service they represent. Community forks and third-party wrappers are better suited to the Official Anthropic registry.

​
Registry Entry Format

​
Remote (HTTP / SSE) server

Use this shape for servers that clients connect to over a URL: 
{
  "server": {
    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
    "name": "com.example/mcp",
    "title": "Example Service",
    "description": "Description of the MCP server.",
    "version": "1.0.0",
    "remotes": [
      {
        "type": "streamable-http",
        "url": "https://mcp.example.com/mcp",
        "headers": [
          {
            "name": "Authorization",
            "description": "Bearer token",
            "isRequired": true,
            "isSecret": true
          }
        ]
      }
    ]
  }
}

​
npm package (stdio) server

Use this shape for servers that run as a local process via npx: 
{
  "server": {
    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
    "name": "com.example/mcp-stdio",
    "title": "Example Stdio Server",
    "description": "Description of the stdio MCP server.",
    "version": "1.0.0",
    "packages": [
      {
        "registryType": "npm",
        "registryBaseUrl": "https://registry.npmjs.org",
        "identifier": "@org/mcp-server",
        "version": "1.0.0",
        "transport": { "type": "stdio" },
        "environmentVariables": [
          {
            "name": "API_KEY",
            "description": "Your API key",
            "isRequired": true,
            "isSecret": true
          }
        ]
      }
    ]
  }
}

​
Server with both remote and package options

Many servers offer both a hosted remote endpoint and an npm package for self-hosted or offline use. You can include both remotes and packages arrays in the same entry. The add-mcp CLI will let the user choose, defaulting to the remote option. 
{
  "server": {
    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
    "name": "com.example/mcp",
    "title": "Example Service",
    "description": "Supports both hosted remote and self-hosted stdio.",
    "version": "2.0.0",
    "remotes": [
      {
        "type": "streamable-http",
        "url": "https://mcp.example.com/mcp"
      }
    ],
    "packages": [
      {
        "registryType": "npm",
        "registryBaseUrl": "https://registry.npmjs.org",
        "identifier": "@example/mcp-server",
        "version": "2.0.0",
        "transport": { "type": "stdio" }
      }
    ]
  }
}

​
Contribution Workflow

1

Fork the repository

Fork neon-solutions/add-mcp on GitHub and clone your fork locally.
git clone https://github.com/<your-username>/add-mcp.git
cd add-mcp
npm install
2

Add your entry to registry.json

Open registry.json at the repository root. It is a JSON array — append your new server object to the end of the array (before the closing ]). Follow one of the formats above depending on whether your server is remote, an npm package, or both.Keep entries sorted alphabetically by server.title to keep the file reviewable.
3

Verify the registry

Run the built-in verification script to check that your entry is valid JSON and conforms to the expected schema:
npm run registry:verify
Fix any reported errors before opening a pull request.
4

Open a pull request

Push your branch to your fork and open a pull request against main in the upstream repository. Include in the PR description:
  • A brief description of the MCP server
  • A link to the server’s documentation or GitHub repository
  • Confirmation that it is an officially maintained, first-party server
The maintainers will review your entry and merge it once approved.

​
Acceptance Criteria

The curated registry is intentionally selective. Before submitting, make sure your server meets all of these criteria:
The server must be published or directly endorsed by the company or project it represents. Community forks, unofficial wrappers, or personal projects will not be accepted into the curated registry.
Remote servers must have a stable, publicly reachable HTTPS endpoint. npm package servers must be published to the public npm registry with a stable version.
The title, description, and version fields must reflect the current state of the server. Inaccurate or placeholder values will be sent back for revision.
The entry must pass npm run registry:verify without errors. Make sure the $schema field points to the correct schema URL.

​
Questions and Issues

If you have questions about whether your server qualifies, or if you’d like to report an outdated entry, open an issue at: 👉 github.com/neon-solutions/add-mcp/issues

Build docs developers (and LLMs) love

Get started for freeTalk to us