shiplabel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DHL_API_CLIENT_ID | No | DHL developer app client ID (production) | |
| DHL_API_CLIENT_SECRET | No | DHL developer app client secret (production) | |
| SHIPLABEL_DHL_SANDBOX | No | Set to 'true' to use DHL sandbox | |
| SHIPLABEL_CARRIERS_DIR | No | Directory with custom carrier JSON specs | |
| SHIPLABEL_DHL_PASSWORD | No | DHL GKP password | |
| SHIPLABEL_DHL_USERNAME | No | DHL GKP username | |
| SHIPLABEL_DPD_CLOUD_ID | No | DPD cloud ID | |
| SHIPLABEL_DPD_PASSWORD | No | DPD partner password | |
| SHIPLABEL_DPD_USERNAME | No | DPD partner username | |
| SHIPLABEL_GLS_PASSWORD | No | GLS password | |
| SHIPLABEL_GLS_USERNAME | No | GLS username | |
| SHIPLABEL_FEDEX_API_KEY | No | FedEx API key | |
| SHIPLABEL_UPS_CLIENT_ID | No | UPS client ID | |
| DHL_API_CLIENT_ID_SANDBOX | No | DHL developer app client ID (sandbox) | |
| SHIPLABEL_FEDEX_SECRET_KEY | No | FedEx secret key | |
| SHIPLABEL_DHL_ACCOUNTNUMBER | No | DHL billing account number | |
| SHIPLABEL_SHIPCLOUD_API_KEY | No | Shipcloud API key | |
| SHIPLABEL_UPS_CLIENT_SECRET | No | UPS client secret | |
| SHIPLABEL_DHL_RETURN_API_KEY | No | DHL Return API key | |
| SHIPLABEL_UPS_ACCOUNT_NUMBER | No | UPS account number | |
| DHL_API_CLIENT_SECRET_SANDBOX | No | DHL developer app client secret (sandbox) | |
| SHIPLABEL_SENDCLOUD_METHOD_ID | No | Sendcloud shipping method ID | |
| SHIPLABEL_FEDEX_ACCOUNT_NUMBER | No | FedEx account number | |
| SHIPLABEL_SENDCLOUD_PUBLIC_KEY | No | Sendcloud public API key | |
| SHIPLABEL_SENDCLOUD_SECRET_KEY | No | Sendcloud secret API key | |
| SHIPLABEL_DHL_RETURN_RECEIVER_ID | No | DHL Return receiver ID |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_carriersA | List the shipping carriers this server can create labels for. |
| describe_carrierA | Describe the canonical shipment request and, if Call this before |
| create_labelA | Create a shipping label from a canonical shipment request.
Returns the shipment number and, per parcel, the tracking number/URL, label format and (unless disabled) the base64-encoded label. |
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 3 tools
Each tool has a distinct purpose: list_carriers discovers carriers, describe_carrier explains requirements, create_label performs the main action. No functional overlap.
All tools follow a consistent verb_noun pattern with lowercase and underscores (list_carriers, describe_carrier, create_label), making the API predictable.
Three tools is slightly minimal but appropriate for a focused shipping label MCP. It covers discovery, guidance, and creation without extra fluff.
The core workflow (list carriers, describe requirements, create label) is fully covered. Missing operations like label retrieval or cancellation are minor gaps given the server's purpose.