A side-by-side look at the Brightdata MCP and TinySearch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Brightdata MCP for search & data extraction work as a local process; choose TinySearch for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
API_TOKEN.GROUPS, TOOLS, search_engine.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 68/100 · Great | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Freemium | Free |
| Required env vars | API_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,671 | 230 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 8 | Not listed |
| Full listing | View Brightdata MCP | View TinySearch |
GROUPSTOOLSsearch_enginesearch_engine_batchscrape_as_markdownscrape_batchdiscovercustomNo tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"luminati-io-brightdata-mcp": {
"command": "npx",
"args": [
"-y",
"@brightdata/mcp"
],
"env": {
"API_TOKEN": "YOUR_API_TOKEN_HERE"
}
}
}
}
{
"mcpServers": {
"marcellm01-tinysearch": {
"command": "uvx",
"args": [
"--from",
"tinysuite-search[server]",
"tinysearch"
]
}
}
}