Conqueror vs Derrick — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Conqueror vs Derrick
In-depth architectural comparison of the Conqueror and Derrick MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Conqueror
Marketing · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Derrick
Marketing · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Verdict Summary: Choose Conqueror if you need specialized Marketing tools running via a local process. Choose Derrick if your workspace requires Marketing integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Conqueror when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Turns SEO insight into page changes: keyword research, SERP and rank data, rewrites you approve.
B2B data enrichment tools for any MCP client. Ask for a verified work email, a phone number, company firmographics, a tech stack or hiring signals in plain language, and get real data back instead of a guess. Tools are loaded dynamically from the Derrick API, so new actions appear without updating the server. Requires a Derrick account with API access, from the Standard plan at 20 EUR a month.
Conqueror is categorized under Marketing and uses a local stdio subprocess. In contrast, Derrick belongs to Marketing using local stdio subprocess. Select Conqueror when you need capabilities focused on marketing and Derrick when you require tools for marketing.