F
licenseA
qualityD
maintenanceEnables LLM clients to access scheduling data, KPIs, routes, and trigger optimization algorithms via MCP.
9
-
Spoke Dispatch MCP server
by dragosh29
Related Servers
Alternatives to Spoke Dispatch MCP server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables authenticated MCP tools for planning commercial routes with fail-closed economic boundaries, plus marketplace discovery, matching, and agent interaction capabilities.-
- FlicenseNot gradedqualityCmaintenanceEnables logistics route optimization by exposing tools for traffic factors, holiday and circulation restrictions, and fuel price references over a remote MCP HTTPS endpoint.-
- FlicenseAqualityBmaintenancePlans and optimizes last-mile delivery routes with capacity and time-window constraints, offering tools for managing deliveries, vehicles, routes, and what-if scenarios.10-
- AlicenseAqualityCmaintenanceEnables MCP clients to search availability, read services, resources, bookings and customers, and, when writes are enabled, reserve slots, create or cancel bookings, and add or update customers.10MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to read campaign and account data freely while routing every write through human-approved plans, with budget caps, drift refusal, undo, and audit logging.6MIT
TDQS
A3.8/5.0
Scored across 12 tools
Disambiguation5/5
Each tool has a distinct scope: get_* retrieves a single entity, list_* retrieves collections, list_plan_stops and list_route_stops differ by parent scope, and search_stops provides cross-cutting full-text search. Overlaps between get_route and list_routes (or get_plan and list_plans) are cardinality differences, not ambiguities.
Naming Consistency5/5
All tool names use consistent snake_case with a clear verb_noun pattern: get_route, list_plans, get_plan, list_plan_stops, search_stops, etc. No mixed conventions or confusing verb choices.
Tool Count5/5
The 12 tools are well-scoped: each covers a distinct resource and action (plans, routes, stops, drivers, depots, operations) without obvious filler or duplication. This is an appropriate size for the dispatch domain.
Completeness3/5
The surface covers read access to plans, routes, stops, drivers, depots, and operations, but has no mutation or lifecycle tools (create/update/delete for core entities). Crucially, get_operation references optimize_plan as the source of operations, yet no optimize_plan tool is provided, creating a dead end for a key workflow.
Maintenance
ActivityMaintained
ResponsivenessNo issues