DragonMCP vs Cdek — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
DragonMCP vs Cdek
In-depth architectural comparison of the DragonMCP 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
DragonMCP
Delivery · Local stdio
Quality: 52/100 (Good) | Auth: API Key required
Cdek
Delivery · Local stdio
Quality: 36/100 (Fair) | Auth: No auth required
Verdict Summary: Choose DragonMCP 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 DragonMCP 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: AMAP_API_KEY.
Primary tools included: Live MTR arrivals and transfer-aware journey planning, Hong Kong weather and warning data, Unified Hong Kong and Mainland China transit routing.
MCP server for Greater China local life services: Meituan/Ele.me food delivery, Didi/Meituan ride-hailing, WeChat Pay/Alipay, Amap/Baidu Maps, 12306 high-speed rail, Taobao/JD/Xianyu e-commerce, Hong Kong government e-services, and more.
MCP server for CDEK delivery service API — create orders, track shipments, search delivery points
DragonMCP is categorized under Delivery and uses a local stdio subprocess. In contrast, Cdek belongs to Delivery using local stdio subprocess. Select DragonMCP when you need capabilities focused on delivery and Cdek when you require tools for delivery.