Shipi MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHIPI_BASE_URL | No | API base URL (default: https://app.myshipi.com) | https://app.myshipi.com |
| SHIPI_INTEGRATION_KEY | Yes | Your Shipi integration key |
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 |
|---|---|
| list_shipmentsC | List shipments with pagination and filters. Filter by status (new/created/delivered), carrier, or date range. |
| get_shipmentB | Get detailed information about a specific shipment by ID or order ID. Includes shipper, recipient, products, tracking, and label URLs. |
| search_shipmentsC | Search shipments by order ID or tracking number. Returns matching shipments. |
| create_shipmentA | Create a shipping label. Requires carrier account, shipper/recipient addresses, and product details. Returns tracking number and label URL. |
| cancel_shipmentB | Cancel a shipment and void its label. Requires the shipment ID (del_ref). |
| get_shipping_ratesA | Get live shipping rates from all configured carriers. Provide recipient address and package details to compare prices across FedEx, UPS, DHL, USPS, etc. |
| schedule_pickupB | Schedule a carrier pickup for a shipment. The carrier will come to the shipper address to collect the package. |
| track_shipmentA | Get a tracking URL for a shipment. Supports auto-detection of carrier from tracking number format. |
| fetch_labelsA | Fetch shipping labels for printing. Filter by printed/unprinted status. Returns label URLs. |
| list_addressesB | List all saved addresses from the address book. Filter by type (shipper/receiver). |
| get_addressC | Get a specific address by ID from the address book. |
| add_addressC | Add a new address to the address book. Used for saving shipper or receiver addresses for reuse. |
| edit_addressC | Update an existing address in the address book. Only changed fields need to be provided. |
| delete_addressB | Delete an address from the address book by ID. |
| list_carriersA | List all configured shipping carrier accounts. Shows carrier type, primary status, and shipper address. Credentials are never exposed. |
| get_carrierB | Get details of a specific carrier account by ID. Returns carrier type and shipper address info. |
| get_account_infoB | Get Shipi account information including user details, store info, billing/balance, plan, and feature flags. |
| get_shipping_statsC | Get shipping statistics and analytics. View shipment counts, cost breakdowns, carrier usage, tracking status, and daily trends. |
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 18 tools
Each tool has a clearly distinct purpose targeting specific resources and actions, such as address management (add_address, edit_address, delete_address), shipment operations (create_shipment, cancel_shipment, track_shipment), and informational queries (get_shipping_rates, get_shipping_stats). There is no overlap or ambiguity in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern, such as 'add_address', 'cancel_shipment', 'get_account_info', and 'list_carriers'. This uniformity in naming conventions enhances readability and predictability, allowing agents to easily understand and navigate the tool set without confusion from mixed styles.
With 18 tools, the server is well-scoped for its shipping and logistics domain, covering key areas like address management, shipment lifecycle, carrier operations, and analytics. Each tool serves a specific and necessary function, avoiding redundancy while providing comprehensive coverage, which is appropriate for the complexity of the domain.
The tool set offers complete CRUD/lifecycle coverage for shipping operations, including address management (create, read, update, delete), shipment handling (create, cancel, track, list, search), carrier management (list, get), and analytics (stats, rates). There are no obvious gaps, ensuring agents can perform all essential workflows without dead ends.