Conqueror vs SearchAtlas
A side-by-side look at the Conqueror and SearchAtlas MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Conqueror for marketing work over a hosted endpoint; choose SearchAtlas for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Conqueror when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Choose SearchAtlas when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SEARCHATLAS_TOKEN, SEARCHATLAS_API_KEY, SEARCHATLAS_API_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 37/100 · Fair | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | SEARCHATLAS_TOKENSEARCHATLAS_API_KEYSEARCHATLAS_API_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2 |
| Directory activity | 3 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Conqueror | View SearchAtlas |
Tools & capabilities
Conqueror tools
No tool names declared yet. Check the project README from the listing page.
SearchAtlas tools
No tool names declared yet. Check the project README from the listing page.
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.
Conqueror
{
"mcpServers": {
"conqueror-2": {
"url": "https://winwith.conquerorapp.com/mcp"
}
}
}
SearchAtlas
{
"mcpServers": {
"searchatlas": {
"command": "npx",
"args": [
"-y",
"searchatlas-mcp-server"
],
"env": {
"SEARCHATLAS_TOKEN": "YOUR_SEARCHATLAS_TOKEN_HERE",
"SEARCHATLAS_API_KEY": "YOUR_SEARCHATLAS_API_KEY_HERE",
"SEARCHATLAS_API_URL": "YOUR_SEARCHATLAS_API_URL_HERE"
}
}
}
}
Frequently asked questions
Conqueror is categorized under Marketing and uses a remote HTTP/SSE transport. SearchAtlas belongs to Marketing and uses a local stdio subprocess. Pick Conqueror for marketing work and SearchAtlas for marketing.
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.
Conqueror has no declared pricing — check the project's own site. SearchAtlas has no declared pricing — check the project's own site. 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 conqueror-2 and searchatlas as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Conqueror has a quality signal of 37/100 (Fair) with 3 views, 0 installs and 0 GitHub stars. SearchAtlas has 43/100 (Fair) with 5 views, 0 installs and 2 GitHub stars.