In-depth architectural comparison of the Cdek and Plain Freight 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
Cdek
Delivery · Local stdio
Quality: 36/100 (Fair) | Auth: No auth required
Plain Freight
Delivery · Remote HTTP/SSE
Quality: 36/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Cdek if you need specialized Delivery tools running via a local process. Choose Plain Freight if your workspace requires Delivery integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Cdek 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).
Cdek is categorized under Delivery and uses a local stdio subprocess. In contrast, Plain Freight belongs to Delivery using remote streaming HTTP/SSE transport. Select Cdek when you need capabilities focused on delivery and Plain Freight when you require tools for delivery.