Coresignal MCP vs Brightdata MCP
A side-by-side look at the Coresignal MCP 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 Coresignal MCP for developer tools work over a hosted endpoint; choose Brightdata MCP for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Coresignal MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
entity_search, entity_fields, entity_fetch.
Choose Brightdata MCP when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
API_TOKEN. - You want tools like
search_engine, scrape_as_markdown, search_engine_batch.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Search & Data Extraction |
| Quality signal | 48/100 · Fair | 73/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | API_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 2,685 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 5 | 11 |
| Full listing | View Coresignal MCP | View Brightdata MCP |
Tools & capabilities
Coresignal MCP tools 5
entity_searchNatural-language search over employees, companies, or jobsentity_fieldsKeyword search over an entity's ~300 field namesentity_fetchPull full (JSONL) or projected records, by search handle or by idemail_enrichVerified business emails for employee ids (CSV)artifact_readPage rows back out of a delivered file
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.
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.
Coresignal MCP
{
"mcpServers": {
"mcp-77": {
"url": "https://mcp.coresignal.com/mcp/v2"
}
}
}
Brightdata MCP
{
"mcpServers": {
"brightdata-mcp": {
"command": "npx",
"args": [
"@brightdata/mcp"
],
"env": {
"API_TOKEN": "YOUR_API_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Coresignal MCP is categorized under Developer Tools and uses a remote HTTP/SSE transport. Brightdata MCP belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Coresignal MCP for developer tools work and Brightdata MCP for search & data extraction.
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.
Coresignal MCP has no declared pricing — check the project's own site. Brightdata MCP is listed as freemium — a free tier with paid plans. Auth: api key required. 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 mcp-77 and brightdata-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Coresignal MCP has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. Brightdata MCP has 73/100 (Great) with 4 views, 0 installs and 2,685 GitHub stars.