ShipStation API MCP Server

Created By
mattcoatswortha year ago
Overview

what is ShipStation API MCP Server?

ShipStation API MCP Server is a comprehensive Model Context Protocol (MCP) server designed for interacting with the ShipStation API, providing tools and resources for managing various aspects of shipping and order fulfillment.

how to use ShipStation API MCP Server?

To use the ShipStation API MCP Server, clone the repository, install the necessary dependencies, create a .env file with your ShipStation API credentials, and run the server. You can then test the server using the MCP Inspector.

key features of ShipStation API MCP Server?

  • Complete coverage of ShipStation API endpoints
  • Structured tools for all API operations
  • Documentation resources for API reference
  • Error handling and logging

use cases of ShipStation API MCP Server?

  1. Managing orders and shipments efficiently.
  2. Integrating with various carriers and warehouses.
  3. Automating fulfillment processes through webhooks.

FAQ from ShipStation API MCP Server?

  • What is the purpose of the MCP server?

The MCP server facilitates interaction with the ShipStation API, allowing users to manage orders, shipments, and more.

  • How do I get started with the server?

Clone the repository, install dependencies, set up your API credentials, and run the server.

  • Is there documentation available?

Yes, API documentation can be accessed through the shipstation://docs/{section} resource.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mattcoatsworth
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago