shipstation

This MCP server provides a comprehensive interface to the ShipStation API, exposing tools for managing orders, shipments, carriers, warehouses, products, customers, stores, webhooks, and fulfillments. Use the documented endpoints and actions to perform common operations such as listing orders, creating shipments, generating labels, managing stores and webhooks, and handling fulfillments. The API docs are organized into sections (orders, shipments, carriers, warehouses, products, customers, stores, webhooks, fulfillments) accessible via shipstation://docs/{section}. For example, shipstation://docs/orders provides an overview of order-related operations. Tools are grouped under each resource, e.g. list_orders, get_order, create_order, and similarly for other resources like shipments, carriers, and stores. To get started, configure your ShipStation credentials in a .env file, install dependencies, and run the dev server. You can then test and explore the API via MCP Inspector or your client tooling wired through the MCP interface.

Prerequisites:

• Node.js (14+ recommended) and npm
• Access to ShipStation API with an API key and secret

Step-by-step:

1. Clone the repository: git clone https://github.com/your/repo.git cd repo

2. Install dependencies: npm install

3. Create a .env file with your ShipStation credentials: SHIPSTATION_API_KEY=your_api_key SHIPSTATION_API_SECRET=your_api_secret

4. Start the server in development mode: npm run dev

5. (Optional) Run the MCP inspector to test endpoints: npm run inspect

Note: If your environment uses a different entry point, update the mcp_config accordingly to point to the correct server file (e.g., path/to/server.js).

Tips:

• Ensure your ShipStation API credentials are kept secure and not committed to version control.
• If you encounter authentication errors, verify that the API key/secret are valid and have the necessary permissions.
• The MCP docs can be accessed at shipstation://docs/{section}; use this to discover available operations under each resource.
• For local development, you can mock ShipStation responses to speed up testing, but ensure real credentials are used in integration tests.
• Check environment variable scoping in your hosting environment; some platforms require explicit variable definitions in the deployment settings.
• If you update endpoints or add new tools, reload the MCP server to pick up changes.