ShipStation API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
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 39 tools
Every tool has a clearly distinct purpose targeting specific resources and actions in the ShipStation domain. There is no ambiguity between tools like 'get_order' vs 'list_orders' or 'create_order' vs 'mark_order_as_shipped', as each handles a unique operation on well-defined entities.
Tool names follow a highly consistent verb_noun pattern throughout, such as 'create_order', 'list_orders', 'get_order', 'delete_order'. Minor variations like 'add_tag_to_order' or 'hold_order_until' maintain readability and adhere to the same overall naming convention without mixing styles.
With 39 tools, the count is borderline high for typical MCP server scope, potentially overwhelming for agents. While it covers many aspects of ShipStation's API, it might benefit from consolidation or categorization to reduce cognitive load, placing it in the 16-25+ range that feels heavy.
The tool set provides comprehensive CRUD and lifecycle coverage for the ShipStation domain, including orders, products, warehouses, stores, shipments, and webhooks. It supports full workflows from creation to deletion, with no obvious gaps that would cause agent failures in typical e-commerce operations.