ShipSmart-MCP
Provides shipping tools for DHL integration, including address validation and rate preview capabilities through the DHL shipping provider.
Provides shipping tools for FedEx integration, including address validation and rate preview capabilities through the FedEx shipping provider.
Provides shipping tools for UPS integration, including address validation and rate preview capabilities through the UPS shipping provider.
Provides shipping tools for USPS integration, including address validation and rate preview capabilities through the USPS shipping provider.
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., "@ShipSmart-MCPvalidate address 123 Main St San Francisco CA 94105"
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.
ShipSmart-MCP
Standalone MCP (Model Context Protocol) server exposing ShipSmart's shipping
tools (validate_address, get_quote_preview, …) over a small HTTP contract.
It is the single source of truth for tool behavior across the platform. Both
ShipSmart-API (Python / FastAPI — RAG & LLMs) and ShipSmart-Orchestrator
(Java / Spring Boot — upcoming AI features) call this server instead of
implementing tools in-process.
HTTP contract
Method | Path | Purpose |
GET |
| Service discovery (name, version, tool count, endpoints). |
GET |
| Liveness probe used by Render. |
POST |
| Return schemas for all registered tools. |
POST |
| Execute a tool by name with the provided arguments. |
Wire-compatible with the MCP tools/list and tools/call
semantics: each call returns { success, content: [...], error? }, where
content is a list of {type, text} blocks suitable for LLM consumption.
Auth
If MCP_API_KEY is set on the server, every POST /tools/* request must
send the matching value in X-MCP-Api-Key. If MCP_API_KEY is empty, auth
is disabled (local dev only).
Tools
Name | Description |
| Validate + normalize a shipping address through the configured carrier. |
| Non-binding rate preview for a package. Final rates come from the Java API. |
Tools delegate to pluggable ShippingProvider implementations
(mock, ups, fedex, dhl, usps) selected by SHIPPING_PROVIDER.
Adding a tool is a matter of dropping a new class into app/tools/ and
registering it in app/main.py.
Running locally
cp .env.example .env
# fill in credentials if you want real carrier integration; default is SHIPPING_PROVIDER=mock
uv sync
uv run uvicorn app.main:app --reload --host 0.0.0.0 --port 8001Smoke test:
curl -s http://localhost:8001/health
curl -s -X POST http://localhost:8001/tools/list
curl -s -X POST http://localhost:8001/tools/call \
-H 'Content-Type: application/json' \
-d '{
"name": "validate_address",
"arguments": {
"street": "123 Main St",
"city": "San Francisco",
"state": "CA",
"zip_code": "94105"
}
}'Tests
uv run pytestConsumers
ShipSmart-API (Python/FastAPI): points
SHIPSMART_MCP_URLat the deployed server and calls/tools/list+/tools/callfrom its orchestration and advisor services.ShipSmart-Orchestrator (Java/Spring Boot): will call the same HTTP contract from its upcoming AI-assist flows. No tool logic lives in the Java codebase.
This keeps the tool layer centralized — add a tool once, every service gets it.
This server cannot be installed
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
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/nia194/ShipSmart-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server