A side-by-side look at the AllMCPs Server and Brightdata MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AllMCPs Server for aggregators work over a hosted endpoint; choose Brightdata MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AllMCPs Server when
You need dedicated capabilities in the Aggregators domain.
You prefer a remote HTTP/SSE transport.
Its auth model fits you: No auth required.
You have the keys it needs: ALLMCPS_MCP_URL.
You want tools like search_mcp_servers, get_mcp_install_config, recommend_mcp_stack.
search_mcp_serversSearch the AllMCPs directory for Model Context Protocol (MCP) servers by keyword or category.
get_mcp_install_configGet the exact claude_desktop_config.json setup snippet and documentation for a specific MCP server by ID.
recommend_mcp_stackRecommend a curated multi-tool MCP server stack for a specific developer role or workflow (e.g. "fullstack", "data science", "devops").
list_mcp_categoriesList all categories available in the AllMCPs directory along with server counts.
get_boost_pricingGet pricing and features for boosting / featuring an MCP server on AllMCPs.com.
boost_mcp_serverInitiate a sponsorship / boost order for an MCP server by ID, returning a Stripe checkout session URL and x402 invoice.
get_boost_statusCheck current boost status, verified badge level, and sponsorship expiration for an MCP server by ID.
submit_mcp_serverProgrammatically submit a new MCP server repository to AllMCPs.com for indexing and review. Supports the same optional enrichment fields as the human submission form — fill in whichever you can confidently determine from the repository (README, package.json, code) to produce a fully flushed-out listing. Omit anything you are not confident about rather than guessing; all enrichment fields are optional and unrecognized enum values are simply dropped, not rejected.
verify_mcp_claimVerify ownership and claim an MCP server listing by checking GitHub README badge, website badge, or DNS TXT record. Works two ways: (1) fully unattended — pass `agentToken` from confirm_mcp_agent (or set an `Authorization: Bearer <token>` header if your client supports it), no human sign-in needed; or (2) if called with neither, requires the caller to already have an active AllMCPs browser session. Unattended agents should use register_mcp_agent + confirm_mcp_agent first.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
AllMCPs Server is categorized under Aggregators and uses a remote HTTP/SSE transport. Brightdata MCP belongs to Developer Tools and uses a local stdio subprocess. Pick AllMCPs Server for aggregators work and Brightdata MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
AllMCPs Server is listed as free. Auth: no auth required. Brightdata MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add allmcps-server and brightdata-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AllMCPs Server has a quality signal of 85/100 (Excellent) with 59 views, 20 installs and 4 GitHub stars. Brightdata MCP has 71/100 (Great) with 2 views, 0 installs and 2,661 GitHub stars.
Start unattended-agent registration: emails a 6-digit confirmation code to the given address. Follow up with confirm_mcp_agent to exchange the code for a bearer token, which unlocks verify_mcp_claim (and future privileged tools) without ever needing a human to sign in via browser.
confirm_mcp_agentExchange the 6-digit code emailed by register_mcp_agent for a durable bearer token (90-day TTL). Pass the returned token as `agentToken` on verify_mcp_claim, or set it as an `Authorization: Bearer <token>` header on subsequent MCP requests if your client supports that.
Brightdata MCP tools 11
search_engineScrape search results from Google, Bing or Yandex. Returns SERP results in JSON or Markdown (URL, title, description),Ideal forgathering current information, news, and detailed search results.
scrape_as_markdownScrape a single webpage URL with advanced options for content extraction and get back the results in MarkDown language. This tool can unlock any webpage even if it uses bot detection or CAPTCHA.
search_engine_batchRun multiple search queries simultaneously. Returns JSON for Google, Markdown for Bing/Yandex.
scrape_batchScrape multiple webpages URLs with advanced options for content extraction and get back the results in MarkDown language. This tool can unlock any webpage even if it uses bot detection or CAPTCHA.
discoverSearch the web and rank results by AI-driven relevance. Returns scored results with title, description, and URL. Supports intent-based ranking, geo-targeting, date filtering, and keyword filtering.
search_scrapersFind a Bright Data pre-built scraper (Web Scraper API, 1,200+ sites) for a site or data type, e.g. "amazon reviews" or "linkedin.com". Returns dataset_id, name, domain and collection_methods. Next: call get_scraper_details with a dataset_id and one method.
get_scraper_detailsShow the scraper description, input fields, example input and main output fields for one method. Call before run_scraper and build the input from sample_input or input_fields. Records may contain more fields than output_fields lists.
run_scraperRun a scraper method. input is a list of objects shaped like sample_input from get_scraper_details, one per URL or query. collect_by_url returns one record per input; discover_by_* methods return up to limit_per_input records per input, and every record is billed. Waits up to 45 seconds; if still running it returns snapshot_id with status "running": then poll get_scraper_progress and call get_scraper_results when ready. Records with an "error" field explain failed inputs.
get_scraper_progressStatus of a run: starting, running, ready, failed or canceled.
get_scraper_resultsRecords of a finished run. Returns status "running" if not ready yet.
refresh_scrapersReload the scraper list now instead of waiting for the daily refresh.