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 find command (also available as search) lets you discover and install MCP servers from configured registries without needing to know a server’s URL or package name ahead of time. You can search by keyword or browse the full catalog interactively. Results are ranked by relevance and presented in a paginated list.

​
Usage

npx add-mcp find [keyword] [options]
npx add-mcp search [keyword] [options]
Omit keyword to browse the entire catalog. The search subcommand is a full alias for find — both behave identically.

​
Options

​
[keyword]
string
A keyword to filter registry results (e.g. vercel, neon, github). Omit to browse all available servers.
​
-g, --global
flag
Install the found server to the user-level (global) config directory instead of the current project.
​
-a, --agent <agent>
string (repeatable)
Specify one or more agents to install to (e.g. -a cursor -a claude-code). Can be repeated. When omitted, the CLI auto-detects agents or prompts for selection.
​
-n, --name <name>
string
Override the server name. Defaults to the name derived from the selected catalog entry.
​
-y, --yes
flag
Skip all interactive prompts. Auto-selects the top-ranked result, prefers remote over stdio, and inserts placeholder values for any required template variables (e.g. <your-header-value-here>).
​
--all
flag
Install the found server to all 15 supported agents.
​
--gitignore
flag
Append generated project-level config file paths to .gitignore after installation.

​
Registry setup (first run)

The first time you run find or search, the CLI prompts you to select which registries to enable. Your choice is saved to ~/.config/add-mcp/config.json (respecting XDG_CONFIG_HOME) and reused on every future search — you won’t be asked again unless you edit or delete that file.
If you run find with --yes before completing the one-time registry setup, the CLI will exit with a message asking you to rerun without --yes so you can complete configuration.

​
Built-in registries

RegistryURLDescription
add-mcp curated registryhttps://mcp.agent-tooling.dev/api/v1/serversA curated list of first-party, verified MCP servers from popular developer tools and SaaS services
Official Anthropic registryhttps://registry.modelcontextprotocol.io/v0.1/serversThe community-driven MCP registry maintained by Anthropic — the broadest catalog

​
Editing or resetting registry configuration

Registry preferences are stored under the findRegistries key in ~/.config/add-mcp/config.json: 
{
  "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"
    }
  ]
}
To reset and re-trigger the interactive selection prompt, remove the findRegistries key or delete the file entirely.

​
Adding a custom registry

Any server implementing the registry API can be added as a custom entry. Append it to findRegistries in the config file: 
{
  "url": "https://my-registry.example.com/api/v1/servers",
  "label": "My custom registry"
}
The CLI will GET that URL with query parameters search (the lowercased keyword), version=latest, and limit=100, expecting a JSON response in 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"
          }
        ]
      }
    }
  ]
}

​
Transport inference

You do not specify a transport when using find — it is inferred automatically from the registry metadata:
  • The CLI prefers HTTP (streamable HTTP) when available.
  • It falls back to SSE only when HTTP is not available for the selected install context.
  • If you pass -a flags that target agents supporting only SSE, the CLI adjusts the preference accordingly.

​
Remote vs stdio selection

When a registry entry offers both a remote URL and an stdio npm package:
  • Interactive mode — you are prompted to choose (Remote is the default).
  • With --yes — the remote option is auto-selected.

​
Template variable prompting

If the selected server defines URL variables or header inputs with ${VAR}-style placeholders:
  • Interactive mode — required variables must be filled in; optional ones can be skipped with Enter (they are omitted from the config, not written as empty strings).
  • With --yes — placeholder values such as <your-header-value-here> or <your-variable-value-here> are inserted so you can fill them in manually afterwards.

​
Examples

npx add-mcp find vercel
If no results are found in your configured registries, the CLI offers to fall back to other built-in registries you haven’t enabled. This is useful when a server exists in the Anthropic registry but not in the curated list.

Build docs developers (and LLMs) love

Get started for freeTalk to us