Boxberry MCP vs Cdek — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Boxberry MCP vs Cdek
In-depth architectural comparison of the Boxberry MCP and Cdek 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
Boxberry MCP
Delivery · Local stdio
Quality: 30/100 (Emerging) | Auth: No auth required
Cdek
Delivery · Local stdio
Quality: 36/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Boxberry MCP if you need specialized Delivery tools running via a local process. Choose Cdek 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 Boxberry MCP when:
You need dedicated capabilities in the Delivery domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Boxberry MCP is categorized under Delivery and uses a local stdio subprocess. In contrast, Cdek belongs to Delivery using local stdio subprocess. Select Boxberry MCP when you need capabilities focused on delivery and Cdek when you require tools for delivery.