pingLABSCO SUMMARY
One account in front of three carriers, so comparing rates is a single question.
FedEx, UPS and DHL each have their own API and their own credentials; here they sit behind one ShipBoss token, which is what turns "what would this cost" into a single call rather than three integrations. Labels come back as a direct download URL instead of encoded bytes you have to reassemble. Two setup notes in the order they matter: the token comes from the API Integrations page in the ShipBoss admin rather than from your login, and the configuration points at a virtual environment's Python by full path — so create the environment before you write the config.
What it is
An MCP server over the ShipBoss shipping platform, which sits in front of FedEx, UPS and DHL on one account. The tools cover the parcel lifecycle — rates, labels, tracking, pickup scheduling — plus freight quoting and freight tracking.
What you get
- get_parcel_rates returns shipping rates for a parcel between two addresses
- create_parcel_label creates the label and answers with a direct download URL
- track_parcel follows a shipment once it is moving
- create_pickup schedules a carrier collection, and cancel_pickup calls one off
- get_freight_rates quotes freight shipments, and track_freight follows them
- ping is a health check, useful for confirming the server and the token work before anything else is attempted
Requirements
Python 3.9+ and a ShipBoss account. The publisher requires a virtual environment: create one, activate it, then pip install shipboss-mcp-server, and point your client's command at that environment's Python interpreter and at shipboss_mcp_server.py by full path. The API token comes from ShipBoss Admin → API Integrations and can be supplied three ways: SHIPBOSS_API_TOKEN in a .env file next to the server file, --api-token on the command line, or SHIPBOSS_API_TOKEN in the client config's env block.
Setup effort
Follow the published steps — python -m venv shipboss_env
USE CASES
01
Pricing a shipment before promising a delivery date
Rates between two addresses for the weight and dimensions you have, across the carriers connected to the account, in one answer.
02
Getting a package out the door
Create the label for the carrier and service you chose and take the download URL it returns, then follow the shipment with the same tool set.
03
Arranging collection instead of a depot run
Schedule a carrier pickup for the shipment you just labelled, and cancel it if the plan changes.
04
Quoting something too big for a parcel
Freight rates for the load, and freight tracking once it is booked, using the same account and token as the parcel side.
8 tools
Listed in project docs. Your client may show a different list.
get_parcel_ratescreate_parcel_labeltrack_parcelcreate_pickupcancel_pickupget_freight_ratestrack_freightBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation. create_parcel_label buys a real FedEx, UPS or DHL label, and create_pickup and cancel_pickup schedule and cancel collections; the other five only read. ping checks that your token works.
Requires
- Python 3.9+
- SHIPBOSS_API_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
python -m venv shipboss_env
source shipboss_env/bin/activate
pip install shipboss-mcp-serverMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"shipboss-mcp": {
"command": "<YOUR_PATH_TO_SHIPBOSS_ENV>/bin/shipboss-mcp-server",
"env": {
"SHIPBOSS_API_TOKEN": "<YOUR_SHIPBOSS_API_TOKEN>"
}
}
}
}
