bluedart-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLUEDART_DEBUG | No | Set to 'true' for verbose stderr logging | |
| BLUEDART_API_TYPE | No | API type (S for sandbox or as documented) | S |
| BLUEDART_BASE_URL | Yes | Base URL for BlueDart APIGEE (sandbox or production) | |
| BLUEDART_LOGIN_ID | Yes | Profile LoginID (used in BlueDart payload) | |
| BLUEDART_CLIENT_ID | Yes | OAuth Consumer Key from your APIGEE app | |
| BLUEDART_LICENSE_KEY | Yes | Profile LicenceKey | |
| BLUEDART_CLIENT_SECRET | Yes | OAuth Consumer Secret |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bluedart_generate_waybillA | Create a single BlueDart Air Waybill (AWB) for a shipment. Calls POST /waybill/v1/GenerateWayBill. Returns the AWB number, routing info, and (unless suppressed) a base64 AWB label PDF in AWBPrintContent. PRECONDITIONS: OriginArea must match the shipper pincode region (e.g. OriginArea='DEL' for pin '110030') or BlueDart returns InvalidAreaScNotInRegion. CreditReferenceNo must be unique per shipment or BlueDart rejects with 'Waybill already generated'. Weight is in kilograms, dimensions in centimetres. |
| bluedart_import_waybillA | Create multiple BlueDart waybills in a single request via POST /waybill/v1/ImportData. Each entry has the same shape as bluedart_generate_waybill. Returns per-shipment results; partial successes are possible. |
| bluedart_cancel_waybillA | Cancel a BlueDart waybill by AWB number via POST /waybill/v1/CancelWaybill. Only works before the shipment has been manifest-scanned (in-scanned). After in-scan, cancellation is rejected by BlueDart. |
| bluedart_register_pickupA | Schedule a BlueDart pickup at the customer location via POST /pickup/v1/RegisterPickup. Returns a TokenNumber that is required to cancel the pickup later. AreaCode must match the pickup pincode region (same constraint as waybill OriginArea). |
| bluedart_cancel_pickupA | Cancel a previously registered pickup via POST /cancel-pickup/v1/CancelPickup. Requires the TokenNumber returned by bluedart_register_pickup and the original ShipmentPickupDate. |
| bluedart_get_transit_timeA | Estimate the expected delivery date for a shipment between two Indian pincodes via POST /transit/v1/GetDomesticTransitTimeForPinCodeandProduct. Read-only; safe to call repeatedly. |
| bluedart_track_shipmentA | Track a BlueDart shipment by AWB number. Read-only. Returns the current status, expected delivery date, and (when include_scans=true) the scan history. Set response_format='markdown' for a human-readable summary or 'json' for the raw payload. |
| bluedart_download_pincode_masterA | Download serviceable pincode master data via POST /masterdownload/v1/DownloadPinCodeMaster. Pass last_sync_date to get only changes since that date. The response can be very large; consider syncing incrementally. |
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 8 tools
Each tool targets a distinct operation (cancel, create, track, schedule, etc.) with no overlap. The descriptions clearly differentiate their purposes.
All tools follow the consistent pattern 'bluedart_verb_noun' (e.g., bluedart_cancel_pickup, bluedart_generate_waybill), making the set predictable.
With 8 tools, the server covers the core logistics workflows without being overwhelming or too sparse—excellent scope for a single domain.
The tool set covers essential CRUD-like operations for waybills and pickups, plus tracking and transit time. Minor gaps like updating a shipment or listing waybills are not critical for the primary use cases.