Global Logistics MCP
Aggregation platform for shipping labels; this MCP server uses the AfterShip Shipping API to quote rates, create labels, and cancel labels across multiple carriers with the merchant's own carrier accounts.
Allows creating shipping labels via DHL through the AfterShip integration.
Allows creating shipping labels via FedEx through the AfterShip integration.
Allows creating shipping labels via UPS through the AfterShip integration.
Allows creating shipping labels via USPS through the AfterShip integration.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Global Logistics MCPget shipping rates for a 2kg parcel from USA to GBR"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Global Logistics MCP
Use it in 60 seconds
Paste this into your MCP client config (Claude Desktop, Cursor, Windsurf, or any MCP-capable agent):
{
"mcpServers": {
"global-logistics": {
"type": "http",
"url": "https://logi-global.wishpool.app/mcp"
}
}
}Nothing to install. Credentials, when you need them, travel as HTTP headers on each request and are never stored — see the threat model.
Or run it yourself
Would you rather not send production credentials to a server you do not control? Deploy this identical code to your own account and point your agent at your own URL:
git clone https://github.com/junter1989k-ai/global-logistics-mcp && cd global-logistics-mcp && npx vercel --prodMIT-licensed. Self-hosting removes us from the picture entirely, at no cost and with no loss of function.
Remote MCP server that lets any AI agent buy shipping labels worldwide via AfterShip Shipping (Postmen) — UPS, USPS, FedEx, DHL, Ninja Van, J&T and more — using the merchant's OWN bound carrier accounts. Stateless, bring-your-own API key, never stored.
Endpoint:
https://logi-global.wishpool.app/mcp(MCP Streamable HTTP, stateless JSON)Credential header:
x-aftership-key(your AfterShip key; forwarded upstream asas-api-key)Environment header:
x-aftership-env=sandbox(default — real labels at zero cost) orproduction
Related MCP server: royalmail-mcp
The aggregation model (the honest core)
This server owns no carrier accounts. AfterShip is an aggregation layer: the merchant
binds their own carrier accounts (their contracts and rates) inside AfterShip
(admin.postmen.com) and passes that shipper_account_id on each call. This is exactly how an
agent reaches carriers that do not issue self-serve API keys — J&T, Ninja Van, Aramex —
the curve-around is the merchant's AfterShip-bound account. The sandbox can be tested with a fake
shipper account at zero cost.
Tools & capability matrix
Tool | AfterShip endpoint | Supported | Notes |
|
| ✅ yes | Compare live rates across the carriers on |
|
| ✅ yes | Buy a chosen |
|
| ✅ yes | Void an unused label by |
| — | ❌ not supported | The Shipping (Postmen) API has no tracking endpoint. Tracking is a separate product: the AfterShip Tracking API. Returns a structured |
Addresses use ISO 3166-1 alpha-3 country codes (USA, GBR, JPN). Weight and dimension are
{value, unit} (unit kg|lb|oz|g and cm|in|m).
Owner policy guardrails
Set by the human owner in the MCP client config; the agent cannot relax them. The label charge is gated before any purchase.
x-agentpay-max-amount— hard cap; over it,POLICY_BLOCKED.x-agentpay-approval-above— over it, returns an unsigned draft (rate quoted, no label bought).x-agentpay-allowed-tools— tool allow-list.
Safety
Stateless translation layer: the AfterShip API key travels per-request in a header and is never stored; labels are generated and served by AfterShip/the carrier, never held here. Parcels flow sender ↔ carrier ↔ recipient directly.
Develop
npm run dev # local server on http://localhost:3242
npm test # e2e: protocol + validation + units + fake-key real 401 fingerprintThe e2e suite includes a live probe: a fake key really hits sandbox-api.aftership.com and
must receive the native 401 "The API key is invalid." fingerprint (proving the endpoint is alive).
Sister servers
US domestic labels via EasyPost — usa-logistics-mcp · Taiwan CVS pickup & home delivery — taiwan-logistics-mcp · local payments in 81 countries — mcp.wishpool.app · electronic-invoice servers across nine countries (Mexico CFDI, Brazil NF-e, Chile DTE, Peru CPE, India GST).
MIT.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/junter1989k-ai/global-logistics-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server