delovye-linii-mcp
Related Servers
Alternatives to delovye-linii-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for Yandex Delivery B2B API, enabling natural language interaction to calculate delivery costs, create and manage express and platform delivery orders, track couriers, and handle pickup points.1660 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the Yango Delivery B2B API, enabling price estimation, express-courier claim creation and confirmation, courier tracking, and recipient tracking links through natural language.1344 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server providing access to Russian Railways ticket API, enabling train search, station lookup, and trip information.1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that integrates with the Jadlog logistics API, enabling shipping order creation and cancellation, freight simulation, tracking queries, CT-e XML retrieval, pick-up/drop-off point lookup, QR code generation, and TOTVS Moda integration for order payloads.MIT
- FlicenseAqualityDmaintenanceMCP server for BlueDart (DHL eCommerce India) shipping API enabling waybill creation, tracking, pickup scheduling, and transit time lookup via MCP tools.8-
- AlicenseDqualityDmaintenanceMCP server for Yandex Delivery API, allowing AI assistants to manage deliveries, track couriers, and handle orders.21MIT
TDQS
Scored across 6 tools
Each tool targets a distinct operation: calculate pricing, track shipments, search terminals, create orders, view history, and search cities. There is minor overlap potential between calculate (rate/schedule) and create_order (which may imply cost negotiation), and get_order_history vs track could overlap conceptually but generally serve different query types. Overall boundaries are clear enough for an agent.
Most tools follow a clean verb_noun pattern: calculate, get_terminals, create_order, get_order_history, get_cities. Only 'track' deviates as a bare verb rather than verb_noun (e.g. track_order or get_tracking). This is a minor inconsistency but otherwise the naming is predictable and readable.
Six tools is a well-scoped set for a logistics/courier MCP server covering the major user journeys: quoting, booking, tracking, and reference lookups. Each tool clearly earns its place, and the count feels appropriate for the domain.
The surface covers core workflows well: city lookup, terminal lookup, pricing, order creation, order tracking, and order history. Obvious gaps include the ability to cancel or update an order, and there is no document/label generation for shipping, though these are secondary for a courier integration. Core lifecycle is otherwise present.