cdek
Related Servers
Alternatives to cdek
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables CDEK delivery operations through natural language, including tariff calculation, order management, shipment tracking, pickup point search, courier pickup scheduling, barcode and receipt generation, and webhook management.751MIT
- FlicenseNot gradedqualityDmaintenanceEnables courier rate checks, order management, shipping, and tracking via Shiprocket's API through natural language.3-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to track packages, rate and create shipments, manage pickups and customs documentation, and perform international shipping logistics checks through natural language.MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Shiprocket shipping services to check courier rates and delivery times, create and manage orders, ship packages, track shipments, and schedule pickups through natural language commands.329-
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to track and manage deliveries by interacting with the Parcel delivery tracking API. Users can add new shipments, retrieve active delivery statuses, and look up carrier information through natural language.2-
- AlicenseNot gradedqualityDmaintenanceEnables integration with SF Express shipping and logistics APIs for order management, shipment tracking, route queries, and logistics services through natural language interactions.MIT
TDQS
Scored across 49 tools
Most tools have distinct purposes, but cdek_barcode and cdek_label both print barcodes with only format difference, causing slight confusion. Similarly, cdek_calculate_tariff, cdek_calculate_tarifflist, and cdek_calculate_tariff_and_service overlap in function. Overall, boundaries are clear for the majority.
CDEK operations consistently use 'cdek_verb_noun' pattern, but local tools (goods_list, goods_add, config_show) break the prefix convention, creating inconsistency. Some names like cdek_order_intakes or cdek_delivery_points use noun_noun instead of verb_noun.
With 49 tools, the server attempts to cover the full CDEK API plus local catalog/configuration. This is excessive for an MCP server, overwhelming agents and making tool selection error-prone. A more focused subset (15-20) would be appropriate.
The tool set covers major CDEK operations: order lifecycle, tracking, printing, tariff calculation, intakes, deliveries, webhooks, and location services. Only minor gaps exist (e.g., missing order status history or some document types), but core workflows are well-supported.