Registries are searchable catalogs of MCP servers that theDocumentation 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.
find (and search) command queries when you look up a server by keyword. Each registry exposes an HTTP endpoint that add-mcp calls at search time, and the results from all enabled registries are merged, deduplicated, and ranked before being presented to you. add-mcp ships with two built-in registries and also lets you plug in any number of custom ones.
How the find command uses registries
When you runnpx add-mcp find <keyword>, add-mcp sends a GET request to every enabled registry URL with your keyword as the search query parameter. Results across all registries are merged and deduplicated by name@version. The combined list is then ranked—exact name matches score highest, followed by title and description matches—and presented as an interactive selection list.
search is an alias for find and behaves identically.One-time registry setup
The very first time you runfind or search, add-mcp prompts you to choose which built-in registries to enable. Your selection is written to ~/.config/add-mcp/config.json (or $XDG_CONFIG_HOME/add-mcp/config.json if that environment variable is set) and reused on every subsequent search—no prompt is shown again.
If you run
find with -y before completing this one-time setup, the CLI exits early with a message asking you to re-run without --yes so the registry selection prompt can proceed.Config file format
Registry selections are stored under thefindRegistries key:
findRegistries key from the file (or delete the file entirely). The next find run will prompt you to choose again.
Built-in registries
add-mcp curated registry
URL:
https://mcp.agent-tooling.dev/api/v1/serversA hand-curated list of first-party, verified MCP servers from popular developer tools and SaaS services. Designed to surface high-quality, officially maintained servers rather than a long tail of unmaintained or third-party entries. This registry is backed by registry.json in the add-mcp GitHub repository.Official Anthropic registry
URL:
https://registry.modelcontextprotocol.io/v0.1/serversThe community-driven MCP server registry maintained by Anthropic. Contains the broadest catalog of MCP servers across the ecosystem, including community-contributed and third-party servers.Transport selection from find results
Transport forfind/search results is inferred automatically from the registry metadata—you do not need to pass --transport.
- HTTP preferred: when a server advertises a
streamable-httpremote, add-mcp selects it by default. - SSE fallback: if only an SSE remote is available, add-mcp falls back to SSE transport automatically.
- Both remote and stdio available: in interactive mode you are asked to choose between the remote URL and the local stdio package (remote is the suggested default). With
-y, the remote option is always selected automatically.
Example servers in the curated registry
The add-mcp curated registry covers a wide range of developer tools and SaaS platforms. Here is a sample of what is available:Airtable
Manage bases, tables, and records via the official Airtable remote MCP server.
AWS Knowledge
Real-time access to AWS documentation, API references, and best practices.
Apify
Extract data from social media, search engines, maps, and any website.
GitHub
Official GitHub MCP server for repos, issues, PRs, and workflows.
Neon
Manage Neon projects and Postgres databases via the official remote server.
Figma
Access design files, components, and design context from Figma.
Stripe
Official Stripe MCP server for Stripe API tools and payment operations.
Supabase
Interact with the Supabase platform for database and auth management.
Cloudflare
Cloudflare MCP servers for Workers, D1, R2, and more.