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.

A custom registry is any HTTP endpoint that implements the add-mcp registry API—a simple GET endpoint that accepts a search keyword and returns a list of MCP server descriptors. Once added to your config, a custom registry is searched alongside the built-in registries every time you run find or search, and its results are merged and deduplicated with the rest.

​
Registry API contract

Your endpoint must accept a GET request to its configured URL with the following query parameters:
ParameterValueDescription
searchuser’s keyword (lowercased)The search term entered by the user. Omitted when the user browses without a keyword.
versionlatestFixed string; always latest.
limit100Maximum number of results to return.
The endpoint must respond with Content-Type: application/json and a body matching this shape: 
{
  "servers": [
    {
      "server": {
        "name": "example-server",
        "description": "An example MCP server",
        "version": "1.0.0",
        "remotes": [
          {
            "type": "streamable-http",
            "url": "https://mcp.example.com/mcp"
          }
        ]
      }
    }
  ]
}
Each server object must include at minimum name, description, version, and either a remotes array or a packages array (or both). Entries missing any of these required fields are silently skipped by add-mcp.

​
Supported remote transport types

The type field inside a remotes entry can be:
  • "streamable-http" — Streamable HTTP (preferred)
  • "sse" — Server-Sent Events (legacy, still supported)
add-mcp prefers streamable-http when both types are listed for the same server.

​
How to add a custom registry

1

Locate your config file

Open (or create) ~/.config/add-mcp/config.json. If the XDG_CONFIG_HOME environment variable is set, the file lives at $XDG_CONFIG_HOME/add-mcp/config.json instead.If the file does not exist yet, create it with the following minimal structure:
{
  "version": 1,
  "findRegistries": []
}
2

Append your registry entry

Add a new object to the findRegistries array with a url and an optional human-readable label:
{
  "version": 1,
  "findRegistries": [
    {
      "url": "https://mcp.agent-tooling.dev/api/v1/servers",
      "label": "add-mcp curated registry"
    },
    {
      "url": "https://registry.modelcontextprotocol.io/v0.1/servers",
      "label": "Official Anthropic registry"
    },
    {
      "url": "https://my-registry.example.com/api/v1/servers",
      "label": "My custom registry"
    }
  ]
}
3

Verify by running find

Run a search to confirm add-mcp queries your registry:
npx add-mcp find <keyword>
If your registry is unreachable, add-mcp will print a warning and continue with results from the other registries. No crash occurs.

​
How to edit or remove registries

The findRegistries array is plain JSON—edit it directly in ~/.config/add-mcp/config.json to reorder, update, or remove entries. To remove a registry, delete its object from the array: 
{
  "version": 1,
  "findRegistries": [
    {
      "url": "https://mcp.agent-tooling.dev/api/v1/servers",
      "label": "add-mcp curated registry"
    }
  ]
}
To reorder registries, rearrange the objects in the array. add-mcp queries registries in order and deduplicates results by name@version, so the first registry to return a given server wins. To update a registry URL, change the url field in the relevant entry.

​
Resetting to the built-in selection prompt

To re-trigger the one-time interactive setup prompt (which lets you choose which built-in registries to enable), remove the findRegistries key entirely from the config file: 
{
  "version": 1
}
Alternatively, delete ~/.config/add-mcp/config.json entirely. The next time you run find or search, add-mcp will prompt you to choose registries again from scratch.
Deleting the config file also clears the lastSelectedAgents preference used by other commands. Remove only the findRegistries key if you want to preserve agent selections.

​
Contributing to the add-mcp curated registry

The source of truth for the add-mcp curated registry is registry.json in the GitHub repository. Every entry in that file is served by the curated registry endpoint at https://mcp.agent-tooling.dev/api/v1/servers. If you maintain an MCP server that belongs in the curated list, open a pull request against the repository and add your server entry to registry.json. Curated registry entries follow the same schema as the API response—each entry is a { "server": { ... } } object with name, title, description, version, and either remotes or packages (or both).
Before opening a PR, check that your server is not already present in registry.json. If it is listed but has an outdated version or incorrect metadata, a PR to update the existing entry is equally welcome.

Build docs developers (and LLMs) love

Get started for freeTalk to us