In-depth architectural comparison of the Codemagic MCP and Novaposhta 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
Novaposhta
Delivery · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Codemagic MCP if you need specialized Delivery tools running via a local process. Choose Novaposhta 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, Novaposhta belongs to Delivery using local stdio subprocess. Select Codemagic MCP when you need capabilities focused on delivery and Novaposhta when you require tools for delivery.