delivery-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OSRM_URL | No | Optional URL to a running OSRM instance for real road distances. | |
| ROUTE_DB | No | Path to the SQLite database file. Defaults to 'data/routes.db'. | data/routes.db |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_deliveriesA | List deliveries for a date with weight, address and time window. |
| list_vehiclesA | List fleet vehicles with capacity (kg / units), depot and driver shift. |
| plan_routesA | Plan routes for the fleet on a date (CVRPTW). Returns per-vehicle stop sequence, ETA, distance and duration, plus deliveries that could not be assigned and why. Persists the plan so it can be inspected and edited. |
| get_route_detailB | Full stop-by-stop detail of a planned route: sequence, ETA, cumulative load. |
| evaluate_insertionA | Marginal cost (km and minutes) of inserting a delivery into each active route for a date, the best position, and whether it violates capacity or time windows. Provide either delivery_id (existing) or a new_delivery object. |
| commit_insertionB | Insert a delivery into a route at a position and rewrite downstream ETAs. |
| mark_vehicle_out_of_serviceB | Mark a vehicle inactive and return its orphaned (previously assigned) deliveries. |
| reassign_deliveriesC | Redistribute the given deliveries among active vehicles for a date; lists what did not fit. |
| update_delivery_statusB | Set a delivery's status (pending | assigned | delivered | failed). |
| export_route_sheetB | Render a printable route sheet for a route as markdown or CSV text. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a clear, distinct purpose: listing deliveries/vehicles, planning routes, viewing route details, evaluating/committing insertions, managing vehicle status, reassigning, updating delivery status, and exporting. No overlapping or ambiguous tools.
All tool names follow a consistent verb_noun snake_case pattern (list_, plan_, get_, evaluate_, commit_, mark_, reassign_, update_, export_). Verbs are specific and accurately describe actions.
10 tools is well-scoped for a delivery route planning MCP server, covering the full workflow without unnecessary bloat or missing essentials.
The surface covers the main lifecycle: listing, planning, viewing, modifying, and exporting. Minor gaps exist such as directly adding/removing deliveries or canceling a route, but the core operations are well represented.