Codemagic MCP vs Nahook MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Codemagic MCP vs Nahook MCP
In-depth architectural comparison of the Codemagic MCP and Nahook MCP 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
Codemagic MCP
Delivery · Local stdio
Quality: 40/100 (Fair) | Auth: API Key required
Nahook MCP
Delivery · Local stdio
Quality: 48/100 (Fair) | Auth: other
Verdict Summary: Choose Codemagic MCP if you need specialized Delivery tools running via a local process. Choose Nahook MCP if your workspace requires Delivery integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Codemagic MCP when:
You need dedicated capabilities in the Delivery domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: CODEMAGIC_API_TOKEN, ASC_KEY_ID, ASC_ISSUER_ID, ASC_PRIVATE_KEY_B64, ASC_BYPASS_KEYCHAIN, GOOGLE_PLAY_SERVICE_ACCOUNT_CREDENTIALS.
Codemagic MCP is categorized under Delivery and uses a local stdio subprocess. In contrast, Nahook MCP belongs to Delivery using local stdio subprocess. Select Codemagic MCP when you need capabilities focused on delivery and Nahook MCP when you require tools for delivery.
Build, sign, and publish iOS and Android apps through AI agents. Integrates Codemagic CI/CD, App Store Connect, and Google Play in one server.
"The official MCP server for the Nahook webhook platform — trigger webhooks, inspect deliveries, retry failures, and manage endpoints from your AI assistant."